Redolog status

[newcomer]

Hi All,

If I will loose one of the log members in a group - when my Datbase is up and running, does oracle write that information in ALTER file?

I mean, without shutting down my database and bouncing it back or withour querying status in v$logfile , is there any way to know that members got deleted.

Thanks

[Giani]

Your database will crash.

Originally posted by newcomer
Hi All,

If I will loose one of the log members in a group - when my Datbase is up and running, does oracle write that information in ALTER file?

I mean, without shutting down my database and bouncing it back or withour querying status in v$logfile , is there any way to know that members got deleted.

Thanks

Yes, it will write a trace file in which you can see the missing and also in the alert log something like this including trace file:
ORA-27037: Message 27037 not found; No message file for product=RDBMS, facility=ORA
SVR4 Error: 2: No such file or directory
Additional information: 3
LGWR: terminating instance due to error 313
Instance terminated by LGWR, pid = nnnnn

HTH

[Giani]

Sorry I missed this part :

eg:
Errors in file /dbs/app/oracle/admin/$ORACLE_SID/bdump/xxxx_nnnn.trc:
ORA-00313: Message 313 not found; No message file for product=RDBMS, facility=ORA; arguments: [4] [1]
ORA-00312: Message 312 not found; No message file for product=RDBMS, facility=ORA; arguments: [4] [1]
[/u01/oradata/$ORACLE_SID/redoSID_4.log

[seelan]

Originally posted by Giani
Your database will crash.

Hi,

If ur database contains atleast one valid member in all the log groups, then your database won't get crash.

But ofcourse it will write the infomation about ur invaid member in the alert files as follows

Alert file Output
*****************

Dump file G:\Oracle\admin\fatma\bdump\fatmaALRT.LOG

11:30 AM 4/29/1999Thu Apr 29 11:34:56 1999
Thread 1 advanced to log sequence 152
Current log# 1 seq# 152 mem# 0: G:\ORACLE\ORADATA\FATMA\REDO01.LOG
Thu Apr 29 11:34:56 1999
ARC0: Beginning to archive log# 2 seq# 151
Thu Apr 29 11:35:00 1999
Errors in file G:\Oracle\admin\fatma\bdump\fatmaLGWR.TRC:
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'G:\ORACLE\ORADATA\FATMA\REDO31.LOG'
ORA-27048: skgfifi: file header information is invalid
OSD-04004: invalid file header

Thu Apr 29 11:35:00 1999
Errors in file G:\Oracle\admin\fatma\bdump\fatmaLGWR.TRC:
ORA-00321: log 3 of thread 1, cannot update log file header
ORA-00312: online log 3 thread 1: 'G:\ORACLE\ORADATA\FATMA\REDO31.LOG'

Thu Apr 29 11:35:00 1999
Errors in file G:\Oracle\admin\fatma\bdump\fatmaLGWR.TRC:
ORA-00313: open failed for members of log group 3 of thread 1

Trace file Output
*************************


*** SESSION ID:(3.1) 1999-04-29 11:24:47.477
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00313: open failed for members of log group 3 of thread 1
ORA-00312: online log 3 thread 1: 'G:\ORACLE\ORADATA\FATMA\REDO31.LOG'
ORA-27048: skgfifi: file header information is invalid
OSD-04004: invalid file header
ORA-00321: log 3 of thread 1, cannot update log file header
ORA-00312: online log 3 thread 1: 'G:\ORACLE\ORADATA\FATMA\REDO31.LOG'
ORA-00313: open failed for members of log group 3 of thread 1

Seelan