Upgrade Guide for DB2 UDB for z/OS and OS/390 > Upgrading a Database from the Midtier > Executing SQL Output Files After the Second Pause >

Executing SQL Output Files After the Second Pause - Stage 1 of 2

This section describes stage 1 of how to execute the output files created by the Siebel Upgrade Wizard before the second pause message.

To execute the SQL output files after the second pause

• Execute the SQL output files in the following order from the DB2 command window. See Resuming the Siebel Upgrade Wizard After the Second Pause for execution procedures.

  NOTE:  You may have a subset of these files, because they are produced according to upgrade path and Siebel eBusiness application.

  • schema.sql
  • tmptable.sql

    NOTE:  You only need to run the following echannel SQL files if you are upgrading from a Siebel 6.x application.

  • echannel_merge_contact.sql
  • echannel_merge_org_int.sql

    To create and populate the temporary tables used by echannel_merge_contact.sql and echannel_merge_org_int.sql, go to the dbsrvr\db2390 directory and run the following jobs:

    • eChannelAccountDivMatch.sql
    • eChannelEmpContactMatch.sql

      If you are a Financial Services customer, run the following jobs:

    • eChannelAccountDivMatch_fins.sql
    • eChannelEmpContactMatch_fins.sql.
  • echannel_merge_contact_sia.sql
  • echannel_merge_org_int_sia.sql
  • HHMigPop.sql

    NOTE:  Change the HHMigPop.sql file to reflect your site-specific storage details (such as, storage group and schemaqualifier). Also, since HHMigPop.sql creates objects that are required for Household_Mig_Fins.sql, make sure you run HHMigPop.sql before running Houshold_Mig_Fins.sql.

  • Household_Mig_Fins.sql
  • dev0ftp.txt

    Execute this file as part of the procedure described in Resuming the Siebel Upgrade Wizard After the Second Pause.

  • ftpdev0.bat

    Execute this file as part of the procedure described in Resuming the Siebel Upgrade Wizard After the Second Pause.

    TIP:   To stop the process after every error when executing the output files, add the parameter -s to the command. This will prevent the need to restore your database and rerun the upgrade if you encounter errors due to data dependencies in these jobs.

    After executing the SQL files successfully and reviewing the log files for unacceptable errors, you deploy the stored procedures and user-defined functions as described in Deploying Stored Procedures and User-Defined Functions.