pr_data_op_session table has multiple records

General
, , , , , ,
1

How to delete passivated operator records from pr_data_op_session table.

There are multiple records for same operator id. For some records “IsPassivated” column as ‘false’, and some records with “IsPassivated” column as ‘true’. So Records are getting huge in production environment. Now question is

  1. What is the requirement to store the passivated operator records?

  2. How to remove the passivated operator records from table?

2

@Susmita@17 this question has been covered in other forum posts:

When is passivation data cleaned up

Does PassivationDaemon clean up only in database or filesystem as well?

Please can you confirm that you have set all the system configuration settings?

Configuring your system for passivation and activation

pr_data_op_session table frequently needs to be defragmented in regular maintenance window and an index added to perform better.

Please see other things to consider in a similar forum question Job pyNodeCleaner failing

Note:

You did not specify your version of Pega. Note that if you are seeing ORA-01795 error while pzClusterAndDBCleaner job is running then this is a known problem (o BUG-695023). This error occurs when there are more than 1000 requestors in IN clause of delete query which deletes records from presence table.

The pzClusterAndDBCleaner job scheduler was not able to cleanup data in pr_op_data session table due to the delete query formed to clean up this table throwing “ora-01795 maximum number of expressions in a list is 1000 oracle 19c” exception. This has been resolved by splitting requestor IDs into batches of 1000.

Fixed in:
8.5.6, 8.6.4, 8.7.2 and 8.8. You can read about it in the ‘Resolved Issues’ documentation.