SA-27805

Summary

Execution of exportRAP through prpcUtils.sh displays error in log resulting in failure to export schema for external database tables.

Error Messages

**Date and time**,748 [ your_host] [ STANDARD] [ PegaRULES:06.03] ( internal.util.MoveLog) INFO
JSR94|Deployment|Utility|pxExportApp|AE82D7DB284B081D4C1881C65C8606388 - Error: Database-BadDBDef-Missing your_DB1 (DATA-ADMIN-
DB-TABLE YOUR_CLASS)
**Date and time**,752 [ your_host] [ STANDARD] [ PegaRULES:06.03] ( internal.util.ExportImpl) ERROR
JSR94|Deployment|Utility|pxExportApp|AE82D7DB284B081D4C1881C65C8606388 - Unable to add Schema for class Data-Admin-DB-Table
com.pega.pegarules.pub.database.BadDatabaseDefinitionException: Database-BadDBDef-Missing your_DB2
From: (AE82D7DB284B081D4C1881C65C8606388:Deployment)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getDBConfig(ConnectionManagerImpl.java:2287)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:1075)
at com.pega.pegarules.data.internal.access.ConnectionManagerImpl.getConnection(ConnectionManagerImpl.java:977)
.
.
.

Steps to Reproduce

Run ./prpcUtils.sh exportRAP script.

Root Cause

prpcUtils.sh generates new prbootstrap.properties and prconfig.xml during runtime, thus external database connection information cannot be added to them prior to the script execution.

Resolution

1. In prpcUtils.properties file, uncomment these properties, and set them to the location of the files that can be modified:

# Use the following properties If you want to use a
# custom prconfig.xml or prbootstrap.properties file
pegarules.config=/nba/pega/config/prconfig.xml
prbootstrap.config=/nba/pega/config/prbootstrap.properties

2. In the prbootstrap.properties file, provide PegaRULES database connection details and a temp location.
3. In prconfig.xml, add the connection details for external databases.

<env name="database/databases/YOUR_DB/url" value="jdbc:oracle:thin:@your_dbhost:your_port:your_db1" />
<env name="database/databases/YOUR_DB/userName" value="your_username" />
<env name="database/databases/YOUR_DB/password" value="your_password" />