Troubleshooting (DB2 UDB for UNIX and Windows) 

Use

Any scheduled action can occasionally fail, so you must at least check the more critical actions such as database backups.

Procedure

...

       1.      To check whether the background job was executed correctly, you can consult the job log. If no job log exists, the background job was probably not started.

For more details, call transaction SM37 and display the job overview.

The names of all jobs scheduled in the DBA Planning Calendar start with DBA. The job log will also tell you whether an external program was started.

       2.      If you are sure that the background job ran successfully, consult the job log or program log (if one is available).

       3.      Once the error has been corrected, execute the action manually using  Execute, making sure there are no clashes with other scheduled actions.