When running a Policy Server, when a user authenticates, from time to time, the user data can't be seen in the Audit data in the DB.
Should the smaccesslog4 table and sm_username column like filters in use?
Policy Server 12.8SP6a;
Audit Store on Oracle RAC;
At first glance, there are 2 tables in the Oracle Audit Store:
and both have sm_username as a field. The fact that the data might not be written or might not be accessible could be caused by:
Some parameters can be set to configure and tune the connections with the Audit Store (5)(6).
- SQLBulkInsertFlushInterval determines the frequency in which the Policy Server inserts queued audit events into the audit database. The default value of this registry key is 60 seconds. If 60 seconds elapses before the value defined by the SQLBulkInsertFlushRowCount is reached, the Policy Server inserts all queued audit events into the audit database.
- SQLBulkInsertFlushRowCount determines how many audit events occur before the Policy Server inserts audit events into the audit database. The default value of this registry key is 1,000. If 1,000 audit events are queued before the value defined by SQLBulkInsertFlushInterval is reached, the Policy Server inserts all queued audit events into the audit database.