Take RMAN backup in NOARCHIVE mode : In this article I’m going to demonstrate to you how to use RMAN in NOARCHIVE mode steps by steps.
As you know Oracle strongly recommended running your database in archivelog mode for database security. If you running the database in noarchivelog mode, you refused any recovery.
During Oracle RMAN database backup, database must be in archivelog mode for RMAN backup. If you want to take database backup using RMAN in noarchivelog mode then you must put the database in mount state.
There are different ways of offline backup you can take during which database will not be available for normal use. This type of backup is ideally called as consistent backup.
Error in NOARCHIVE mode :
If you tried to take RMAN backup in NOARCHIVE mode
[oracle@node-1 ~]$ rman target / Recovery Manager: Release 126.96.36.199.0 - Production on Sat May 1 11:27:17 2021 Version 188.8.131.52.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL (DBID=1595923691) RMAN> backup database; Starting backup at 01-MAY-21 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=30 device type=DISK RMAN-00571: =========================================================== RMAN-00569: =============== ERROR MESSAGE STACK FOLLOWS =============== RMAN-00571: =========================================================== RMAN-03002: failure of backup command at 05/01/2021 11:28:30 RMAN-06149: cannot BACKUP DATABASE in NOARCHIVELOG mode RMAN>
Take RMAN Backup in NOARCHIVE mode :
There are few simple step to use RMAN if Database in NOARCHIVE. So if you want to take database backup in noarchivelog mode, your database must be in mount mode.
Steps to Backup a Database in Noarchivelog Mode :
Step-1. Shutdown Database :
SQL> SQL> shut immediate; Database closed. Database dismounted. ORACLE instance shut down. SQL>
Step-2. Startup Database in mount stage :
SQL> startup mount; ORACLE instance started. Total System Global Area 759165480 bytes Fixed Size 8901160 bytes Variable Size 285212672 bytes Database Buffers 461373440 bytes Redo Buffers 3678208 bytes Database mounted. SQL>
Step-3. Connect with RMAN and take backup :
[oracle@node-1 ~]$ rman target / Recovery Manager: Release 184.108.40.206.0 - Production on Sat May 1 11:36:18 2021 Version 220.127.116.11.0 Copyright (c) 1982, 2019, Oracle and/or its affiliates. All rights reserved. connected to target database: ORCL (DBID=1595923691, not open) RMAN> backup database; Starting backup at 01-MAY-21 using target database control file instead of recovery catalog allocated channel: ORA_DISK_1 channel ORA_DISK_1: SID=429 device type=DISK file 2 is excluded from whole database backup file 5 is excluded from whole database backup channel ORA_DISK_1: starting full datafile backup set channel ORA_DISK_1: specifying datafile(s) in backup set input datafile file number=00001 name=/u01/app/oracle/oradata/ORCL/system01.dbf input datafile file number=00003 name=/u01/app/oracle/oradata/ORCL/sysaux01.dbf input datafile file number=00004 name=/u01/app/oracle/oradata/ORCL/undotbs01.dbf input datafile file number=00007 name=/u01/app/oracle/oradata/ORCL/users01.dbf channel ORA_DISK_1: starting piece 1 at 01-MAY-21 channel ORA_DISK_1: finished piece 1 at 01-MAY-21 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/backupset/2021_05_01/o1_mf_nnndf_TAG20210501T113643_j8svzn0d_.bkp tag=TAG20210501T113643 comment=NONE channel ORA_DISK_1: backup set complete, elapsed time: 00:01:06 Finished backup at 01-MAY-21 Starting Control File and SPFILE Autobackup at 01-MAY-21 piece handle=/u01/app/oracle/fast_recovery_area/ORCL/autobackup/2021_05_01/o1_mf_s_1071401664_j8sw1p9o_.bkp comment=NONE Finished Control File and SPFILE Autobackup at 01-MAY-21 RMAN>
I hope my written content will helped you. Your suggestions/feedback are most welcome from orakldba.com.
Keep learning… Have a great day!!!
Please comment here for your any query related to above content. You can write to mail me through : email@example.com.