I have a pega 24.1 install on an OpenShift container platform using an oracle database, and am also using Harness for the deployment. I have already created the Oracle schemas for Rules and Data, and I want the installer to bypass the schema generation when the installer runs. In the last there was a way to bypass schema generation by updatting the setupDatabase.properties file if I was installing on a linux server, but now we are using a container environment, and I dont see where I can set this. The helm charts dont seem to have a parameter for bypassing this. Any advice on how I can do this?
Set Pega to skip DDL/schema creation by setting bypass.pega.schema=true in setupDatabase.properties, then inject that file into the installer job via the Helm chart. Create a ConfigMap that contains your customized setupDatabase.properties with your Oracle connection, rules/data schema names, and bypass.pega.schema=true. In your pega/pega values.yaml, use the installer.custom volume/volumeMounts to mount that ConfigMap over the installer path where scripts/setupDatabase.properties is read (typically /opt/pega/kit/scripts/setupDatabase.properties). Redeploy the installer job with this values.yaml so it uses your file and does not generate or apply schema DDL. Keep your runtime tier pointing at the already-created RULES and DATA schemas via jdbc URLs and schema names. If you ever need DDL again, remove the override or set bypass.pega.schema=false. For reference, bypass.pega.schema is the documented flag to skip schema creation and UDF generation in setupDatabase.properties
@Sairohith this worked perfectly. Thank you very much