Huge Database Archive Logs are Getting Generated for Argus Due to Incomplete Mandatory Configurations
(Doc ID 2694643.1)
Last updated on JULY 13, 2023
Applies to:
Oracle Life Sciences Argus Safety - Version 7.0.0 and laterOracle Life Sciences Argus Interchange - Version 7.0.0 and later
Oracle Life Sciences Argus Safety Japan - Version 7.0.0 and later
Information in this document applies to any platform.
Symptoms
Huge archive logs are getting created in Argus Safety Database for minimal activity on the application server.
DB is averaging 800gb to 1+ TB of archive log generation daily but the DB is less then 200gb in size.
The database is constantly churning logs even at night when no one is using them system.
Customers reported that the ESM Service seems to have got into a loop where it is processing huge amounts of data and producing massive redo logs.
The system is a customer production system. The database is running in archivelog mode.
The logs are being archived every night but are being generated faster than they can be archived.
This has resulted in the drive containing the archive logs becoming full and stopping the database.
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 |