After DB upgrade to 184.108.40.206, Database Link (DBLink) Target is dumping multiple *.aud files when DBLink is used
(Doc ID 2745786.1)
Last updated on JANUARY 21, 2021
Applies to:Oracle Database - Enterprise Edition - Version 220.127.116.11 to 18.104.22.168 [Release 11.2]
Oracle Net Services - Version 22.214.171.124 to 126.96.36.199 [Release 11.2]
Information in this document applies to any platform.
*NOTE: All values in this SR are fictitious and do not represent any actual or existing environments.
Two databases were upgraded from 188.8.131.52 (this example on Solaris 10 container) to 184.108.40.206.
The TNS Listeners servicing these databases were also upgraded to 11204.
After this, the two Databases were involved in an overnight "ETL job" which used an existing Database Link (DBLink) but this was now taking an extremely long time to run.
A job that used to take ~4 min to run now runs for over 10 hrs and then fails.
In addition, there are constant *.aud files being dumped under $ORACLE_BASE/admin//adump in the TARGET Database for the dblink from the start of the ETL until death.
In this case, around 0.5 Million audit files were created over the 10 hour period.
Audit files are small but numerous, and contain information as below:
This was an upgrade of a single set of Databases from 220.127.116.11 to 18.104.22.168 which were using legacy DBLinks for ETL jobs.
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