Database Tutorials MSSQL, Oracle, PostgreSQL, MySQL, MariaDB, DB2, Sybase, Teradata, Big Data, NOSQL, MongoDB, Couchbase, Cassandra, Windows, Linux 
When you create backups with rman in Oracle 12.2 databases, an “RMAN-10038: database session for channel d1 terminated unexpectedly” error occurs. You see the error “ORA-00600: internal error code, arguments: [krbebad_1]” in the Alert log file. The problem is caused by a bad “block or blocks” that are not yet marked. After detecting and fixing the corrupte block or blocks, rman backup can successfully created.
Error in rman Session
1 2 3 4 5 | RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03009: failure of backup command on d1 channel at 11/07/2019 17:32:15 RMAN-10038: database session for channel d1 terminated unexpectedly |
Error in Alert Log
1 2 3 4 | ORA-00602: internal programming exception ORA-07445: exception encountered: core dump [skgxpdmprqh_int()+84] [SIGSEGV] [ADDR:0x0] [PC:0x7F7D8B52BB74] [SI_KERNEL(general_protection)] [] ORA-07445: exception encountered: core dump [ksmem_dump()+80] [SIGSEGV] [ADDR:0x0] [PC:0x1282B10] [SI_KERNEL(general_protection)] [] ORA-00600: internal error code, arguments: [krbebad_1], [1031], [25], [], [], [], [], [], [], [], [], [] |
Check Corrupted Blocks
If you do not see bad blocks when you check v$database_block_corruption, all datafiles should be checked as follows. When a corrupted block is detected, you will see it in v$database_block_corruption.
1 2 3 4 5 6 7 8 9 10 11 12 13 14 15 16 17 18 19 20 21 22 23 24 25 26 27 28 29 30 31 32 33 34 35 36 37 38 | RMAN> backup validate check logical datafile 2; Starting backup at 05-NOV-19 allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=197 instance=ORCL1 device type=DISK allocated channel: ORA_DISK_2 channel ORA_DISK_2: SID=5 instance=ORCL1 device type=DISK allocated channel: ORA_DISK_3 channel ORA_DISK_3: SID=135 instance=ORCL1 device type=DISK allocated channel: ORA_DISK_4 channel ORA_DISK_4: SID=196 instance=ORCL1 device type=DISK allocated channel: ORA_DISK_5 channel ORA_DISK_5: SID=261 instance=ORCL1 device type=DISK allocated channel: ORA_DISK_6 channel ORA_DISK_6: SID=324 instance=ORCL1 device type=DISK allocated channel: ORA_DISK_7 channel ORA_DISK_7: SID=645 instance=ORCL1 device type=DISK allocated channel: ORA_DISK_8 channel ORA_DISK_8: SID=773 instance=ORCL1 device type=DISK channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00002 name=+DATA/orcl/datafile/sysaux.500.921154373 channel ORA_DISK_1: backup set complete, elapsed time: 00:00:15 List of Datafiles ================= File Status Marked Corrupt Empty Blocks Blocks Examined High SCN ---- ------ -------------- ------------ --------------- ---------- 2 FAILED 0 36070 454402 1453401262323 File Name: +DATA/orcl/datafile/sysaux.500.921154373 Block Type Blocks Failing Blocks Processed ---------- -------------- ---------------- Data 0 150505 Index 1 184242 Other 0 83583 validate found one or more corrupt blocks See trace file /u01/app/oracle/diag/rdbms/orcl/ORCL1/trace/ORCL1_ora_295378.trc for details Finished backup at 05-NOV-19 |
To fix corrupted blocks you may want to read the article “How To Detect and Repair Block Corruption in Oracle”
