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

DB schema name issue for ADM and VBD during DSM installation

SA-10392

Summary



User is installing a new Pega 7.1.7 + DSM + NBAM 7.1.2 environment in preparation of migrating existing PRPC 6.x applications to Pega 7.

User is on WebSphere 8.5.5.5 and DB2 9.7 FP7 on AIX.

For maximum flexibilty, the following schemas have been created with their own tablespaces:

PEGA_DATA
PEGA_RULES
PEGA_ADM
PEGA_IH
PEGA_PAD
PEGA_VBD
PEGA_NBAM

After installing ADM and VBD, the WebSphere log files show that the DB connection is using <DB2_USER>.<TABLE_NAME> instead of <SCHEMA>.<TABLE_NAME> for ADM and VBD.

Disabling the startup of both the ADM.ear and VBD.ear files prove that the server starts up with no errors.

The problem may be due to incorrect logic in the application.
For Oracle, the schema and user names are the same, but this is not the case for DB2.

Error Messages



org.springframework.jdbc.BadSqlGrammarException: PreparedStatementCallback; bad SQL grammar [select pzCollectionName, pzConfigurationData from PR_DATA_VBD_COLLECTION_CONFIG where pzCollectionName=?]; nested exception is com.ibm.db2.jcc.am.SqlSyntaxErrorException: "ABC.PR_DATA_VBD_COLLECTION_CONFIG" is an undefined name.. SQLCODE=-204, SQLSTATE=42704, DRIVER=4.14.113; nested exception is org.springframework.beans.factory.BeanCreationException: Error creating bean with name 'vbdConfiguration' defined in class path resource [vbd-service-config.xml]

AND

[5/21/15 16:10:50:056 CEST] 00000083 O UOW= source=SystemOut org=null prod=null component=null thread=[server.startup : 0]
16:10:50.044 [server.startup : 0] ERROR com.pega.decision.adm.client.ADMException - Exception occured within ADM with message: "ABC.SETTINGS" is an undefined name.. SQLCODE=-204, SQLSTATE=42704, DRIVER=4.14.113
com.pega.decision.adm.client.ADMException: "ABC.SETTINGS" is an undefined name.. SQLCODE=-204, SQLSTATE=42704, DRIVER=4.14.113


Resolution



Use schema name explicitly in JDBC URL for respective Datasources in DB2:

jdbc:Db2://<HOST>:<PORT>/<DATABASE>:currentSchema={SCHEMA_NAME};

Published June 12, 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