Displaying Actions

You can display all the information about actions in the DBA Planning Calendar.

?     Status of an action

?     Action Parameters

?     Repeat patterns

?     Job logs, for actions already executed

?     Program logs

The status of an action is displayed by the color of the calendar cell in the DBA Planning Calendar containing the action.

Procedure

Open the DBA Planning Calendar (Setting Up and Using the DBA Planning Calendar).

Displaying the Status of a Day’s Actions

...

       1.      Double-click on the header for a particular day.

The result list appears. All scheduled actions are displayed.

Failed or interrupted actions are highlighted red in the DBA Planning Calendar. If all the actions on a given day contained errors or were interrupted, that day’s header cell is also highlighted red.

       2.      To display another day, select a new one by double-clicking on the calendar control in the left screen margin.

Displaying a Scheduled Action

       3.      Double-click on the calendar cell containing the desired action or position the cursor on the calendar cell and select Action Details.

       4.      A dialog box appears displaying detailed information about the action. The Action Description group box displays information about the scheduling and status of the action.

Action Parameters

Depending on the action selected, different action parameters are displayed here.

Repeat

This tab page is only displayed if the action is part of a repeating action.

Job Log

The job log for the background processing generated by the action is displayed. All messages written by the background job are also displayed.

To display any long texts, double-click on the message.

Program Log

Some actions write program logs on the database computer. If there is such a program log, it is displayed on this tab page.

Log and action timestamps are used to associate database logs and scheduled actions. An action log is assigned to the action that has the same type and the closest corresponding time stamp. In some cases, for example if no background work process is available, the action is delayed and maybe even postponed until the next scheduled time. This unfortunately means that the action log is then assigned to the next scheduled time, making the original scheduled time incorrect. This is the case when the logs of preceding schedulings are displayed for the next scheduled action of the same type.

Troubleshooting

Every scheduled action can, in exceptional cases, fail. You should therefore perform daily checks of at least the critical actions, such as database backups.

       5.      Use the job log to check if the background job was executed correctly. If no job log exists, the background job was probably not started.

To find out about other details, call transaction Simple Job Selection (transaction SM37) and display the job overview ( Managing Jobs from the Job Overview).

The names of jobs scheduled in the DBA Planning Calendar always begin with DBA. The job log also tells you whether an external program was started.

       6.      Once you have established that the background job was executed successfully, call up the job or program log (if available).

       7.      After you have fixed the error, restart the action manually. Choose Execute. Make sure the action does not conflict with other planned actions.

See also:

Starting an Action Immediately