An ORA-15028 error occurred while deleting archive logs from ASM

Today, at, I ran to CICC to check the data and found that the archive of the Library (11gr2 RAC, 4 nodes under aix6.1) was full recently. I ran to ask the middleware buddy who had arrived in advance, no exception was found ......

It's just a bit cool. If this is my mother's time, something will happen soon and taxpayers will not be in a hurry ...... If you do not need to talk about it, clear it first. Switch to the grid user and use the OS command to delete two folders through asmcmd.

When the result is deleted to the second folder, an error occurs:

ORA-15032: not all alterations saved med
ORA-15028: ASM file '+ fra/bjschxcx /...... 'Not dropped; currently being accessed (DBD error: ocistmtexecute)

LS command Check, found that only one file has not been deleted, the database has been restored from the Hang machine status, try to delete with rman, still reports the following error:

RMAN-00571: ========================================================== ==============================
RMAN-00569: ==================== error message stack follows ==========================
RMAN-00571: ========================================================== ==============================
RMAN-03009: failure of DELETE command on default channel at 06/08/2012 13:20:35
ORA-15028: ASM file '+ fra/bjschxcx /...... 'Not dropped; currently being accessed

The archive I want to delete has been paid for several days. Currently, it should not be used properly. Even if several goldengate instances are configured on the database recently, the database is successfully released after a bit of archive space is released.

But this problem is not solved. I checked several manufacturers' goldengate instances and did not use the archived logs I want to delete, and there is no latency in the process.

I checked Metalink and found 2 or 3 articles describing this phenomenon.

One of the descriptions is as follows, which definitely does not meet the scenario I encountered here. First, exclude,

Cause

The issue can be caused by any replication process running or hanging, holding this file.

For example a Golden Gate replication or shareplex replication process.

Solution

Stop the replication process and Try deleting the file uisng RMAN or asmcmd.

The other two articles are as follows:

Cause:An attempt was made to drop an ASM file, but the file was being accessed by one or more database instances and therefore could not be dropped. Action:Shut down all database instances that might be accessing this file and then retry the drop command.

Solution

Use the following to quickly find out which database instance holds the lock and to identify for restart:

Asmcmd [+]> lsof-G dg_arch
Db_name instance_name path
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_eclipseq_72711.5178.785032231
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_eclipseq_7272134818.785040307
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_eclipseq_72727.4616.785046605
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_eclipseq_72730.4479.78501_61
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_eclipseq_72742.4395.785059089
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_2_seq_70382.2308.785047531
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_2_seq_70385.1835.785050225
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_2_seq_70402.3091.785064133
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_2_seq_70408.1211.785069875
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_2_seq_70410.4439.785071661
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_3_seq_67973.4354.785051059
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_3_seq_67974.2051.785051959
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_3_seq_67995.1876.785069891
Myprod myprod1 + dg_arch/myprod/archivelog/2012_06_04/thread_6_seq_32158.4060.785020.39
Myprod myprod1 + dg_arch/myprod/datafile/tbs_hways_master_data_med.1698.750777283

These two articles may be a bit like my scenario. According to the example in the third article, I also executed lsof-G FRA in asmcmd, but no output is displayed after the command is executed.

I don't know if my version here is not suitable. My environment database version is 11.2.0.3.0, and my database version written in this article should also be applicable.

Oracle Server-Enterprise Edition-version 11.2.0.2 and later
Information in this document applies to any platform.

At around, another colleague of mine was going to check the help information of the lsof command. As a result, he was really hurt. He directly entered lsof

As a result, the output shown above is ......

The result is that instance 4 locks the archive log. After node 4 is restarted at noon, run the RMAN command to delete the archive normally.

For reprint, please indicate the source and original article links:

Http://blog.csdn.net/xiangsir/article/details/8679761