Status of online redo log file INVALID warning appears during online backup

[Former Member]

Hi All,

I have a peculiar problem in one of the SAP ECC 6.0 systems. The daily online backup is getting completed with warnings.

Please find below the warnings in DB12 logs:

BR0335W Status of online redo log file /oracle/AS0/mirrlogB/log_g18m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogB/log_g18m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g50_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogA/log_g50_m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogB/log_g51_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogB/log_g51_m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g52_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogA/log_g52_m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g53_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogA/log_g53_m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g54_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogA/log_g54_m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g55_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogA/log_g55_m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g56_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogA/log_g56_m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogB/log_g57_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogB/log_g57_m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogA/log_g58_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogA/log_g58_m2.dbf' not found

BR0335W Status of online redo log file /oracle/AS0/mirrlogB/log_g59_m2.dbf is INVALID

BR0274W File '/oracle/AS0/mirrlogB/log_g59_m2.dbf' not found

For the above mentioned alerts I followed the recommendations of SAP Note 491160. I dropped and recreated the mirrorlog files. But the next day again when I checked the backup it finished with warnings. At the database level there is no problem

SQL> select * from v$logfile;

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

59 ONLINE

/oracle/AS0/origlogB/log_g59_m1.dbf

NO

59 ONLINE

/oracle/AS0/mirrlogB/log_g59_m2.dbf

NO

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

58 ONLINE

/oracle/AS0/origlogA/log_g58_m1.dbf

NO

58 ONLINE

/oracle/AS0/mirrlogA/log_g58_m2.dbf

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

NO

57 ONLINE

/oracle/AS0/origlogB/log_g57_m1.dbf

NO

57 ONLINE

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

/oracle/AS0/mirrlogB/log_g57_m2.dbf

NO

56 ONLINE

/oracle/AS0/origlogA/log_g56_m1.dbf

NO

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

56 ONLINE

/oracle/AS0/mirrlogA/log_g56_m2.dbf

NO

55 ONLINE

/oracle/AS0/origlogA/log_g55_m1.dbf

NO

54 ONLINE

/oracle/AS0/origlogA/log_g54_m1.dbf

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

NO

54 ONLINE

/oracle/AS0/mirrlogA/log_g54_m2.dbf

NO

53 ONLINE

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

/oracle/AS0/origlogA/log_g53_m1.dbf

NO

53 ONLINE

/oracle/AS0/mirrlogA/log_g53_m2.dbf

NO

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

52 ONLINE

/oracle/AS0/origlogA/log_g52_m1.dbf

NO

52 ONLINE

/oracle/AS0/mirrlogA/log_g52_m2.dbf

NO

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

51 ONLINE

/oracle/AS0/origlogB/log_g51_m1.dbf

NO

51 ONLINE

/oracle/AS0/mirrlogB/log_g51_m2.dbf

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

NO

50 ONLINE

/oracle/AS0/origlogA/log_g50_m1.dbf

NO

50 ONLINE

GROUP# STATUS TYPE

-

---

-

---

-

---

MEMBER

-

---

IS_

---

/oracle/AS0/mirrlogA/log_g50_m2.dbf

NO

8 ONLINE

/oracle/AS0/origlogB/log_g18m1.dbf

As you can see from the above output at the database level everything is fine. So why during backup it is giving me warnings in DB12. Any help with this regard will be appreciated.

Regards

Mitesh Nair

[Former Member]

Those file xy not found messages could indicate a permission problem.

What is your operating system?

Does it work if you run brbackup as user ora<sid> from command line? (Assuming Unix here.)

[Former Member]

Hi Joe,

My OS is HP-UX. I dont think its a permission problem. Please find below the contents of origlogA and mirrlogA

predbci2:/oracle/AS0/origlogA#ls -rtl

total 1433712

drwxrwxrwx 2 oraas0 dba 96 Oct 15 03:27 cntrl

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 01:50 log_g52_m1.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 03:51 log_g50_m1.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 05:51 log_g54_m1.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 07:52 log_g53_m1.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 09:50 log_g55_m1.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 10:50 log_g56_m1.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 12:41 log_g58_m1.dbf

predbci2:/oracle/AS0/mirrlogA#ls -rtl

total 1433728

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 01:50 log_g52_m2.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 03:51 log_g50_m2.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 05:51 log_g54_m2.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 07:52 log_g53_m2.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 09:50 log_g55_m2.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 10:50 log_g56_m2.dbf

-rw-rw---- 1 oraas0 dba 104858624 Dec 4 12:41 log_g58_m2.dbf

Regards

Mitesh

[Former Member]

Christ !

Why so many redo logs ! You must have a busy system....

Did you reset the logs when you opened the database after the rebuild ?

Mark

[Former Member]

Hello Mitesh,

what I had in mind wasn't files, but directory permissions.

What is the output of:

ls -ld /oracle/AS0/mirrlogA

And what about my question:

Does it work if you run brbackup as user ora<sid> from command line?

regards

[Former Member]

Hi,

have you anything hardcoded for the mirrologs in you init files

If you have dropped and re-created them you could have a new sequence number.

Also you did ALTER DATABSE OPEN RESETLOGS;

Mark