Recover Database noredo Is Failing with (RMAN-00600: internal error, arguments [5041]) while performing roll forward of Physical standby
(Doc ID 2319557.1)
Last updated on OCTOBER 17, 2019
Applies to:
Oracle Database - Enterprise Edition - Version 12.1.0.2 to 12.2 BETA1 [Release 12.1 to 12.2]Oracle Database Exadata Cloud Machine - Version N/A and later
Oracle Cloud Infrastructure - Database Service - Version N/A and later
Oracle Database Cloud Exadata Service - Version N/A and later
Oracle Database Exadata Express Cloud Service - Version N/A and later
Information in this document applies to any platform.
Symptoms
For the purposes of this document, the following fictitious environment is used as an example to describe the procedure:
Database Name: REDC2
Instance Name: redc2t1
***********************
Recover Database Noredo Is Failing with (RMAN-00600: internal error, arguments [5041]) while Performing A Roll Forward Of Physical Standby
Recovery Manager: Release 12.1.0.2.0 - Production on Mon Oct 16 13:46:16 2017
Copyright (c) 1982, 2014, Oracle and/or its affiliates. All rights reserved.
connected to target database: REDC2 (DBID=2487049592, not open)
RMAN> RECOVER DATABASE NOREDO;
Starting recover at 16-OCT-17
using target database control file instead of recovery catalog
allocated channel: ORA_DISK_1
channel ORA_DISK_1: SID=13 instance=redc2t1 device type=DISK
RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-00601: fatal error in recovery manager
RMAN-03012: fatal error during compilation of command
RMAN-03028: fatal error code for command recover : 600
RMAN-00600: internal error, arguments [5041] [5] [1951044] [12835683] []
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 |
Cause |
Solution |