We have 4 databases which each have a standby database. These databases were sending the archive logs to the correct locations in ASM. After recycling the databases now one of these
databases is sending the archive logs to the default location of $ORACLE_HOME/dbs. Unfortunately the file names of the generated logs are generic and we cannot determine which database is erroneously sending
the archive logs to the wrong location. This caused an issue over the holiday where by the file system where $ORACLE_HOME resides filled up to 100%.
The Primary and Standby LOG and RECOVERY-recovery related parameters appear to look fine. None of our ArchiveLog destinations point to a file system. They all point to an ASM
disk group. So we are baffled as to why the system is sending these files to the default oracle archive file destination at $ORACLE_HOME/dbs.
Here is a sample of the names of the files. Numerous of these files appear in the $ORACLE_HOME/dbs directory.
-rw-r----- 1 oracle dba 862720 Jan 2 11:11 DB_RECOVERY_FILE_DEST1_9541_774882286.dbf
-rw-r----- 1 oracle dba 966144 Jan 2 11:11 DB_RECOVERY_FILE_DEST2_9215_774882286.dbf
Note that there is a file DEST1 and DEST2
Also notice that the files do not indicate the database of origin.
One option would be to temporarily suspend the MRP0 process for each database done-by-one and see if the system stops writing these files.
Flashback is turned on for these primary databases.