Troubleshooting: Oracle 
On rare occasions, an action planned using the DBA Planning Calendar may not execute correctly, for a variety of reasons. You should therefore perform daily checks of at least the critical actions, such as database backups.
To find out why the failure occurred:
Was the background job executed correctly?
Consult the job log. If no job log exists, the background job was probably not started. You can get more details using the job overview in Transaction
SM37
(note that the names of all jobs scheduled in the Calendar start with
DBA...
). The job log will also tell you whether an external program was started.
Consult the action log (if one is available) if you are sure that the background job ran successfully.
If available, also display the detail log. This log contains details of the external program, and any errors which occurred during execution.
After you have fixed the error, restart the action manually. Choose Start immediately. Make sure the action does not conflict with other planned actions.
For more information, see
Checking the Results of Actions: OracleCommon errors when using a tape drive include:
No tape inserted in the tape drive
The tape in the tape drive is write protected.
The tape in the tape drive has not been initialized.
The tape drive contains the wrong tape.
The tape is already full
An error has occurred in the tape drive
For more information, see
BC SAP Database Administration: OracleBackup on a standalone Windows NT database server
You must activate the
SAP Gateway
, before starting a backup on a standalone Windows NT database server, using BRBACKUP. Do the following:- Choose Tools ® System administration ® Administration ® Network ® RFC destinations.
Alternatively use Transaction SM59.
- Click + to open the
TCP/IP connections
node.
Double-click
SAPXPG_DBDEST<hostname>
Choose Destination ® Gateway optionsSpecify a
Gateway host
and a
Gateway service
Choose O.K. and save the transaction.