Siebel Database Upgrade Guide for DB2 for z/OS > Performing the Siebel Repository Merge >

Generating the Runtime Repository Data

Upgrades: All upgrades.

Environments: Development environment only.

Once the Incremental Repository merge is complete and after all merge conflicts have been resolved and before starting upgphys you must generate the Siebel Runtime Repository data. To generate the Siebel Runtime Repository data, you must execute the Full Publish command in Siebel Tools. For more information about executing the Full Publish command in Siebel Tools, see Using Siebel Tools.

Full publish has to be executed against the New Customer Repository. Make sure to change the DockRepositoryName in tools.cfg to New Customer Repository and verify that Siebel tools launches against the correct Repository

NOTE:  This is a mandatory step and not executing this successfully will have consequences in the further steps of upgrade.

The full Publish command is the following:

siebdev /c tools.cfg /TL ENU /d ServerDataSrc /u <username> /p <password> /FullPublish

The TL <lang_code> parameter is a mandatory argument for Full Publish because it specifies the published languages for the database. You can add multiple languages separated by a comma. For example:

TL ENU,DEU,JPN

Depending on the number of the languages specified, the Full Publish process spans the number of Siebdev processes to compile objects in the specified language and write the data to the database.

Siebdev silently closes after completion of a Full Publish, which indicates there are no errors. If there are errors during the Full Publish process, the Siebdev process throws errors and stops.

In the log file, Failure Reported For indicates an error with an object. The log file lists the object name and type for Failure Reported For errors. Any Workflow Process errors in the log file can be ignored.