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

Bix throwing fatal errors for some executions

SA-64690

Summary



Business Intelligence  Exchange (BIX) fails for some executions and data is not fetched for that run. BIX is run using the Linux script Command Line Prompt.


Error Messages



[ALDECLARATIVECLASSES] (l.access.ConnectionManagerImpl) ERROR - Not returning connection 3 for database "pegarules" to the pool as it previously encountered the following error
User ID: (unknown)
Last SQL: SELECT pxObjClass AS "pxObjClass", pzInsKey AS "pzInsKey", pyRuleSet AS "pyRuleSet", pyRuleSetVersion AS "pyRuleSetVersion", pyClassName AS "pyClassName", pyPurpose AS "pyPurpose", pyRuleStarts AS "pyRuleStarts", pyRuleAvailable AS "pyRuleAvailable", pyRuleEnds AS "pyRuleEnds", pyCircumstanceProp AS "pyCircumstanceProp", pyCircumstanceVal AS "pyCircumstanceVal", pyCircumstanceDateProp AS "pyCircumstanceDateProp", pyCircumstanceDate AS "pyCircumstanceDate", pyBaseRule AS "pyBaseRule", pyCircumstanceType AS "pyCircumstanceType", pySortDateCircumWithinRSMajor AS "pySortDateCircumWithinRSMajor" FROM GIN.pr4_rule_property "property" WHERE (pyClassName = ?) AND (pxObjClass = 'Rule-Obj-Property') AND (pyIsAssociation = 'true')
java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

com.pega.pegarules.pub.database.NonexistentTableException: Database-NonexistentTable GIN.pr4_rule_sysgen PegaRULES"



Steps to Reproduce



Not Applicable


Root Cause



The exceptions occurred as the BIX extract rule was run from the  Command Prompt.


Resolution



Perform the following local-change since the user migrated from single schema to split schema:

Modify the prconfig.xml as below.

<!-- Rules Schema configuration details -->

  <env name="database/drivers" value="oracle.jdbc.OracleDriver" />
  <env name="database/databases/PegaRULES/dataSource" value="java:comp/env/jdbc/PegaRULES" />
  <env name="database/databases/PegaRULES/url" value="jdbc:oracle:thin:@//HOSTNAME/SID" />
  <env name="database/databases/PegaRULES/userName" value="gin_appid" />
  <env name="database/databases/PegaRULES/password" value="password" />
  <env name="database/databases/PegaRULES/defaultSchema" value="GIN_RULE" type="java.lang.String"  />
  
  <!-- Target Database Configuration Details -->
  <env name="database/databases/TargetDB/url" value="jdbc:oracle:thin:@//HOSTNAME/SID" />
  <env name="database/databases/TargetDB/userName" value="ginmart_appid" />
  <env name="database/databases/TargetDB/password" value="password" />
  
  <!-- Data Schema configuration details -->
  <env name="database/databases/PegaDATA/dataSource" value="java:comp/env/jdbc/PegaDATA" />
  <env name="database/databases/PegaDATA/url" value="jdbc:oracle:thin:@//xxxx:49125/xxxx" />
  <env name="database/databases/PegaDATA/userName" value=" " />
  <env name="database/databases/PegaDATA/password" value="xxxx" />
  <env name="database/databases/PegaDATA/defaultSchema" value="GIN" type="java.lang.String" />



Published October 28, 2018 - Updated December 2, 2021

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