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

Pega UVU - Batch - Log File Error - Unable to initialize tables



When extracting case-based usage data from PRPC Application database (Oracle), the batch edition of the Pega UVU fails when encountering specific work types, such as BD-FW-AP-Work-Archive.

Error Messages

2015-05-15 23:10:48,840 [ main] [ ] [ ] (gine.database.UsageClassDetail) ERROR - Unable to initialize tables for BD-FW-AP-Work-Archive
2015-05-16 00:27:28,473 [ main] [ ] [ ] (gine.database.UsageClassDetail) ERROR - Unable to initialize tables for BD-FW-AP-Work-TAX Database-BadDBDef-Missing workApp
From: (unknown)
at com.pega.pegarules.engine.database.ConnectionManager.getDBConfig(
at com.pega.pegarules.engine.database.ConnectionManager.getConnection(
at com.pega.pegarules.engine.database.ConnectionManager.getConnection(
at com.pega.pegarules.engine.database.ThreadConnectionStore.getConnection(
at com.pega.pegarules.engine.database.TableInformationMap.lookupTableInfo(
at com.pega.pegarules.engine.database.TableInformationMap.get(
at com.pega.pegarules.engine.database.TableInformationMap.get(
at com.pega.pegarules.engine.database.UsageClassDetail.initializeTable(
at com.pega.pegarules.engine.database.UsageClassDetail.<init>(
at com.pega.pegarules.engine.database.UsageClassImpl.initialize(
at com.pega.pegarules.engine.database.UsageValidation.main(

Steps to Reproduce

Run the batch-edition of the Pega UVU against PRPC Application database.

Root Cause

The root cause of this problem is an error/omission in product documentation. The reason the UVU utility fails for some runs is because the application has Class records such as 

that are mapped to database tables present in external Database (Data-Admin-DB-Name) "workApp".


This issue is resolved through the following local change:

Define a pegarules database connection in the prconfig.xml file in use by UVU for each of these external databases. Here is an example:

                <env name="database/drivers" value=";oracle.jdbc.OracleDriver" />
                <env name="database/databases/PegaRULES/url" value="jdbc:oracle:thin:@PegaRULES-Host:1521:prpc62sp2" />
                <env name="database/databases/PegaRULES/userName" value="<username>" />
                <env name="database/databases/PegaRULES/password" value="<password>" />
                <env name="database/databases/workApp/url" value="jdbc:oracle:thin:@EXTDB-Host:1521:DBName" />
                <env name="database/databases/workApp/userName" value="<username>" />
                <env name="database/databases/workApp/password" value="<password>" />

In the above example, the assumption is that there is a Data-Admin-DB-Name record named "workApp". You'd need similar configuration updates for other Data-Admin-DB-Name records that fail with this error.

Published July 9, 2015 - Updated October 8, 2020

Was this useful?

0% found this useful

Have a question? Get answers now.

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

Did you find this content helpful?

Want to help us improve this content?

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