Editing/Deleting Actions (Oracle) 

Use this procedure to change the scheduled time of an action or the command arguments used to execute it (including the names and number of tapes available for the backup or archiving).

You can also delete individual actions. However, you cannot delete all actions of an action pattern as a unit.

Prerequisites

Be sure that the changes you plan to make do not compromise critical database maintenance activities. For example, be sure that you do not alter or delete backup actions in such a way that you are no longer able to recover the database in the event of an error.

Procedure

  1. Select a particular day, for which you want to change or delete an action, by double-clicking the header of the action, or the + hotspot on the header.

    2. Alternatively, select the action you want to change or delete and choose Change action or Delete action.

  2. Select the action and choose Delete action or Change action

    3. Delete action: The system asks you to confirm the deletion. When you do so, the action is deleted from the DBA Planning Calendar. The corresponding background job is also deleted. Deletion of the job also stops automatic periodic repetition of the action, if scheduled. The procedure is finished.

    Change action: The system displays a dialog showing the actions supported by the DBA Planning Calendar. The action you chose is selected. Continue with the rest of this procedure.

  3. Change the start time or repeat period for the action, as required
  4. Choose Parameters, if you want to change the attributes for the action. This allows you to change SAPDBA command arguments, profiles, or tablespaces, or add tapes and so on, depending on the selected action.

    5. Are you changing the number of tapes required for a backup? Then you need to make the change only once. The change is automatically activated for all repetitions of the action.

  5. Choose Continue to finish scheduling the action.

Result

The system checks for conflicts with previously-scheduled activities. If any are found, the conflicts are displayed and the action is not scheduled.

Otherwise the action is added to the Planning Calendar and the required background job is scheduled.