RMAN backup and recovery - RAC environment, the database backup (1)
RMAN backup and recovery - RAC environment, the database backup (1): http://yangtingkun.itpub.net/post/468/285260
RMAN backup and recovery - RAC environment, the database backup (2): http://yangtingkun.itpub.net/post/468/287076
RMAN backup and recovery - RAC environment, the database backup (3): http://yangtingkun.itpub.net/post/468/287617
RMAN backup and recovery - RAC environment, the database backup (4): http://yangtingkun.itpub.net/post/468/288295
RMAN backup and recovery - RAC environment, the database backup (5): http://yangtingkun.itpub.net/post/468/288557
RMAN backup and recovery - RAC environment, the database backup (6): http://yangtingkun.itpub.net/post/468/288973
RMAN backup and recovery - RAC environment, the database backup (7): http://yangtingkun.itpub.net/post/468/289665
RMAN backup and recovery - RAC environment, the database backup (8): http://yangtingkun.itpub.net/post/468/290599
RMAN backup and recovery - RAC environment, the database backup (9): http://yangtingkun.itpub.net/post/468/291018
RMAN backup and recovery - RAC environment, the database backup (10): http://pub.itpub.net/post/468/291415
This difference is mainly reflected in the particularity of the RAC environment.
According to Oracle's RAC environment, the different, RMAN backup, recovery operations are different. If the RAC environment is built on the CLUSTER file system, or is based on the ASM, then the backup and recovery process can be very simple and common database environment is basically not much difference. If the RAC environment is built on the bare device, because of archive log can not be stored on the bare device, then the archive log files must be placed on multiple nodes of the local hard disk, then backup and restore of the database becomes and the general environment vary.
Click here to first discuss the establishment of the RAC environment, ASM database backup. If the archive log on the ASM, then the two nodes can all be backed up, and this time, backup and general single-instance database, there is no difference.
SQL> SHOW PARAMETER LOG_ARCHIVE_DEST_1
NAME TYPE VALUE
------------------------------------ ----------- --- ---------------------------
log_archive_dest_1 string LOCATION = + DISK / testrac /
log_archive_dest_10 string
$ Rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Wednesday April 25 17:23:01 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to target database: TESTRAC (DBID = 4291216984)
RMAN> configure channel device type disk format '/ data1/backup /% U';
Using target database control file instead of recovery catalog old RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ data / backup / testrac /% U'; new RMAN configuration parameters:
CONFIGURE CHANNEL DEVICE TYPE DISK FORMAT '/ data1/backup /% U'; has been successfully stored new RMAN configuration parameters
RMAN> backup database plus archivelog delete all input;
-07 To start backup at 25-4 on the current log archived allocated channel: ORA_DISK_1 channel ORA_DISK_1: sid = 312 instance = testrac1 devtype = DISK channel ORA_DISK_1: Starting archive log backup set channel ORA_DISK_1: backup set is being specified archive log input archive log thread = 1 sequence = 134 timestamp = 620,832,208 records input archive log thread = 1 sequence = 135 timestamp = 620,846,651 records input archive log thread = 2 sequence = 56 Record timestamp = 620,831,921 input archive log thread = 2 sequence = 57 Record timestamp = 620,846,652 channel ORA_DISK_1: Starting in paragraph 1 was 25-4 on -07 channel ORA_DISK_1: paragraph 1 has been completed on the 25-4 month -07 Duan handle = / data1/backup/08ig2nhv_1_1 tag = TAG20070425T172413 Comment = NONE channel ORA_DISK_1: backup set has been completed, after a time: 00:00:07 channel ORA_DISK_1: Deleting archive log archive log filename = + DISK/testrac/1_134_618591128.dbf record timestamp = 620,832,208 archive log filename = + DISK / testrac / 1_135_618591128.dbf record timestamp = 620,846,651 archive log filename = + DISK/testrac/2_56_618591128.dbf record timestamp = 620,831,921 archive log filename = + DISK/testrac/2_57_618591128.dbf record timestamp = 620,846,652 to complete backup in the 25-4 -07 months
-07 To start backup at 25-4 on the use of channel ORA_DISK_1 channel ORA_DISK_1: Start all the data file backup sets channel ORA_DISK_1: backup set is being specified input data file data files fno = 00006 name = + DISK/testrac/datafile/zhejiang01.dbf input data file fno = 00007 name = + DISK/testrac/datafile/zhejiang02.dbf input data file fno = 00009 name = + DISK/testrac/datafile/zhejiang03.dbf input data file fno = 00011 name = + DISK / testrac / datafile / zhejiang04.dbf input data file fno = 00012 name = + DISK/testrac/datafile/zhejiang05.dbf input data file fno = 00014 name = + DISK/testrac/datafile/zhejiang06.dbf input data file fno = 00008 name = + DISK / testrac/datafile/ndmain01.dbf input data file fno = 00002 name = + DISK/testrac/datafile/undotbs1.263.618591197 input data file fno = 00004 name = + DISK/testrac/datafile/undotbs2.266.618591249 input data file fno = 00010 name = + DISK/testrac/datafile/ndindex01.dbf input data file fno = 00013 name = + DISK/testrac/datafile/lt_index_ts01.dbf input data file fno = 00001 name = + DISK/testrac/datafile/system.262.618591167 input data file fno = 00003 name = + DISK/testrac/datafile/sysaux.264.618591225 input data file fno = 00005 name = + DISK/testrac/datafile/users.267.618591279 channel ORA_DISK_1: Starting in paragraph 1 was 25-4 on -07 channel ORA_DISK_1: paragraph 1 has been completed on the 25-4 month -07 Duan handle = / data1/backup/09ig2ni9_1_1 tag = TAG20070425T172424 Comment = NONE channel ORA_DISK_1: backup set has been completed, after a time: 00:15:05 channel ORA_DISK_1: Start all the data files backup set channel ORA_DISK_1: backup set is being specified data file backup set including current control file in the backup set that contains the current SPFILE channel ORA_DISK_1: Starting in paragraph 1 was 25-4 on -07 channel ORA_DISK_1: paragraph 1 has been completed on the 25-4 On -07 segment handle = / data1/backup/0aig2oej_1_1 tag = TAG20070425T172424 Comment = NONE channel ORA_DISK_1: backup set has been completed, after a Time: 00:00:03 to complete backup in the 25-4 month -07
-07 To start backup at 25-4 on the current log archived using channel ORA_DISK_1 channel ORA_DISK_1: Starting archive log backup set channel ORA_DISK_1: is specified archive log backup set input archive log thread = 1 sequence = 136 timestamp = 620,847,576 records input archive log thread = 2 sequence = 58 Record timestamp = 620,847,576 channel ORA_DISK_1: Starting in paragraph 1 was 25-4 on -07 channel ORA_DISK_1: paragraph 1 has been completed on the 25-4 month -07 Duan handle = / data1/backup / 0big2oes_1_1 tag = TAG20070425T173940 Comment = NONE channel ORA_DISK_1: backup set has been completed, after a time: 00:00:02 channel ORA_DISK_1: Deleting archive log archive log filename = + DISK/testrac/1_136_618591128.dbf archive log record timestamp = 620,847,576 file name = + DISK/testrac/2_58_618591128.dbf record timestamp = 620,847,576 to complete backup in the 25-4 month -07
Database recovery is also very simple, first modify some data:
SQL> CONN TEST / TEST is connected.
SQL> SELECT COUNT (*) FROM T;
COUNT (*)
----------
0
SQL> INSERT INTO T SELECT ROWNUM FROM DBA_OBJECTS;
51880 rows created.
SQL> COMMIT;
To submit completed.
To begin the restoration and rehabilitation of the following:
$ Rman target /
Recovery Manager: Release 10.2.0.3.0 - Production on Thursday April 26 11:21:29 2007
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Is connected to the target database (not started)
RMAN> startup mount
Oracle instance started database has been loaded
Total System Global Area 2147483648 bytes
Fixed Size 2031480 bytes
Variable Size 318767240 bytes
Database Buffers 1811939328 bytes
Redo Buffers 14745600 bytes
RMAN> restore database;
-07 Month at 26-4 to start restore the use of channel ORA_DISK_1
Channel ORA_DISK_1: is beginning to restore the data file backup set channel ORA_DISK_1: backup set is being designated from the data file to restore the data file 00001 being restored to + DISK/testrac/datafile/system.262.618591167 being restored to 00002 data file + DISK / testrac / datafile/undotbs1.263.618591197 being restored to 00003 data file + DISK/testrac/datafile/sysaux.264.618591225 being restored to 00004 data file + DISK/testrac/datafile/undotbs2.266.618591249 being restored to 00005 data file + DISK / testrac/datafile/users.267.618591279 being restored to 00006 data file + DISK/testrac/datafile/zhejiang01.dbf being restored to 00007 data file + DISK/testrac/datafile/zhejiang02.dbf being restored to 00008 data file + DISK / testrac/datafile/ndmain01.dbf data files being restored to 00009 data file + DISK/testrac/datafile/zhejiang03.dbf being restored to 00010 data file + DISK/testrac/datafile/ndindex01.dbf being restored to + 00011 DISK/testrac/datafile/zhejiang04.dbf being restored to 00012 data file + DISK/testrac/datafile/zhejiang05.dbf data files being restored to 00013 data file + DISK/testrac/datafile/lt_index_ts01.dbf being restored to 00014 + DISK/testrac/datafile/zhejiang06.dbf channel ORA_DISK_1: backup segment is being read / data1/backup/09ig2ni9_1_1 channel ORA_DISK_1: restored backup of paragraph 1 above handle = / data1/backup/09ig2ni9_1_1 tag = TAG20070425T172424 channel ORA_DISK_1: restore complete with time: 00:20:26 to complete restore on 26-4 on -07
RMAN> restore archivelog sequence between 134 and 136 thread 1;
-07 Month at 26-4 to start restore the use of channel ORA_DISK_1
Channel ORA_DISK_1: Starting to the default target archive log restore channel ORA_DISK_1: archived log archive log is restored thread = 1 sequence = 134 channel ORA_DISK_1: archived log archive log is restored thread = 1 sequence = 135 channel ORA_DISK_1: backup segment is being read / data1/backup/08ig2nhv_1_1 channel ORA_DISK_1: restored backup of paragraph 1 above handle = / data1/backup/08ig2nhv_1_1 tag = TAG20070425T172413 channel ORA_DISK_1: restore complete, with time: 00:00:07 channel ORA_DISK_1: Starting to the default target archive log restore channel ORA_DISK_1: archived log archive log is restored thread = 1 sequence = 136 channel ORA_DISK_1: backup segment is being read / data1/backup/0big2oes_1_1 channel ORA_DISK_1: restored backup of paragraph 1 above handle = / data1/backup/0big2oes_1_1 tag = TAG20070425T173940 channel ORA_DISK_1: restore complete, with time: 00:00:01 to complete restore on 26-4 on -07
RMAN> restore archivelog sequence between 56 and 58 thread 2;
-07 Month at 26-4 to start restore the use of channel ORA_DISK_1
Channel ORA_DISK_1: Starting to the default target archive log restore channel ORA_DISK_1: archived log archive log is restored thread = 2 sequence = 56 channel ORA_DISK_1: archived log archive log is restored thread = 2 sequence = 57 channel ORA_DISK_1: backup segment is being read / data1/backup/08ig2nhv_1_1 channel ORA_DISK_1: restored backup of paragraph 1 above handle = / data1/backup/08ig2nhv_1_1 tag = TAG20070425T172413 channel ORA_DISK_1: restore complete, with time: 00:00:03 channel ORA_DISK_1: Starting to the default target archive log restore channel ORA_DISK_1: archived log archive log is restored thread = 2 sequence = 58 channel ORA_DISK_1: backup segment is being read / data1/backup/0big2oes_1_1 channel ORA_DISK_1: restored backup of paragraph 1 above handle = / data1/backup/0big2oes_1_1 tag = TAG20070425T173940 channel ORA_DISK_1: restore complete, with time: 00:00:01 to complete restore on 26-4 on -07
RMAN> recover database;
Recover from 26-4 to start using channel ORA_DISK_1 month -07
Are starting media recovery media recovery complete, with time: 00:00:38
-07 Months to complete recover in 26-4
RMAN> alter database open;
The database is open
Check whether restoration has been completed:
$ Sqlplus "/ as sysdba"
SQL * Plus: Release 10.2.0.3.0 - Production on Thursday April 26 13:29:14 2007
Copyright (c) 1982, 2006, Oracle. All Rights Reserved.
Been connected to the idle routine.
SQL> startup
ORACLE instance started.
Total System Global Area 2147483648 bytes
Fixed Size 2031480 bytes
Variable Size 318767240 bytes
Database Buffers 1811939328 bytes
Redo Buffers 14745600 bytes Database has finished loading. The database has been opened.
SQL> CONN TEST / TEST is connected.
SQL> SELECT COUNT (*) FROM T;
COUNT (*)
----------
51880
Related Posts of RMAN backup and recovery - RAC environment, the database backup (1)
-
ORACLE10G full version centos5 installed (the installation has passed)
ORACLE10G full version centos5 installed (the installation has passed) 1. Centos 5.0 install rn GUI must be installed, it is best not to start selinux rn rn rn 2. . Ready to install the software: (this is very important, is the first installation fai ...
-
SGA extended the principle of 32bit oracle
SGA extended the principle of 32bit oracle From: http://www.itpub.net/247048.html Because the median 32bitrnoracle restrictions can only visit the oracle process 4g (2 of 32 power) following virtual memory address, the time at a lot of people this is ...
-
SQL optimization (4) - Table of the three connections
Test the following three commonly used connection between the table: Sort - merge connected (sort-merge join, SMJ) Nested loops (nested loop, NL) Hash connection (hash join, HASH) 1. To create the test table SQL> select * from v $ version; BANNER ...
-
Dbms_obfuscation_toolkit use of Oracle's encryption and decryption of data (to)
In order to protect sensitive data, oracle start from 8i to provide a data encryption package: dbms_obfuscation_toolkit. Take advantage of this package, our data can be DES, Triple DES or MD5 encryption. This article on the use of this and the use of ...
-
Oracle XDB relax resolve port conflict of 8080
In this paper, carried: http://www.enet.com.cn/article/2008/0306/A20080306175452.shtml Oracle 9i from the start, Oracle includes the installation of the default XDB. After starting the database, Oracle XDB's http service will automatically take u ...
-
Oracle in the relationship between User and Schema
If we want to know the database and the User What is the relationship between Schema, we must first know about User and Schema database What is the concept in the end. In SQL Server2000 in architecture because of the reason, User and Schema there is ...
-
High Availability Oracle Flashback
Brief introduction Flashback Database is a point in time (PIT) restore the database approach. This incomplete recovery strategy can be used to restore the logic because of human error cause damage to the database. At the introduction of 10g, it is de ...
-
An example of the use of TKPROF
First, view and edit parameters SQL> show parameter max_dump_file_size NAME TYPE VALUE ------------------------------------ ----------- --- --------------------------- max_dump_file_size string UNLIMITED SQL> show parameter user_dump_dest NAME TYPE
-
Diagnosis and principles of order
SQL> select disk.value "Disk", mem.value "Mem", 2 (disk.value / mem.value) * 100 "Ratio" 3 from v $ sysstat mem, v $ sysstat disk 4 where mem.name = 'sorts (memory)' 5 and disk.name = 'sorts (disk)'; D ...
-
ORACLE 10G dataguard configuration Step by Step
oracle dataguard













Leave a Reply