Policy Server doesn't write audit log on database DB
search cancel

Policy Server doesn't write audit log on database DB

book

Article ID: 249181

calendar_today

Updated On:

Products

SITEMINDER

Issue/Introduction

 

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?

 

Environment

 

Policy Server 12.8SP6a;
Audit Store on Oracle RAC;

 

Resolution

 

At first glance, there are 2 tables in the Oracle Audit Store:

  • smaccesslog4
  • smobjlog4

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:

  • The SQL statement is not the correct one (1).
  • Lack of configuration (2).
  • Lack of resources in the ODBC Store (3)(4).

Some parameters can be set to configure and tune the connections with the Audit Store (5)(6).

 

Additional Information