Context-based access clean-up
When performing context-based access clean-up, rows are deleted when their expiry is reached.
Manual clean-up queries
To disable the out-of-the-box cleanup, set session.dbCleanupInterval to 0.
Delete the records by using the following SQL queries:
1. DELETE FROM RBA_USER_ATTR_SESSION_DATA WHERE SESSION_ID IN (SELECT SESSION_ID FROM RBA_USER_ATTR_SESSION WHERE REC_TIME < TIMESTAMP);
2. DELETE FROM RBA_USER_ATTR_SESSION WHERE REC_TIME < TIMESTAMP;
3. DELETE FROM AUTH_TXN_OBL_DATA WHERE REC_TIME < TIMESTAMP;
4. DELETE FROM RBA_DEVICE WHERE LAST_USED_TIME < TIMESTAMP;
Note:
- These SQL statements are "pseudo" code examples only and are not specific to any DB type.
- TIMESTAMP is a variable of the TIMESTAMP data type. Records created / last accessed prior to this timestamp will be removed. This can be a derived value calculated from the current date / time and an offset (e.g. Advanced Configuration properties attributeCollection.sessionTimeout for query #1 and #2 (in seconds) or deviceRegistration.inactiveExpirationTime for query #4 (in days)).
- Depending on DB type, the format of TIMESTAMP may differ (e.g. date / time or epoch representation).
- Where value comparisons occur, data types must match.
- Due to a potentially large number of returned records, it may be necessary to limit the 'SELECT' statement in query #1 to a maximum of 1000 records at a time.