How to Manage your UC4 System database on UNIX machine
Article ID: 88748
Updated On:
Products
Issue/Introduction
Detailed Description and Symptoms
In Application Manager (AM), you ran the SYSTEM chain to help keep the file system and database from overloading with too much data.
In Automic V9.00, there is not SYSTEM chain. How do you remove older data from my UNIX Automation Engine?
Environment
Release: 9.0
Component: Automation Engine
Resolution
In AM the SYSTEM chain had two jobs:
1. DELDEFAULT - Which cleaned out the reports and output file from the file system on the agent machine after 7 days (by default)
2. HISTORY_PURGE - Which removed the previous run of the job from history within the database. By default we stored 60 days of data in the database.
In Automic V9.00 and Operations Manager the reports of the jobs are stored in the database, not within the file system on the machine. So there are no files to remove. Automic V9.00 and Operations Manager do have the option to store the reports and output files on the file system, but is not set by default. If you are storing file on the OS itself, you will need to manager the directories outside of Automic.
In Automic V9.00 and Operations Manager, there are three major jobs to run to help keep the database clean, Archive, Reorganization and Unload. Each one of these program will need to be run per client.
Archive - The utility Automic.DB Archive serves to archive messages, statistics and reports. The generated files are clearly structured in folders, thereby distinguishing clients and archiving runs. As folder names also contain the corresponding dates, it is easier to locate particular data records.
Archived data can be viewed with the Archive Browser at any time. Set filters to limit the number of data records to be displayed depending on your requirements.
Reorganize - Use the utility Automic.DB Reorg for the subsequent reorganization of data records. These are marked with deletion markers in this step but are not yet deleted from the database!
Unload - Call the utility Automic.DB Unload to finally erase the data records from the database. Use the option "Reorganize database". If necessary, this utility can also be used for resetting archive and reorganization flags.
When a GSO consultant is on site installing the instance, they will normally set up a Maintenance folder and process flow to help maintenance the system. If you already have this set up, then you should see a schedule running called JSCH.MAINTENANCE.ARCHIVE.REORG.UNLOAD. If you do not have this set up in your instance, please follow the instructions below.
1. If you have not run the Archive Utility for a while or have never run this utility, please call Automic Support for help with the best way to run the Archive, Reorg and unload to get the database down to the date you want.
2. Create a new folder in your client called MAINTENANCE.
3. Import the attached file into the new MAINTENANCE folder.
4. Edit the JOBI.MAINTENANCE object.
- a. Replace <Directory where Oracle is installed> with the actual directory of where the Oracle is installed. If you are using DB or another database, please call support.
- b. Replace <Directory where Automic is installed> with the directory of where you have the Automic files installed and where the Utility directory is going to be located.
- c. Check the your PATH environment veriable on the machine. Copy the directories and replace it over <The path that is set for your Automic instance>. If you get an error U4006586 (The compound line is too long) then break the line into multiple lines. Please a question mark "?" behind eack line. Ex:
PATH=$UC4/bin:/u01/users/qa4/uc4/om8/jdk1.6.0_17/bin:?
/usr/lib64/qt.3/bin:/usr/kerberos/bin:/usr/local/bin:?
/bin:/usr/bin:/u01/users/qa4/bin;export PATH
- d. Replace the <The LD_LIBRARY_PATH that is set for your Automic instance> with what you may currectly have set. If LD_LIBRARY_PATH is not set. Then set the line line:
LD_LIBRARY_PATH=$UC4/bin; export LD_LIBRARY_PATH
5. Edit the JOBS.UNIX.ARCHIVE.CLIENT.0 object. Replace <Directory where your Automic instance is install> with the directory of where you have the Automic files installed and where the Utility directory is going to be located.
6. Edit the JOBS.UNIX.REORG.CLIENT.0 object. Replace <Directory where your Automic instance is install> with the directory of where you have the Automic files installed and where the Utility directory is going to be located.
7. Edit the JOBS.UNIX.REMOVE.ARCHIVE.FILES object. Replace <Directory where your Automic instance is install> with the directory of where you have the Automic files installed and where the Utility directory is going to be located.
8. Edit the JOBS.UNIX.REMOVE.REORG.FILES object. Replace <Directory where your Automic instance is install> with the directory of where you have the Automic files installed and where the Utility directory is going to be located.
9. Edit the JOBS.UNIX.UNLOAD.ALL.CLIENTS object. Replace <Directory where your Automic instance is install> with the directory of where you have the Automic files installed and where the Utility directory is going to be located.
10. The JOBS.UNIX.ARCHIVE.CLIENT.100 is an example of other clients you may have in your system. You can rename and/or copy this job to match the client you have. Ex:
You have a client 50, rename the existing job JOBS.UNIX.ARCHIVE.CLIENT.100 to JOBS.UNIX.ARCHIVE.CLIENT.50. Then edit the job, replace <Directory where your Automic instance is install> with the directory of where you have the Automic files installed and where the Utility directory is going to be located. Also change "-s0100" to "-s0050"
11. The JOBS.UNIX.REORG.CLIENT.100 is an example of other clients you may have in your system. You can rename and/or copy this job to match the client you have. Ex:
You have a client 50, rename the existing job JOBS.UNIX.REORG.CLIENT.100 to JOBS.UNIX.REORG.CLIENT.50. Then edit the job, replace <Directory where your Automic instance is install> with the directory of where you have the Automic files installed and where the Utility directory is going to be located. Also change "-s0100" to "-s0050"
12. Edit the JOBP.MAINTENANCE object. Currently the process flow only holds the jobs for CLIENT 0 and CLIENT 100. If you renamed JOBS.UNIX.ARCHIVE.CLIENT.100 and JOBS.UNIX.REORG.CLIENT.100, then the jobs in the process flow will also be changed. If you copied JOBS.UNIX.ARCHIVE.CLIENT.100 and JOBS.UNIX.REORG.CLIENT.100 to new jobs for additional client, you will need to add those jobs to your process flow.
13. Once everything is set up and ready to go, all you need to do is launch the JSCH.MAINTENANCE.ARCHIVE.REORG.UNLOAD schedule.
Attachments
Feedback
