Siebel Database Upgrade Guide for DB2 UDB for z/OS > Upgrading the Target Database >

Restarting Upgrade Jobs That Fail

Upgrades: All upgrades.

Environments: All environments.

This topic is part of an upgrade process. See How to Perform a Siebel Database Upgrade.

This topic describes how to restart mainframe upgrade jobs that fail.

To restart a mainframe upgrade job that fails

1. Identify the job that failed under the SDSF exit (job status).

   You can find the name of the job that failed using one of the following options on the In-Place Upgrade 8.0 Main Menu:

   • Option 5: Staging Database Joblog
   • Option 6: Target Database Joblog

     See Running SQL in Siebel Logs for further information.

2. Determine the reason the job failed. You can determine the reason for the job failure by selecting the job on the SDSF output queue panel using the s action character.
3. Correct the problem.

   If a job fails because of an SQL error, fix the problem in the appropriate SQL PDS member. For example, for PRESCHM jobs, you can locate the relevant SQL PDS member in the DSNHLQ.SIEBEL.PRESCHM.SQL data set.

   NOTE:  If you need help in performing these tasks or if you require confirmation that the tasks that you are about to run are correct, create a service request (SR) on My Oracle Support.

4. Once the problem has been identified and corrected, restart the job. You can do this by selecting the job that failed on the SDSF output queue using the SJ action character. This will automatically call up the next scheduled job allowing the upgrade process, for example PRESCHM, to continue.