Reviewing the PostInstallDBSetup Execution Status

A PostInstallDBSetup job is run as part of the deployment pipeline. It is run as a Kubernetes job. The failure of this job does not stop the deployment and the application execution. However, you are advised to check the logs to confirm that PostInstallDBSetup ran successfully. In case of failure, take appropriate corrective action, as described in Siebel Database Upgrade Guide on Siebel Bookshelf. This topic is part of Troubleshooting a Siebel Cloud Manager Instance or Requested Environment.

Before checking the PostInstallDBSetup execution, first set up the kubectl CLI. Connect to the SCM container and set the profile for your environment, as follows:

sudo podman exec -it cloudmanager bash

source /home/opc/siebel/<env_id>/k8sprofile 

Next, run kubectl commands to find the PostInstallDBSetup job pod for which you will run the logs command. First run a command like this:

kubectl -n <env_name> get pods | grep postinstall

Example output:

postinstalldb-q2wnv                  0/1       Completed    0              92m

And then run a command like this:

kubectl -n demo3 logs po/postinstalldb-q2wnv

Example output:

+ /siebel/mde/siebsrvr/bin/PostInstallDBSetup -i /config/PostInstallDBSetup.ini -p
        S1e8eladm1n123 -z SiebelAdmin123 'PostInstallDBSetup' database final configuration is not required on this instance as it has already been executed in a prior install.

real 0m21.438s

user 0m2.504s

sys 0m0.952s

Exit Status : 8

Detailed logs for PostInstallDBSetup can be verified from the persistent folder stored in the file storage service (OCI service). To access this location from the SCM instance, use a command like the following in the same shell in which you connected to the SCM container:

cd /home/opc/siebel/<env_id>/siebfs0/<ENV_NAME_IN_CAPS>/SES/POSTINSTALLDB/siebsrvr/log