My Oracle Support Banner

OPAM Auditing: Not Writing All Events To The Database (Doc ID 2265081.1)

Last updated on OCTOBER 11, 2019

Applies to:

Oracle Privileged Account Manager - Version and later
Information in this document applies to any platform.


OPAM Auditing is not writing all events to the database audit tables.  The majority of events are written to audit logs on the file system. Only the "PolicyEnforcer.removeCheckouts:checkIn" are being written to the database though many of these are ending up in the file system audit logs.

Found article under Oracle Community where resolution was to restart the bi_server1 managed server. Also restarted the OPAM managed servers. After this a few Checkout/Checkin events were written to the database, but went right back to being written to the file system audit logs.

The following error is seen in managed server diagnostic logs:

java.sql.BatchUpdateException: ORA-12899: value too large for column "PROD_IAU"."IAU_COMMON"."IAU_RESOURCE" (actual: 579, maximum: 255)


To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!

In this Document

My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.