Checking the Results of Actions in the DBA Planning Calendar 

Use

This section tells you how to check the results after an action has been executed in the DBA Planning Calendar. For more information see:

·        DBA Planning Calendar (Oracle)

·        DBA Planning Calendar (Informix)

Actions executed in the DBA Planning Calendar generate the following:

·        Action logs

·        Job logs

You can view both of these in the DBA Planning Calendar.

Background jobs are used to schedule actions and these background jobs generate job logs. You can view all the information using the Calendar. In addition, you can view all previous archive and backup actions with the:

·         Display of Backup Logs and Status (Oracle)

·         Archive and Backup Monitor in CCMS (Informix)

Prerequisites

You are ready to use CCMS. For more information, see:

·        Getting Started in  CCMS with Oracle DBA

·        Getting Started in CCMS with Informix DBA

If you started the DBA Planning Calendar using Local Calendar from the Central DBA Planning Calendar, you can check the results of actions for all remote systems running on the same 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 check the results of actions for all other Oracle systems running Oracle version 9. If the action you want to check also runs on Oracle version 8, then you can also check that action for all systems running Oracle version 8.

This only applies if you started the local calendar from the Central DBA Planning Calendar.

Procedure

To display the current state of an action (past, current, or previous) in the Calendar, do the following:

...

       1.      Choose Administration ® CCMS ® DB Administration ® DBA Planning Calendar ® Local to start the DBA Planning Calendar. Alternatively, call transaction DB13.

The system displays the calendar, with a list of actions for each day. The actions are color-coded to indicate status:

Abbreviation	Color	Status
SCHED	Black	Scheduled
SUCC.	Green background	Successfully completed
WARN.	Yellow background	Warning
START	Orange background	Started
UNKN.	Red	Unknown
ERROR	Red background	Error

The headers for each day are color-coded as follows (the text color is always black):

Background Color	Meaning
Light blue	There is no action scheduled for today, or no action has failed.
Dark blue	At least one action failed today.
Light turquoise	All scheduled actions completed successfully, or no action was executed.
Dark turquoise	At least one executed action failed.

       2.      Choose the day for the action you want to look at by double-clicking the header or selecting the "+" symbol on the header.

The system displays a list of actions for the day you selected. The Log. field is selected if an action log was written.

       3.      Look at the field State for the action.

The values for abbreviation in the table above are possible.

If there is one ERROR in one day, then the header for that day is also highlighted.

       4.      Choose Action Logs to look at the action log.

The system displays the action log, if there is one.

A job log (see next step) contains general information, whereas an action log contains specific information about the database aspect of the action. You normally check the action log. If there is a problem with the job, you should also check the job log.

Action logs are sometimes assigned to a later action than they should be, due to problems with the timestamp used to assign logs to scheduled actions. In some cases the action is delayed and even postponed until after the next scheduling time.

This occurs, for example, if no batch work process is available. An action log is then assigned to the action that has the same type and the closest corresponding timestamp. Unfortunately this means that the action log is then assigned to the next scheduling time and the log for the originally scheduled time is incorrect.

       5.      Choose Job Logs to display the job log for an action. For example, this is recommended if there is a problem.

The system displays the job log.

       6.      Choose Environment ® Backup Logs for the archive and backup monitor, where you can see the results of archives and logical-log backups. For more information, see:

¡        Display of Backup Logs and Status (Oracle)

¡        Using the Archive and Backup Monitor in CCMS (Informix)

       7.      If there is a problem, see:

¡        Troubleshooting in the DBA Planning Calendar (Oracle)

¡        Troubleshooting in the DBA Planning Calendar (Informix)

Result

By checking the results of actions executed in the DBA Planning Calendar, you can make sure that your database is functioning optimally. For example, you can tell if a database backup has failed, fix the problem, and schedule it again immediately. Therefore, you can avoid downtime for your SAP system.