Setup
of the DBA Planning Calendar (DB2 UDB for UNIX and Windows) 
When you start your system for the first time, there are no actions planned in the DBA Planning Calendar.
For proper operation of your database, you need to perform certain tasks involving a minimum number of regular actions. The following actions are currently available in the DBA Planning Calendar for DB2 UDB for UNIX and Windows:
|
Task Area |
Actions Involved |
|
Backup and recovery of the database |
Full Database Backup into TSM Full Database Backup to Device Full Database Backup with Vendor Library Initialize Tape in Device
These actions are only available for RFC-monitored systems. |
|
Archiving of log files |
Archive Inactive Log Files to Device Archive Inactive Log Files with TSM
These actions are only available for RFC-monitored systems. |
|
Running statistics for tables |
Check Tables for Statistics Update RUNSTATS and REORGCHK (DBSTATC) RUNSTATS and REORGCHK for all Tables RUNSTATS and REORGCHK for Single Table |
|
Reorganization of tables and tablespaces |
REORG and RUNSTATS of Flagged Tables REORG of Tables in Tablespace(s) REORG and RUNSTATS for single Table Automatic REORG REORGCHK for all Tables (only available for RFC-monitored systems or if the system monitored using a remote database connection is an ABAP-based SAP system) |
The actions involved in Backup and recovery of the database and Archiving of log files have an impact on the availability of the database.
The actions involved in Running statistics for tables and Reorganization of tables and tablespaces have an impact on the performance of the database.
Most actions that you can plan using the DBA Planning Calendar should normally be scheduled as a recurring action. You can set up your DBA Planning Calendar using the pattern setup function described below. You should be aware of the fact that there are some dependencies between actions which need to be considered:
· Action RUNSTATS and REORGCHK (DBSTATC) depends on data provided by action Check Tables for Statistics Update. If Check Tables for Statistics Update is not planned, the action will not work properly.
For more information, see Update Statistics.
· Action Initialize Tape in Device should always be followed by action Archive Inactive Log Files to Device.
You must check the DBA Planning Calendar daily to be sure that scheduled actions have been executed correctly.
You can start the DBA Planning Calendar by calling the DBA Cockpit and choosing Jobs ® DBA Planning Calendar in the navigation frame of the DBA Cockpit.
On the initial screen, you can select a predefined action from the Action Pad. Whenever you add a new action, it is proposed to run once. You can schedule, change, and delete actions according to your requirements.
Pattern Setup
You can use the pattern setup function to schedule actions that are recommended to be run regularly.
On the initial
screen of the DBA Planning Calendar, choose 
Pattern
Setup. The Add Planning Patterns dialog box appears
providing a list of actions that you can schedule with this function.
A set of recommended actions is already preselected by default. You may change this selection set, for example, if you want to use TSM for backup and archiving instead of backup and archive to devices.
To proceed, choose
Next. The system now displays one action after the other
and provides the options to define the recurrence pattern and to change the
parameters of an action. You can navigate between the selected actions by
choosing Next or 
Previous.
Once you have made
your choices for the selected actions, confirm your entries by choosing
Save on the last screen.
Some of the actions do have an impact on the performance and availability of your system. You should carefully check the proposed start times of the scheduled actions to guarantee good performance and availability of your system.
Keep in mind that there are a number of database-related jobs that are not controlled by the system but which you must take into account when scheduling regular actions. The jobs involve:
· Collection of database performance history data done every two hours starting at 00:00
· Monitoring of database and database manager configuration changes done daily on 8.00 am, 01.00 pm and 7.00 pm
· Collection of database and tablespace history data done daily at 7:00 am and 8.00 pm
· Collection of tables and indexes space history data done weekly on Sunday at 12.00 pm
Authorization Checks
To make sure that database administration actions are secure, authorization checks must be made for certain operations as follows:
· SAP system
You need authorization for database administration and background job scheduling. This is provided by the profiles S_RZL_ADMIN and S_BTCH_ALL.
External programs must be able to run on the database server so that actions affecting the database can be performed from other application servers.
· Database system
Some actions require authorization to connect to the database. Others, such as online backup, require even higher levels of authorization.
Before scheduling database backups, see the information on how to back up the database in the documentation SAP Database Administration Guide: IBM DB2 Universal Database for UNIX and Windows.
· Hardware
The number of tapes required depends on the backup strategy you decide to use. The tapes must already be in the specified tape drive or tape changer, so that the operator does not have to interrupt scheduled backup runs.
Different tape drives are needed if logs are to be archived with periodic database backups.
You cannot perform all of the actions required for database administration from the DBA Planning Calendar. For help with actions that you must perform with the SAP system down, see the documentation SAP Database Administration Guide: IBM DB2 Universal Database for UNIX and Windows.
See also:
· Displaying the Status of a Day’s Actions