ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode During RMAN COLD BACKUP

Complete error:

RMAN-00571: ===========================================================
RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS ===============
RMAN-00571: ===========================================================
RMAN-03009: failure of backup command on c1 channel at 11/21/2016 17:30:42
ORA-19602: cannot backup or copy active file in NOARCHIVELOG mode

Cause: Database was shut down with shut down abort option or due to internal/External error or any user error or hardware error.

There are datafile file that are not in consistent state..
A COLD backup for a database running in NOARCHIVELOG mode has to be a CONSISTENT backup as it cannot be recovered after restore.


To Confirm :

 SQL> select distinct checkpoint_change# from v$datafile_header;

If this will return >1 row, indicating that files are at different points in time.

or we can also check which datafile file need more recovery.

     Select * from v$recover_file ;

  no rows selected ,means no file is waiting for recovery. If any files shown in output need to go for standard datafile recovery. 

Check for   if the datafiles are in Fuzzy status

What is Fuzzy:

FUZZY bit in datafile header means that there may have been writes into a
datafile after the last checkpoint. E.g. there may be changes written to
datafile with higher SCN than checkpoint_change# stored in datafile header
(seen from v$datafile_header.checkpoint_change#).

So, whenever a datafile is opened it is checked for fuzzy bits.
If it is fuzzy then the database checks the checkpoint_change$
column to search the SCN from which the redo logs are to be applied.

Select status,file#,fuzzy,checkpoint_change# from v$datafile_header;

 STATUS       FILE# FUZ CHECKPOINT_CHANGE#
------- ---------- --- ------------------
ONLINE           1 YES            10234
ONLINE           2 YES            10234
ONLINE           3 YES            10234
ONLINE           4 YES            10234

YES value indicates files are fuzzy and need recovery.

check  redo log files(Current/Active shown q

uery 1) are available or not.

SQL>Select b.member,a.group#,a.sequence# from v$log a ,v$logfile b where a.group#=b.group#

If  redo logs are available go with recovery.

SQL>Recover database ;

     

Note:  No need to open the database with resetlogs option after recovery.

References: 

COLD RMAN backup fails: Ora-19602 even after SHUTDOWN IMMEDIATE and STARTUP MOUNT (Doc ID 373828.1)

 http://www.parnassusdata.com/en/node/569