On Thursday, Feb 14, at about 8:20 - 8:30 pm, pacific time, the partition holding archive logs filled up completely so the database staooped processing transactions. The space that was available in the partition earlier in the day was sufficient for 3-5 days of "normal" archive log buildup, yet it seems to have filled up in only about a 45 minute time frame immediately before the processing stopped.
I really need to know what was hammering my database so hard it produced that kind of transaction history in only 45 minutes.
the error which i ngot in alert log :
ORA-16038: log 4 sequence# 10840 cannot be archived
ORA-19502: write error on file "", blockno (blocksize=)
ORA-00312: online log 4 thread 1: '/ora01/oradata/pbm1/redo/
redo04a'
ORA-00312: online log 4 thread 1: '/usr1/oradata/pbm1/redo/r
edo04b'
Thu Feb 14 20:16:24 2008
Thread 1 advanced to log sequence 10842
Current log# 6 seq# 10842 mem# 0: /ora01/oradata/pbm1/redo/r
edo06a
Current log# 6 seq# 10842 mem# 1: /usr1/oradata/pbm1/redo/re
do06b
Current log# 6 seq# 10842 mem# 0: /ora01/oradata/pbm1/redo/r
edo06a
Current log# 6 seq# 10842 mem# 1: /usr1/oradata/pbm1/redo/re
do06b
Thu Feb 14 20:16:24 2008
ARC1: Beginning to archive log# 4 seq# 10840
ARC1: Archiving not possible: No primary destinations
ARC1: Failed to archive log# 4 seq# 10840
ARCH: Archival stopped, error occurred. Will continue retrying
Thu Feb 14 20:16:24 2008
ORACLE Instance stndby - Archival Error
ARCH: Connecting to console port...
Thu Feb 14 20:16:24 2008
ORA-16014: log 4 sequence# 10840 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/ora01/oradata/pbm1/redo/
redo04a'
ORA-00312: online log 4 thread 1: '/usr1/oradata/pbm1/redo/r
edo04b'
ARCH: Connecting to console port...
ARCH:
ORA-16014: log 4 sequence# 10840 not archived, no available destinations
ORA-00312: online log 4 thread 1: '/ora01/oradata/pbm1/redo/
redo04a'
ORA-00312: online log 4 thread 1: '/usr1/oradata/pbm1/redo/r
edo04b'
Thu Feb 14 20:16:34 2008
i know that this error is cause of archive destination gets full.
as i have said my archive destination size is good but on thursday my destination got full in 45 mins
could anybody explain me why archiving is genereted so fast.???
Thanks,
Daniesh