Search this product 

 Menu

CA Workload Automation AE & Workload

Control Center
Documentation powered by DocOps

 Home /  Administrating /  AE Administration /  Maintain the Event Server

General Database Maintenance

Last update January 30, 2017

Periodic database maintenance helps ensure that CA Workload Automation AE is working correctly. Each run of each job generates
several events. If you do not remove these events from the database periodically, the database eventually reaches its size limit,
bringing CA Workload Automation AE and its jobs to a halt. Therefore, periodic database maintenance is recommended.

Automate Database Maintenance

You can automate the database maintenance using the DBMaintTime and DBMaintCmd parameters. The scheduler performs internal
database maintenance once a day. Event processing is slowed down during maintenance. We recommend that you schedule the
maintenance during low processing times. For environments where DBMaint starts becoming disruptive, we recommend that you
minimize the impact by running DBMaint multiple times per day so that the processing is spread over multiple shorter periods as
opposed to a single longer duration.

How the DBMaint.bat Batch File or DBMaint Script Runs

By default, CA Workload Automation AE runs the DBMaint script on UNIX or the DBMaint.bat batch file on Windows during the daily
maintenance cycle. The DBMaint command runs the dbstatistics, archive_events, and archive_jobs commands to perform
maintenance on the CA Workload Automation AE database.

The DBMaint command runs the dbstatistics command to perform the following tasks:

Update statistics in the database for optimal performance. For Oracle and Sybase databases, it computes statistics for all the
tables.

Run the dbspace command to check the available space in the database. If the amount of free space is insufficient, the
dbspace command issues warning messages and generates a DB_PROBLEM alarm.

Note: The DB_PROBLEM alarm is issued if the database space exceeds the value specified in the
DBSPACE_ALARM_SPACE environment variable. The default value is 1000 MB.

Calculate and update the average job run statistics in the ujo_avg_job_run table. When the dbstatistics command runs, it
overwrites old data with the new data.
The DBMaint command runs the archive_events command to remove old information from various database tables. Specifically, the
archive_events commandSearch
removes theproduct
this following: 
 Menu
Events and associated alarms from the ujo_event table

Job run information from the ujo_job_runs table

autotrack log information from the ujo_audit_info and ujo_audit_msg tables

The DBMaint command runs the archive_jobs command to delete obsolete job versions from the database tables. It specifically
removes the obsolete information from the job type database tables.

The output from the DBMaint command reports the amount of space remaining in your database so you can monitor whether the
event tables are filling up. By monitoring these values, you can calculate how many events you can safely maintain in a day before
archiving.

Note: For more information about the DBMaint, dbspace, dbstatistics, archive_events, and archive_jobs commands, see AE
Commands.

(UNIX) Modify the DBMaint Script

You can modify the $AUTOSYS/bin/DBMaint script. For example, you might want to modify the script to perform database backups.

Follow these steps:

1. Make a copy of the $AUTOSYS/bin/DBMaint script and modify the copied version.

2. Log in to CA Workload Automation AE and run the shell that is sourced to use CA Workload Automation AE.

3. Check that the modified DBMaint script is placed in the location specified by the following parameter of the configuration file:

DBMaintCmd=pathed_command

pathed_command

Defines the location of the DBMaint script.

Default: $AUTOSYS/bin/DBMaint

CA Workload Automation AE uses the modified DBMaint script to perform database maintenance.

Note: When you upgrade from Unicenter AutoSys JM r11 to CA Workload Automation AE r11.3, Release 11.3.5, or Release 11.3.6
you will not lose the changes you made in the copied version. You can modify the DBMaint script that is installed when you
upgrade to CA Workload Automation AE r11.3, Release 11.3.5, or Release 11.3.6 to match your copied version.

(Windows) Modify the DBMaint.bat File

You can modify the %AUTOSYS%\bin\DBMaint.bat file. For example, you might want to modify the batch file to perform database
backups.

Follow these steps:

1. Make a copy of the DBMaint file and modify the copied version.
 2. Click Start, Programs, CA, Workload Automation AE, Administrator.
Search this product
The Instance - CA Workload Automation AE Administrator window opens.

 Menu
3. Select an instance from the Instance drop-down list.

4. Click the Scheduler icon on the toolbar.

The Scheduler - CA Workload Automation AE Administrator window appears.

5. Click the Database Maintenance tab, enter the location of the modified DBMaint.bat batch file in the Command field, and click
Apply.

CA Workload Automation AE uses the modified DBMaint script to perform database maintenance.

Note: When you upgrade from Unicenter AutoSys JM r11 to CA Workload Automation AE r11.3, Release 11.3.5, or Release 11.3.6,
you will not lose the changes you made in the copied version. You can modify the DBMaint file that is installed when you upgrade
to CA Workload Automation AE r11.3, Release 11.3.5, or Release 11.3.6 to match your copied version.

0 Comments 

Privacy Legal Data Processing/Transfers Site Map Powered by Atlassian | Scroll Viewport
Copyright © 2019 Broadcom. All Rights Reserved. The term “Broadcom” refers to Broadcom Inc. and/or its subsidiaries.