OAM Audit Data Is Not Pushed To The DB After Applying the Docker image 12.2.1.4-jdk8-ol8-240415
(Doc ID 3027870.1)
Last updated on JUNE 12, 2024
Applies to:
Oracle Platform Security for Java - Version 12.2.1.4.0 and laterInformation in this document applies to any platform.
Symptoms
Customer is using OAM 12.2.1.4 on Docker.
After applying image 12.2.1.4-jdk8-ol8-240415 the audit bus file it is not uploaded in DB as it is configured.
The AuditLoader process appears to have issues. The customer shutdown all servers, moved auditloader.state to a backup locations and started everything. The auditloader.state file is not recreated when the servers start.
Observations:
- getAuditRepository() WLST commands outputs the expected values: DB auditing is enabled, 15 seconds interval, etc.
- the relevant events are recorded to audit.log so there is no issue related to the bus-stop files.
- no audit data was pushed to the DB ever since the BPs were applied.
- the OPSS datasources are in good standing as seen below:
customer try following actions:
1.delete autoloader.status file and restart servers
2. delete audit.log and auditloader.status files and restart servers
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 |
Cause |
Solution |
References |