Support Article
Pega UVU - Batch - Log File Error - Unable to initialize tables
SA-10466
Summary
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
and
2015-05-16 00:27:28,473 [ main] [ ] [ ] (gine.database.UsageClassDetail) ERROR - Unable to initialize tables for BD-FW-AP-Work-TAX
com.pega.pegarules.pub.database.BadDatabaseDefinitionException: Database-BadDBDef-Missing workApp
From: (unknown)
at com.pega.pegarules.engine.database.ConnectionManager.getDBConfig(ConnectionManager.java:2024)
at com.pega.pegarules.engine.database.ConnectionManager.getConnection(ConnectionManager.java:880)
at com.pega.pegarules.engine.database.ConnectionManager.getConnection(ConnectionManager.java:842)
at com.pega.pegarules.engine.database.ThreadConnectionStore.getConnection(ThreadConnectionStore.java:369)
at com.pega.pegarules.engine.database.TableInformationMap.lookupTableInfo(TableInformationMap.java:360)
at com.pega.pegarules.engine.database.TableInformationMap.get(TableInformationMap.java:299)
at com.pega.pegarules.engine.database.TableInformationMap.get(TableInformationMap.java:261)
at com.pega.pegarules.engine.database.UsageClassDetail.initializeTable(UsageClassDetail.java:87)
at com.pega.pegarules.engine.database.UsageClassDetail.<init>(UsageClassDetail.java:65)
at com.pega.pegarules.engine.database.UsageClassImpl.initialize(UsageClassImpl.java:460)
at com.pega.pegarules.engine.database.UsageValidation.run(UsageValidation.java:549)
at com.pega.pegarules.engine.database.UsageValidation.main(UsageValidation.java:1211)
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
BD-FW-AP-Work-Archive
BD-FW-AP-Work-TAX
that are mapped to database tables present in external Database (Data-Admin-DB-Name) "workApp".
Resolution
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="com.microsoft.jdbc.sqlserver.SQLServerDriver;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
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.