Summary

The Oracle database hosting Process Commander must have the COMPATIBLE parameter set to 8.1.0.0.0 or greater for the System Pulse to work correctly.

Suggested Approach

V3.1 makes use of record-level caching to reduce the load on the network and database.  In a system with multiple nodes accessing one PegaRULES database, rules caching can get out of sync; the System Pulse makes sure that each node is using the most updated rule details..  

However, the System Pulse process creates a temporary table.  Unless the Oracle COMPATIBLE parameter is set correctly (to 8.1.0.0.0 or greater), the temporary tables cannot be created, and errors result:

15:55:53,539 [    PegaRULES-Batch-4] (   engine.database.DatabaseImpl) ERROR - There was a database problem when performing an ExecuteStoredProc: ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SYS_SQL", line 824
ORA-06512: at "SYS.DBMS_SQL", line 32
ORA-06512: at "RULESQA.SPPR_SYS_UPDATESCACHE_PREPARE", line 93
ORA-06512: at line 1
java.sql.SQLException: ORA-00942: table or view does not exist
ORA-06512: at "SYS.DBMS_SYS_SQL", line 824
ORA-06512: at "SYS.DBMS_SQL", line 32
ORA-06512: at "RULESQA.SPPR_SYS_UPDATESCACHE_PREPARE", line 93
ORA-06512: at line 1