RMAN-10038 and ORA-07445 [krbbAddMetaBlk()+252] During Archivelog Backup After Database Upgrade To 12c

12 Okt

betrifft:
Oracle Database – Enterprise Edition – Version 12.1.0.1 and later – jede Plattform

Fehlerausgabe:
Nach upgrade auf 12.1.0.2, RMAN archivelog backup fails with:
RMAN-03009: failure of backup command on t1 channel at 12/10/2015 16:53:30
RMAN-10038: database session for channel t1 terminated unexpectedly

In the alert.log, the following error is reported corresponding to the RMAN error:
Thu Dec 10 16:52:15 2015
Archivelog not in 10gR2 format, producing non-HARD backup piece although compatibility allows it
Thu Dec 10 16:52:44 2015
Exception [type: SIGSEGV, Address not mapped to object] [ADDR:0x14] [PC:0x109A1EE1C, krbbAddMetaBlk()+252] [flags: 0x0,
count: 1]
Errors in file /opt/app/oracle/admin/diag/rdbms/ptprod2/ptprod2/trace/ptprod2_ora_22534.trc (incident=52650):
ORA-07445: exception encountered: core dump [krbbAddMetaBlk()+252] [SIGSEGV] [ADDR:0x14] [PC:0x109A1EE1C] [Address not mapped to object] []
CHANGES
Database is upgraded.

Thread 1 advanced to log sequence 13313 (LGWR switch)
Current log# 3 seq# 13313 mem# 0: /oradata/ptprod2/redo03a.rdo
Current log# 3 seq# 13313 mem# 1: /oradata/ptprod2/redo03b.rdo
This shows the current log sequence is #13313. Within the RMAN archivelog backup log, we see RMAN is backing up archivelog sequences: 13124
to 13127 and failing with RMAN-10038

RMAN-08014: channel t1: specifying archived log(s) in backup set
RMAN-08504: input archived log thread=1 sequence=13124 RECID=11678 STAMP=897602408
RMAN-08504: input archived log thread=1 sequence=13125 RECID=11679 STAMP=897609606

RMAN-08014: channel t2: specifying archived log(s) in backup set
RMAN-08504: input archived log thread=1 sequence=13126 RECID=11680 STAMP=897609606
RMAN-08504: input archived log thread=1 sequence=13127 RECID=11681 STAMP=897615178
RMAN-08504: input archived log thread=1 sequence=13312 RECID=11866 STAMP=898102331

RMAN-03009: failure of backup command on t1 channel at 12/10/2015 16:53:30
RMAN-10038: database session for channel t1 terminated unexpectedly

RMAN-03009: failure of backup command on t2 channel at 12/10/2015 16:53:30
RMAN-10038: database session for channel t2 terminated unexpectedly

Lösungsansatz:
Nach Durchforsten der Tracefiles/Alert ist zu sehen, dass Teile der archivelogs nicht mit 12.1.0.2 verarbeitet werden können – sondern auf dem Stand 11.2.0.4 sind (archivelog sequences 13124 to 13127)

Diese Dateien müssen auf das neue System kopiert (Betriebsystem) und im Anschluss gelöscht werden.
RMAN> delete noprompt archivelog from sequence 13124 until sequence 13127 thread 1;

Diesen Artikel teilen :Share on Google+Share on LinkedInTweet about this on TwitterShare on Facebook