ORA-600 [17183] Checking Datafiles with RMAN for Corruptions
(Doc ID 1643584.1)
Last updated on JUNE 17, 2021
Applies to:
Oracle Database - Enterprise Edition - Version 10.2.0.4 to 11.2.0.3 [Release 10.2 to 11.2]Oracle Database Cloud Schema Service - Version N/A and later
Gen 1 Exadata Cloud at Customer (Oracle Exadata Database Cloud Machine) - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Backup Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
Using RMAN to check datafiles for corruptions fails with an ORA-600 [17183] like below:
RMAN> BACKUP check logical VALIDATE DATAFILE 89,106,192,346,366,491,492,493,494;
Starting backup at 24-MAR-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=698 instance=<instname> devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00346 name=/dev/rlv_bst_0371
input datafile fno=00366 name=/dev/rlv_bst_0391
input datafile fno=00089 name=/dev/rlv_bst_0096
input datafile fno=00106 name=/dev/rlv_bst_0114
input datafile fno=00192 name=/dev/rlv_bst_0202
input datafile fno=00491 name=/dev/rlv_bst_0516
input datafile fno=00492 name=/dev/rlv_bst_0517
input datafile fno=00493 name=/dev/rlv_bst_0518
input datafile fno=00494 name=/dev/rlv_bst_0519
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/24/2014 21:31:20
ORA-00600: internal error code, arguments: [17183], [0x11049F438], [], [], [], [], [], []
Starting backup at 24-MAR-14
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: sid=698 instance=<instname> devtype=DISK
channel ORA_DISK_1: starting full datafile backupset
channel ORA_DISK_1: specifying datafile(s) in backupset
input datafile fno=00346 name=/dev/rlv_bst_0371
input datafile fno=00366 name=/dev/rlv_bst_0391
input datafile fno=00089 name=/dev/rlv_bst_0096
input datafile fno=00106 name=/dev/rlv_bst_0114
input datafile fno=00192 name=/dev/rlv_bst_0202
input datafile fno=00491 name=/dev/rlv_bst_0516
input datafile fno=00492 name=/dev/rlv_bst_0517
input datafile fno=00493 name=/dev/rlv_bst_0518
input datafile fno=00494 name=/dev/rlv_bst_0519
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on ORA_DISK_1 channel at 03/24/2014 21:31:20
ORA-00600: internal error code, arguments: [17183], [0x11049F438], [], [], [], [], [], []
The call stack from the trace file includes functions like:
... kgherror kghfrf kcbtmfr kdb4chk kd4chk kcbchk krbb1cf krbbtgb krbbpc krbibv ...
Changes
No actual change or backup.
The command is not doing a backup but checking the datafiles for corruption. From 11g and beyond the backup clause can be omitted and use "validate check logical database|datafile".
Please refer to
<Note 472231.1> - How to identify all the Corrupted Objects in the Database with RMAN
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Changes |
| Cause |
| Solution |
| References |