My Oracle Support Banner

Oracle Access Manager 11g (OAM) Configuring a Database Audit Data Store Does not Work / jps-config.xml Changes are Reverted (Doc ID 2251593.1)

Last updated on JULY 27, 2022

Applies to:

Oracle Access Manager - Version 11.1.1.5.5 to 11.1.1.5.9 [Release 11g]
Information in this document applies to any platform.

Symptoms

While changing the OAM repository for auditing from file to database, the change appears to revert.

Using the following documentation:

Oracle® Fusion Middleware Administrator's Guide for Oracle Access Manager with Oracle Security Token Service 11g Release 1 (11.1.1)
24 Auditing Administrative and Run-time Events

1. Created the database for the audit store

2. Modified the file 'jps-config.xml' ($DOMAIN_HOME/config/fmwconfig/jps-config.xml) as described in the Section below and restarted WebLogic Admin and OAM Managed servers..

Oracle® Fusion Middleware Administrator's Guide for Oracle Access Manager with Oracle Security Token Service 11g Release 1 (11.1.1)
Setting Up the Audit Database Store

After the restart, audit tables do not load and the changes made to the 'jps-config.xml' are reverted (audit store set back to file).

Changes

 

Cause

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
Symptoms
Changes
Cause
Solution
References


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