Destination ARCHIVELOG and closing DB space

Hello

ENV: Oracle 10 g 2 (10.2.0.3) 64-bit on Solaris (not sure OS version)

A few days ago, one of process controls failed with 'ORA-03113: end of file on communication channel"in the log file (failure autour mid-night and since what happened in DEV env, I knew not that until the next morning). When I contacted s/n, I was told that destination archivelog had full.

In my experience of prev, in such situation, the database always became 'guillotine' of new impossible connections (with the exception of SYSDBA) but has never stop. And data base resumed normal activity after former archivelog files have been backed up and deleted.

So I wonder if it is possible for the database at the stop (do not know if 'crash' is the right word to use) after waiting for some time for space to become available to Archivelog Destination? If so, this parameter indicates the database queue before you stop time?

Thanks in advance!

Thanks EdStevens!

I found the following document which seems to be more relevant to my situation:

Archiving of full Destination causing ORA-600 [1433] [60] and Instance Crash (Doc ID 748885.1)

BUG: 7242087 -LWGR ORDER DB instead of SUSPEND, ORA-600 [1433]-> MESSAGE Q COMPLETE

Tags: Database

Similar Questions

Maybe you are looking for