Explore Oracle-based RMAN_04 non-consistent backup

Exploring Oracle RMAN_04 for non-consistent backup is very simple. Only a short command is required. However, if you want to create a backup of a regular database, we do not recommend that you use

Exploring Oracle RMAN_04 for non-consistent backup is very simple. Only a short command is required. However, if you want to create a backup of a regular database, we do not recommend that you use

In the previous article, we mentioned consistent Database Backup (seeExplore Oracle-based RMAN_03 non-consistent backup), And the operation is very simple. You only need a short command to complete the process. However, if you want to create a regular database backup, we do not recommend using consistent backup or a simple name. Instead, you can use scripts to implement non-consistent backup.Backup + archive log + redoEffectively recover data to the last changed state, minimizing data loss.

Related reading:

Exploring the RMAN_01 concept of Oracle

Explore the basic use of RMAN_02 in Oracle

Explore Oracle-based RMAN_03 non-consistent backup

Explore Oracle-based RMAN_04 non-consistent backup

Explore RMAN_05 Incremental Backup in Oracle

Exploring Oracle's RMAN_06 backup policy

Create inconsistent backup

In addition, you can back up data without affecting the business of the database. Such a backup will be a non-consistent backup, so if you want to restore it, you canBackup + archive log + redoComeRecover the data from the last log switch instead of the data from the last backup.

1.1Check the archiving status:

SQL> archive log list;

Database log modeNo Archive Mode

Automaticarchival Disabled

Archivedestination USE_DB_RECOVERY_FILE_DEST

Oldest onlinelog sequence 9

Current logsequence 11

SQL>

Archive must be enabled

Status

Databaseclosed.

Databasedismounted.

ORACLE instanceshut down.

SQL> startup mount;

ORACLE instancestarted.

Total SystemGlobal Area 285212672 bytes

Fixed Size 1218968 bytes

VariableSize 79693416 bytes

DatabaseBuffers 197132288 bytes

RedoBuffers 7168000 bytes

Databasemounted.

Databasealtered.

Databasealtered.

SQL> colinstance_name format a15

INSTANCE_NAMESTATUS

---------------------------------------

WWLOPEN

SQL>

SQL> archive log list; ------Check the archiving status. It is already in the Archiving status.

Database log modeArchive Mode

Automatic archivalEnabled

Archivedestination USE_DB_RECOVERY_FILE_DEST

Oldest onlinelog sequence 9

Next logsequence to archive 11

Current logsequence 11

SQL>

1.2Execute backup (The backup command is actually the same as the consistent backup.)

1.2.1 Back up database

RMAN> backup database;

Starting backupat 23-MAY-12

Allocatedchannel: ORA_DISK_1

ChannelORA_DISK_1: sid = 145 devtype = DISK

ChannelORA_DISK_1: starting full datafile backupset

ChannelORA_DISK_1: specifying datafile (s) in backupset

Input datafilefno = 00001 name =/DBData/WWL/system01.dbf

Input datafilefno = 00003 name =/DBData/WWL/sysaux01.dbf

Input datafilefno = 00002 name =/DBData/WWL/undotbs01.dbf

Input datafilefno = 00004 name =/DBData/WWL/users01.dbf

ChannelORA_DISK_1: starting piece 1 at 23-MAY-12

ChannelORA_DISK_1: finished piece 1 at 23-MAY-12

Piecehandle =/DBBak/bak_WWL_05_23_0anbmtkr_1_1 tag = TAG20120523T121210 comment = NONE

ChannelORA_DISK_1: backup set complete, elapsed time: 00:01:46

Finished backupat 23-MAY-12

Starting ControlFile and SPFILE Autobackup at 23-MAY-12

Piecehandle =/DBSoft/product/10.2.0/db_1/dbs/c-5520179-20120523-00 comment = NONE

Finished ControlFile and SPFILE Autobackup at 23-MAY-12

RMAN>