SA-9778

Summary

On all Pega Servers configured to communicate to AES through ASYNC SOAP, user receive a log error message pertaining to the declaration of a stored procedure.

Error Messages

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.SQLStateMapping.newSQLException(SQLStateMapping.java:70)
at oracle.jdbc.driver.DatabaseError.newSQLException(DatabaseError.java:133)
at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:206)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:455)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:413)
at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:1034)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:194)
at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:953)
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1222)
at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3387)
at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3488)
at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1374)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.pmiExecute(WSJdbcPreparedStatement.java:956)
at com.ibm.ws.rsadapter.jdbc.WSJdbcPreparedStatement.execute(WSJdbcPreparedStatement.java:623)
at com.pega.pegarules.data.internal.access.DatabasePreparedStatementImpl.execute(DatabasePreparedStatementImpl.java:990)
at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:6221)
at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6691)
at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6647)
at com.pega.pegarules.data.internal.access.DatabaseImpl.deleteRDB(DatabaseImpl.java:5958)
at com.pegarules.generated.activity.ra_action_populateindexfortable_3d3e0720d87a82b3bd55cbdb4e416484.step2_circum0(ra_action_populateindexfortable_3d3e0720d87a82b3bd55cbdb4e416484.java:226)
at com.pegarules.generated.activity.ra_action_populateindexfortable_3d3e0720d87a82b3bd55cbdb4e416484.perform(ra_action_populateindexfortable_3d3e0720d87a82b3bd55cbdb4e416484.java:86)
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3275)
at com.pega.pegarules.session.internal.mgmt.Executable.invokeActivity(Executable.java:10265)
at com.pegarules.generated.ac

Root Cause

The root cause of this problem is a defect in Pegasystems’ code/rules. There is a Dynamic System Setting aessetting/perfstatmode that is set to “PUSH” by default in ML6. This setting takes two values:

1. PUSH – Remote Node pushes the information to the AES as a scheduled task 
2. PULL – AES requests for the information using MBean operations.

AES 7.1 doesn’t honor this setting sent from the monitored node. It always try to get the desired information from MBean operations i.e. PULL. 

Resolution

This issue is resolved through the following local change:
After updating the DSS value to “PULL” (while talking to an AES 7.1), exceptions were not seen. User validated this by executing PushDBIndexes activity.