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

Oracle Error Reported - ORA-06550 from PegaAESRemote startup

SA-375

Summary



The following error occurs on startup of PegaAESRemote agent running on PRPC 7.1.2:

java.sql.SQLException: ORA-06550: line 1, column 7:
PLS-00201: identifier 'SPPR_POPULATE_INDEX_DATA' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

Error Messages



2014-07-15 17:35:13,758 [ WebContainer : 7] [ STANDARD] [ ] [ PegaRULES:07.10] (l.access.ConnectionManagerImpl) ERROR lnbrpegq01|<HOST>|SOAP|PegaAESRemote|IndexInfo|GetIndexInfo|A3775EAEBCA00F0C4FF8CCC6AD3B46180 - Not returning connection 13501 for database "pegadata" to the pool as it previously encountered the following error
User ID: (unknown)
Last SQL: {call SPPR_POPULATE_INDEX_DATA(?,?)}
java.sql.SQLException: ORA-06550: line 1, column 7:
PLS-00201: identifier 'SPPR_POPULATE_INDEX_DATA' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1044)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3584)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3685)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1376)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecute(WSJdbcPreparedStatement.java:958)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.execute(WSJdbcPreparedStatement.java:625)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.execute(DatabasePreparedStatementImpl.java:990)
at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:6187)
at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6657)
at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6613)
at com.pega.pegarules.data.internal.access.DatabaseImpl.deleteRDB(DatabaseImpl.java:5924)
at com.pegarules.generated.activity.ra_action_getindexinfofortable_00f5d8b29e46787f4dcf4a26a48a74f5.step4_circum0(ra_action_getindexinfofortable_00f5d8b29e46787f4dcf4a26a48a74f5.java:389)
at com.pegarules.generated.activity.ra_action_getindexinfofortable_00f5d8b29e46787f4dcf4a26a48a74f5.perform(ra_action_getindexinfofortable_00f5d8b29e46787f4dcf4a26a48a74f5.java:120)


Steps to Reproduce



AES 3.4 or AES 7.1 is in use to monitor PRPC 7.1.2 and the error is observed in the log file.


Root Cause



The root cause of this problem is a defect in Pegasystems’ code/rules.
The methodology in place to get index information does not support split schema.

Resolution



This issue is scheduled to be resolved in Maintenance Level (ML) 7.

Published March 11, 2016 - 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