SA-37369

Summary

This is an issue with the Pega Marketing 7.1.3 and PRPC platform is 7.2.

The user notices an issue during deployment of the build to a target environment. They created Strategy Result properties in our DEV instance and executed a Program run which successfully created the corresponding columns while run of the program. However, when they export the RAP which has the new SR properties and deployed it in the test environment, they were unable to see the properties being created. They tried deleting the conclusion cache and also tried deleting the rule cache of the CampaignCode SR property. After that they cleared the extract marker and restarted the server. The program run now successfully created the column for this SR property.

Error Messages

User ID: System

Last SQL: select count (*) as "pyCount" from OLY_PEG_MARKET_OWNER.BatchOutPR90 where pxObjClass = 'Data-BatchOutPR90'

java.sql.SQLSyntaxErrorException: ORA-00942: table or view does not exist

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:447)

at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)

at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:951)

at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:513)

at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:227)

at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)

at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:208)

at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:886)

at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1175)

at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1296)

at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3613)

at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3714)

at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1378)

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:582)

at com.pega.pegarules.data.internal.access.DatabaseImpl.list(DatabaseImpl.java:6447)

at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6932)

at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6885)

at com.pega.pegarules.data.internal.access.DatabaseImpl.executeRDB(DatabaseImpl.java:6865)

at Pega.Page.RDBExecute(Page.java:1175)

Steps to Reproduce

Not applicable

Root Cause

The log files did not show up any errors related to import so root cause could not be determined.

Resolution

Issue is complex to fix as hotfix, hence raised a Bug for future release.
Also Local change is available for this issue.
After import of new poposition properties, using SMA -> Etier Static Management page -> Perform deletion of LLC cache.