Shulou(Shulou.com)06/01 Report--

This article shows you how to study reset incarnation, the content is concise and easy to understand, can definitely brighten your eyes, through the detailed introduction of this article, I hope you can get something.

-- first perform a full library backup on entity 5

RMAN > backup database format='c:\ bak\% U.bak'

Launch backup in 26-March-08

Assigned channel: ORA_DISK_1

Channel ORA_DISK_1: sid=142 devtype=DISK

Channel ORA_DISK_1: starts the backup set of all data files

Channel ORA_DISK_1: specifying data files in the backup set

Enter the data file fno=00001 name=E:\ ORACLE\ PRODUCT\ 10.2.0\ ORADATA\ ORCL\ SYSTEM01.DBF

Enter the data file fno=00002 name=E:\ ORACLE\ PRODUCT\ 10.2.0\ ORADATA\ ORCL\ UNDOTBS01.DBF

Enter the data file fno=00003 name=E:\ ORACLE\ PRODUCT\ 10.2.0\ ORADATA\ ORCL\ SYSAUX01.DBF

Enter the data file fno=00004 name=E:\ ORACLE\ PRODUCT\ 10.2.0\ ORADATA\ ORCL\ USERS01.DBF

Channel ORA_DISK_1: starting segment 1 from 26 to March to 08

Channel ORA_DISK_1: completed segment 1 from 27 to March to 08

Segment handle = C:\ BAK\ 0QJC96UQ_1_1.BAK tag = TAG20080326T235922 comment = NONE

Channel ORA_DISK_1: backup set completed, elapsed time: 00:01:05

Channel ORA_DISK_1: starts the backup set of all data files

Channel ORA_DISK_1: specifying data files in the backup set

The backup set includes the current control file

Include the current SPFILE in the backup set

Channel ORA_DISK_1: starting segment 1 from 27 to March to 08

Channel ORA_DISK_1: completed segment 1 from 27 to March to 08

Segment handle = C:\ BAK\ 0RJC970R_1_1.BAK tag = TAG20080326T235922 comment = NONE

Channel ORA_DISK_1: backup set completed, elapsed time: 00:00:04

Completion of backup in 27-March-08

-- close the database, delete the current log file, and force open resetlogs to open the database

RMAN > shutdown immediate

The database is closed

Database has been uninstalled

Oracle instance is closed

RMAN > startup

Connected to the target database (not started)

Oracle instance has been started

The database is mounted

The database is open

The total system global area is 314572800 bytes

Fixed Size 1248768 byt

Variable Size 79692288 byt

Database Buffers 226492416 byt

Redo Buffers 7139328 byt

RMAN > shutdown immediate

The database is closed

Database has been uninstalled

Oracle instance is closed

RMAN > startup mount

Connected to the target database (not started)

Oracle instance has been started

The database is mounted

The total system global area is 314572800 bytes

Fixed Size 1248768 byt

Variable Size 79692288 byt

Database Buffers 226492416 byt

Redo Buffers 7139328 byt

RMAN > recover database

Launch recover on 27-March-08

Assigned channel: ORA_DISK_1

Channel ORA_DISK_1: sid=157 devtype=DISK

Starting media recovery

Unable to recover media

RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =

RMAN-00571: =

RMAN-03002: the recover command (on 03Universe 27 RMAN-03002 at 00:08:47) failed

ORA-00283: recovery session canceled due to errors

RMAN-11003: failed during parsing / executing SQL statement: alter database recover if needed

Start

ORA-00283: the recovery session was cancelled due to an error

ORA-19909: data file 1 is an orphaned prototype

ORA-01110: data file 1:'e:\ ORACLE\ PRODUCT\ 10.2.0\ ORADATA\ ORCL\ SYSTEM01.DBF'

RMAN > alter database open resetlogs

The database is open

-after opening the database, entity 6 is formed.

RMAN > list incarnation

Database prototype list

DB keyword Inc keyword DB name DB ID STATUS reset SCN reset time

-

11 ORCL 1176767170 PARENT 1 10-March-08

2 2 ORCL 1176767170 PARENT 472611 25-March-08

3 3 ORCL 1176767170 PARENT 474163 25-March-08

4 4 ORCL 1176767170 PARENT 488631 26-March-08

5 5 ORCL 1176767170 PARENT 490308 26-March-08

6 6 ORCL 1176767170 CURRENT 506067 27-March-08

-- close the database again, delete the current log file, and open resetlogs through sqlplus to form entity 7

RMAN > shutdown immediate

The database is closed

Database has been uninstalled

Oracle instance is closed

RMAN > quit

The recovery Manager is complete.

D:\ > rman target / nocatalog

Recovery Manager: Release 10.2.0.1.0-Production on Thursday March 27 00:18:13 2008

Copyright (c) 1982, 2005, Oracle. All rights reserved.

Connect to the target database: ORCL (DBID=1176767170)

Replace the recovery directory with the target database control file

RMAN > list incarnation

Database prototype list

DB keyword Inc keyword DB name DB ID STATUS reset SCN reset time

-

11 ORCL 1176767170 PARENT 1 10-March-08

2 2 ORCL 1176767170 PARENT 472611 25-March-08

3 3 ORCL 1176767170 PARENT 474163 25-March-08

4 4 ORCL 1176767170 PARENT 488631 26-March-08

