Example Output for Running PostInstallDBSetup

This topic is part of Updating the Siebel Database Using the PostInstallDBSetup Utility.

The examples that follow show the type of output you can expect from running PostInstallDBSetup:

Example 1: Running PostInstallDBSetup
Example 2: PostInstallDBSetup Has Already Run

Example 1: Running PostInstallDBSetup

This example uses a freshly installed sample database for Siebel CRM 22.4 and the PostInstallDBSetup process from the Siebel CRM 22.6 image. All commands must be entered on one line.

docker run --rm -u 1000 --network siebelnet --envfile PostInstallDBSetup-19.list -v /scratch/persistent/PV/ENT/SES:/persistent --entrypoint /bin/bash store/oracle/siebel:22.6 /config/PostInstallDBSetup.sh

Write access confirmed for folder --> /persistent

The next two lines returned are errors that repeat for each language you are not using and can be safely ignored. These two lines are followed by information about the execution status.

mv: cannot stat '/siebel/mde/siebsrvr/bin/csy/omdefs_sia.run': No such file or directory
ln: failed to create symbolic link '/siebel/mde/siebsrvr/bin/csy/omdefs_sia.run': No such file or directory

[SIEBELDB]
Stage 1 of 3 : Running WSRanking
WSRanking script has already been run on this environment
Stage 2 of 3 : Running SeedSchemaManifest Upgrade
Stage 3 of 3 : Running Workflow DR Upgrade and Migration
****************************SUMMARY*******************************************
Execution of WSRanking is Not applicable.
SeedSchemaManifest Execution Completed Successfully.
Workflow DR Upgrade and Migration completed successfully
******************************************************************************
PostInstallDBSetup Execution HTML Report Location : /siebel/ses/siebsrvr/log/PostInstallDBSetup_2022-05-19_12-04-05.html
real 3m50.899s
user 2m41.013s
sys 0m45.513s

This example uses the PostInstallDBSetup-19.list set of environment variables shown in Using the PostInstallDBSetup-19.list File. The process first confirms access to the persistent volume. It then makes sure that the siebsrvr/sys/.odbc.ini file has an appropriate configuration for talking to the database by creating a driver and reference if necessary. In this example, those references were already present, as you can see in the two output lines starting with SIEBELDB and [SIEBELDB], as they are located with the grep command. After this check, PostInstallDBSetup.ini is populated with the contents supplied from PostInstallDBSetup-19.list and execution starts.

At the end of the execution, a reference is given to the summary log file (in HTML format), which you can review for more details on the process. Because the siebsrvr/log file is persisted, you can find this log file in the persistent directory referenced by your command.

In this example, the command ran with -v /scratch/persistent/PV/ENT/SES:/persistent, and so the actual log content is located in a log file similar to /scratch/persistent/PV/ENT/SES/siebsrvr/PostInstallDBSetup_2022-05-19_12-04-05.html.

Finally, the process provides an indication of how long the process took: in this case, just under four minutes.

Example 2: PostInstallDBSetup Has Already Run

The output in this second example is what you can expect when running the process a second time and with all the same properties (that is, running it unnecessarily). This time, the system quickly determines that execution is unnecessary and quits. All commands must be entered on one line.

docker run --rm -u 1000 --network siebelnet --envfile PostInstallDBSetup-19.list -v /scratch/persistent/PV/ENT/SES:/persistent --entrypoint /bin/bash store/oracle/siebel:22.6 /config/PostInstallDBSetup.sh

[SIEBELDB]
'PostInstallDBSetup' database final configuration is not required on this instance as 
it has already been executed in a prior install.

real 0m3.109s
user 0m1.907s
sys 0m0.468s