Using the Central DBA Planning
Calendar 
Use
You can use the Central DBA Planning Calendar in the Computing Center Management System (CCMS) to view actions on all the databases of your SAP Systems, both local and remote. For more information, see Central DBA Planning Calendar.
Prerequisites
You have defined the systems to be displayed in the calendar by choosing Configuration. By choosing Configuration ® Take over system, you can use the system definitions stored in the CCMS system repository. This means that you do not have to manually enter all the parameters for a new system, but you can still change or add parameters if required. However, if you want to add a new system manually, choose Configuration ® Add system.
We recommend you to choose one system from which to start the Central DBA Planning Calendar. Using your chosen system, you can regularly update the display for all other systems by scheduling a job to be repeated periodically (for example, at 06:00 every morning).
If you have several systems to manage, it can take some time to refresh the results from all systems.
Before adding a new system to the Central DBA Planning Calendar, do the following on that system:
· Delete all actions
· Lock transaction DB13
Procedure
...
1. Choose Administration ® CCMS ® DB Administration ® DBA Planning Calendar ® Central. Alternatively, call transaction DB13C.
The Central DBA Planning Calendar is displayed. If you have already run or planned actions, you see entries by day, one for each system.
Here is an example of entries for a single day affecting two systems, FUD and FIB:
|
Mo. 07.01.2002 |
|
|
3 FUD |
2 |
|
4 FIB |
1 |
On system FUD for Monday 7th January 2002, there were three actions planned, two of which had the highest status severity. For example, the highest status severity for FUD might be “Warning”, in which case the entry for FUD is displayed with a yellow background. This means that two actions ended with a warning.
On system FIB for the same day, there were four actions planned, one of which ended with the highest severity. For example, the highest severity for FIB might be error, in which case the entry for FIB is displayed with a red background. This means that one action ended with an error.
The following table shows the color-coded statuses in the Central DBA Planning Calendar:
Status |
Color |
Planned |
Black |
Success |
Green background |
Warning |
Yellow background |
Started |
Orange background |
Unknown |
Red |
Error |
Red background |
2. To see a summary of the actions for a day, double-click the day header or place the cursor on the day header and choose Actions.
The system displays a summary of the actions and status for each system on the date you selected, as in the following example:
|
System |
All |
Planned |
Success |
Warning |
Started |
Unknown |
Error |
|
FUD |
3 |
1 |
|
2 |
|
|
|
|
FIB |
4 |
|
3 |
|
|
|
1 |
3. To see the individual actions for a system, double-click the entry for the system or place the cursor on the system and choose Actions.
The system displays the actions for the chosen system on the date you selected, as in the following example for system FUD:
|
StartTime |
Period |
Action |
Status |
Log |
|
06:02:14 |
0 |
Check database |
Warning |
|
|
07:04:00 |
0 |
Verify database |
Success |
|
|
08:05:00 |
0 |
Redo log backup |
Warning |
|
The first entry means that the action to check the database ran at 06:02:14 and finished with a warning. As Period is 0, this means that the action was run once only (that is, it was not one of a series). As Log is not ticked, no action log was produced.
4. To see the action and job logs, display the actions as described in the previous step and choose Action logs or Job logs.
If they are available, the system displays the logs.
5. To refresh the display for the system from which you called the Central DBA Planning Calendar (that is, for the local system), choose Refresh ® Local.
6. To refresh the display for all systems, choose Refresh ® Remote.
There are a number of ways to refresh the display:
Method |
Meaning That the Refresh |
Dialog |
Runs in dialog mode, which can take a long time, so not recommended |
Background |
Runs immediately in the background as a job |
Job log |
Shows the job log for the local system |
Planned job |
Runs daily at the time that you specify |
We recommend that you schedule a planned job to refresh the display for remote systems regularly, as mentioned above in “Prerequisites”.
7. To switch to a local DBA Planning Calendar, choose Local Calendar and select the system for which you want to process actions.
You can now schedule, change, delete, or execute actions on the chosen local calendar.
When you call a local calendar from the Central DBA Planning Calendar, you can process actions for all remote systems running on the same database platform and with the same characteristics. This assumes that you have already defined the remote systems to the Central DBA Planning Calendar.
For example, assume that you call the DBA Planning Calendar from the Central DBA Planning Calendar on system FUD, which runs Oracle version 9. You can then process actions for all other Oracle systems running Oracle version 9. If the action you want to process also runs on Oracle version 8, you can also process that action for all systems running Oracle version 8. However, you can not process actions for other systems – such as MaxDB or an IBM database in this example – from the local calendar on system FUD.
This only applies if you start the local calendar from the Central DBA Planning Calendar.
See also:
The CCMS System
Repository