First of all, is it # of Days ? Number of executions ? Auditors are looking for records!
Thank you Luu for spending your time explaining this to me.
What version are you on? (using Java UI or AWI)... The data should just list *** number of record... (it probably on the current default limit right now so you won't see all it in the ui).
Edit: It will also depend on how your maintenance for the system is set - how long are your record retained before clean out of the DB... and if you do archived them or not
-In UC_SYSTEM_SETTING ---> The setting: GENERIC_STATISTICS_LIMIT limit how many are display at one time (note the default is 5000 with a max of 20,000).
If you your auditor need record consider using the DB report tools (+also check on your maintenance job for how long retention of those record are for).
We are on 11.2.1 and I use the Java UI.
Are you saying I need the web UI in order to see the value ?
Where do I find these settings, including the maintenance info ?
No you don't need to be in the webui - i had ask for version/that since everyone are on varying things and some setting may differ in latter versiion.
The statistics is determine by the UC_SYSTEM_SETTING ---> The setting: GENERIC_STATISTICS_LIMITIt limit how many can be displayed at one time (default 5000 with a max at 20,000)
For the maintenance information - On your system someone should of created a series of jobs that ARCHIVE, REORG and Unload the data... (and those jobs call the archive/reorg/unload utility).
Here an example of (one way of how the maintenance can be set up): AWA Data Archival
Thanks Luu. We have those jobs already set up that execute nightly. Our GENERIC_SYSTEMS_LIMIT is set to 5000, If I understand that correctly, at the most, we would have 5000 statistics records for the whole system available at any time. So we don't retain history by days, but by execution occurrences and we would have to adjust the 5000 limit to a number that would leave statistics records that go back far enough to satisfy the requirement of 6 months, 8 months, etc. ?
I think there a slight confusion... for viewing in the UI purpose, it is by # of statistical record... default of 5000.... but with the data as a whole it is counted as - Retain history by days (definied by the maintiance jobs).
As all the data is in the Database - as for how long they are retain, it will depend on your database maintenance job... (for example... keep record (report/statistic etc...) no more than 30days...
That GENERIC_SYSTEM_LIMIT - just mean that your record, that the maximum amount that the system "Show" at a given time... when viewing in the UI....
If you are having auditor looking for data - I would high checked your maintenance jobs (as you might of removed data/reports etc... older than XX days from the Database & depending on maintenance is set, the data would of been archive as a file on your system where the utility is located... If you want to view record, especially for auditor pupose, I would suggest using the DB Reporting Tool .
Hi Luu, That's exactly the value I am looking for "older than XX days from the Database"
I reviewed the pdf you attached but we have our AE DB on a Linux server so I'm not making the connection on how to start that up.
We have the standard maintenance jobs built by Automic that execute every night.
Since you have the maintenance job set up - There are a few object (in each of the client) such as:
UC_UTILITY_ARCHIVE - In here it have the setting if you had for "archiving" any messages/statistics/reportUC_UTILITY_REORG - This will have the value where you would set to removed older than XX date
Note that if you increase this now, it just mean that all future maintenance job would be kept longer... If you are looking to view the current old statistic record... I would see if the current maintenance job kept the record duration as you want... if it doesn't... see how your archive was set up (if you had it done), it should of output a file on the system where that DB Utility was so you can keep.
Thank you Luu. I found the values. I think I'm finally getting it!
Our UC_UTILITY_ARCHIVE has the values:
So after 60 days, (AH) our statistics will rollover to our archive files and they will no longer be viewable within AE. Is this correct ?
Our UC_UTILITY_REORG has the values:
So AH here says to reorg the statistics older than 60 days ? But would they not have been rolled over to an archive file based on the settings in the UC_UTILITY_ARCHIVE?
I searched the log for yesterdays reorg maintenance job and found this;
20180810/060837.104 - U00032189 Reorganization started in client '1000'.20180810/060837.104 - Messages (MELD): read: '30' days ('2018.07.10') unread: '30' days ('2018.07.10')20180810/060837.104 - Statistics (AH): '60' days ('2018.06.10') Keep last 30 Statistical records per object20180810/060837.104 - Reports (RH/RT): '14' days ('2018.07.26') Keep last 14 Reports per object20180810/060837.104 - Version Management: '30' days ('2018.07.10') Keep last 5 VC per object
And this in our Archive log:
20180810/060601.953 - U00031113 Archiving in client '1000' started.20180810/060601.953 - Messages (MELD): read: '7' days ('2018.08.02 19:00:00') unread: '7' days ('2018.08.02 19:00:00')20180810/060601.953 - Statistics (AH/RH): '60' days ('2018.06.10 19:00:00')
Thanks for your patience.
Yes, it look like it will flag those statistical record that are over 60days old for removal (while only retaining only 30 record of each). Anything thats past the 60 days and are over the 30 iteration will be removed and won't be viewable in the AE UI.
So.. this part might be a little confusion - but there a few setting that you would need to check in the utility .ini file also.
REORG: There are 2 setting to check:
no_archive_check= (see if it has 0 or 1 - since 1 mean that it doesn't care if the record is flag for archive or not and would flag the record for remove if it fit the criteria. The zero mean, that it won't be flag for removal unless there is a flag for archive for that record.
auto_reorg= (this by default reorg/flag for removal all record older than 365days UNLESS you have no_archive_check=0 )
UNLOAD: Check to see if there is a setting of "suppress_out= " . (if you have it with the 1, it will skip writing out the data to a file for ).
With the Archive, Reorg & Unload... The Archive will "flag" anything in the data that you want to archive... and the reorg also "flag" those record too and the unload is the part when it really remove it all.
So in essence, anything that got "flagged" for archive and reorg... when the unload run... it will create the file for you to keep and removed that data from the database (unless some of the setting above are used).
Retrieving data ...