Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Export involving external database failing from prpcUtils



Trying to extract a product using the command line utility.

Within the product is a DATA-ADMIN-DB-NAME rule and corresponding DATA-ADMIN-DB-TABLE rules related to an external database.

In the file, user requires a way to specify the database details for the external database.

Error Messages

Not Applicable

Steps to Reproduce

Run ./ exportRAP

Root Cause

A defect or configuration issue in the operating environment.

The auto-generated and prconfig.xml file that are generated by prpcUtils only specify the PegaRULES and PegaDATA database information.

For an external database one must provide a version of these files that includes the external datasource.


Perform the following local-change steps:

1. Start with the auto-generated versions of the and prconfig.xml from the previous run of prpcUtils.

2. In the copy of prconfig.xml, specify the database credentials for the external database.
The name in the properties needs to match the name from DATA-ADMIN-DB-NAME rule. In this example the name is MYEXTERNALDB

3. In the prconfig.xml, observe an entry for url, username, password, defaultSchema for PegaRULES and PegaDATA.

4. Make the same entries for the external database MYEXTERNALDB. The name part of the entries will be as mentioned below and fill in the appropriate value for each:

<env name="database/databases/MYEXTERNALDB/url" value="jdbc:oracle:thin:@xxx" />
<env name="database/databases/MYEXTERNALDB/userName" value="xxx" />
<env name="database/databases/MYEXTERNALDB/password" value="xxx" />
<env name="database/databases/MYEXTERNALDB/defaultSchema" value="xxx" />

5. Then in the file around lines 47 and 48 one might see properties to specify the location of the prconfig and prbootstrap files.

Uncomment those lines and set them to the location of the files:

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

Suggest Edit

Published July 25, 2017 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us