5 5 ORCL 1176767170 PARENT 490308 26-March-08

6 6 ORCL 1176767170 PARENT 506067 27-March-08

7 7 ORCL 1176767170 CURRENT 506961 27-March-08

-- found that there are objects missing and need to be recovered based on time, but the lost objects occurred during the operation of entity 5, so the backup of entity 5 was used for incomplete recovery.

RMAN > shutdown immediate

The database is closed

Database has been uninstalled

Oracle instance is closed

RMAN > startup mount

Connected to the target database (not started)

Oracle instance has been started

The database is mounted

The total system global area is 314572800 bytes

Fixed Size 1248768 byt

Variable Size 79692288 byt

Database Buffers 226492416 byt

Redo Buffers 7139328 byt

-- directly execute the restore command to report an error, because it is currently entity 7, and the time of entity 7 is after the time that needs to be restored

RMAN > run {

2 > sql 'alter session set nls_date_format= "yyyy-mm-dd hh34:mi:ss"'

3 > set until time='2008-3-27 0014 02purl 00'

4 > restore database

5 > recover database

6 > alter database open resetlogs

7 >}

Sql statement: alter session set nls_date_format= "yyyy-mm-dd hh34:mi:ss"

Executing command: SET until clause

RMAN-00569: = ERROR MESSAGE STACK FOLLOWS =

RMAN-00571: =

RMAN-03002: the set command (on 03Universe 27 RMAN-03002 at 00:28:18) failed

RMAN-20207: UNTIL TIME or RECOVERY WINDOW before RESETLOGS time

-- reset the database entity to 5, and then perform a time-based recovery

RMAN > reset database to incarnation 5

Reset the database to prototype 5

RMAN > run {

2 > sql 'alter session set nls_date_format= "yyyy-mm-dd hh34:mi:ss"'

3 > set until time='2008-3-27 0014 02purl 00'

4 > restore database

5 > recover database

6 > alter database open resetlogs

7 >}

Sql statement: alter session set nls_date_format= "yyyy-mm-dd hh34:mi:ss"

Executing command: SET until clause

Launch restore on 27-March-08

Assigned channel: ORA_DISK_1

Channel ORA_DISK_1: sid=157 devtype=DISK

Channel ORA_DISK_1: starting to restore data file backup sets

Channel ORA_DISK_1: specifying datafiles to restore from the backup set

Restoring data file 00001 to E:\ ORACLE\ PRODUCT\ 10.2.0\ ORADATA\ ORCL\ SYSTEM01.DBF

Restoring data file 00002 to E:\ ORACLE\ PRODUCT\ 10.2.0\ ORADATA\ ORCL\ UNDOTBS01.DBF

Restoring data file 00003 to E:\ ORACLE\ PRODUCT\ 10.2.0\ ORADATA\ ORCL\ SYSAUX01.DBF

Restoring data file 00004 to E:\ ORACLE\ PRODUCT\ 10.2.0\ ORADATA\ ORCL\ USERS01.DBF

Channel ORA_DISK_1: reading backup segment C:\ BAK\ 0QJC96UQ_1_1.BAK

Channel ORA_DISK_1: backup segment 1 restored

Segment handle = C:\ BAK\ 0QJC96UQ_1_1.BAK tag = TAG20080326T235922

Channel ORA_DISK_1: recovery completed. Time: 00:01:05

Completion of restore in 27-March-08

Launch recover on 27-March-08

Use channel ORA_DISK_1

Starting media recovery

Archive log thread 1 sequence 3 has been used as file E:\ ORACLE\ PRODUCT\ 10.2.0\ FLASH_RECOVERY_AREA\ OR

CL\ ARCHIVELOG\ 2008 / 03 / 27\ O1_MF_1_3_3YNWZ1KL_.ARC exists on disk

Archive log file name = E:\ ORACLE\ PRODUCT\ 10.2.0\ FLASH_RECOVERY_AREA\ ORCL\ ARCHIVELOG\ 200

8'03'27\ O1_MF_1_3_3YNWZ1KL_.ARC thread = 1 sequence = 3

Media recovery complete, time: 00:00:02

Completion of recover in 27-March-08

The database is open

-- the restore is complete, and because the database is opened again using open resetlogs, the entity is now 8, while the scn of entity 8 is lower than that of entities 6 and 7

RMAN > list incarnation

Database prototype list

DB keyword Inc keyword DB name DB ID STATUS reset SCN reset time

-

11 ORCL 1176767170 PARENT 1 10-March-08

2 2 ORCL 1176767170 PARENT 472611 25-March-08

3 3 ORCL 1176767170 PARENT 474163 25-March-08

4 4 ORCL 1176767170 PARENT 488631 26-March-08

5 5 ORCL 1176767170 PARENT 490308 26-March-08

8 8 ORCL 1176767170 CURRENT 505314 27-March-08

6 6 ORCL 1176767170 ORPHAN 506067 27-March-08

7 7 ORCL 1176767170 ORPHAN 506961 27-March-08

RMAN >

It can be seen from the above that cross-entity recovery is feasible, but, hehe, there must be a backup of the entity in the past, otherwise it will be powerless.

The above content is how to study reset incarnation. Have you learned any knowledge or skills? If you want to learn more skills or enrich your knowledge reserve, you are welcome to follow the industry information channel.

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.