{"id":1179,"date":"2009-09-11T12:22:22","date_gmt":"2009-09-11T16:22:22","guid":{"rendered":"http:\/\/onlineappsdba.com\/index.php\/2009\/09\/11\/oracle-database-incarnation-open-resetlogs-scn\/"},"modified":"2009-09-11T12:26:43","modified_gmt":"2009-09-11T16:26:43","slug":"oracle-database-incarnation-open-resetlogs-scn","status":"publish","type":"post","link":"https:\/\/onlineappsdba.com\/index.php\/2009\/09\/11\/oracle-database-incarnation-open-resetlogs-scn\/","title":{"rendered":"Oracle Database Incarnation : Open Resetlogs , SCN"},"content":{"rendered":"

Q.<\/strong> What happens when you run ALTER DATABASE OPEN RESETLOGS ?
\n<\/strong>The current online redo logs are archived, the log sequence number is reset to 1, new database incarnation<\/strong> is created, and the online redo logs are given a new time stamp and SCN<\/strong>.
\n.<\/p>\n

Q. In what scenarios open resetlogs required ?<\/strong><\/p>\n

An ALTER DATABASE OPEN RESETLOGS statement is required after incomplete recovery (Point in Time Recovery) or recovery with a backup control file.
\n.<\/p>\n

Q. What is SCN (System Change Number) ?<\/strong><\/p>\n

The system change number (SCN) is an ever-increasing value that uniquely identifies a committed version of the database at a point in time. Every time a user commits a transaction Oracle records a new SCN in redo logs.<\/p>\n

Oracle uses SCNs in control files datafile headers and redo records. Every redo log file has both a log sequence number and low and high SCN. The low SCN records the lowest SCN recorded in the log file while the high SCN records the highest SCN in the log file.
\n.<\/p>\n

Q. What is Database Incarnation ?<\/strong><\/p>\n

\"database<\/a><\/strong><\/p>\n

Database incarnation is effectively a new “version<\/strong>” of the database that happens when you reset the online redo logs using “alter database open resetlogs<\/strong>;”.<\/p>\n

Database incarnation falls into following category Current<\/strong>, Parent<\/strong>, Ancestor<\/strong> and Sibling<\/strong><\/p>\n

i) Current Incarnation<\/strong> : The database incarnation in which the database is currently generating redo.<\/p>\n

ii) Parent Incarnation<\/strong> : The database incarnation from which the current incarnation branched following an OPEN RESETLOGS operation.<\/p>\n

iii) Ancestor Incarnation<\/strong> : The parent of the parent incarnation is an ancestor incarnation. Any parent of an ancestor incarnation is also an ancestor incarnation.<\/p>\n

iv) Sibling Incarnation <\/strong>: Two incarnations that share a common ancestor are sibling incarnations if neither<\/strong> one is an ancestor of the other.
\n.<\/p>\n

Q. How to view incarnation\u00a0history of Database ?<\/strong><\/p>\n

Using SQL> select * from v$database_incarnation<\/strong>;
\nUsing\u00a0RMAN>LIST INCARNATION<\/strong>;<\/p>\n

However, you can use the RESET DATABASE TO INCARNATION<\/strong> command to specify that SCNs are to be interpreted in the frame of reference of another incarnation.<\/p>\n

\u2022For example my current database INCARNATION is 3 and now I have used
\nFLASHBACK DATABASE TO SCN 3000;then SCN 3000 will be search in current incarnation which is 3. However if I want to get back to SCN 3000 of INCARNATION 2 then I have to use,<\/p>\n

RMAN> RESET DATABASE TO INCARNATION 2;
\nRMAN> RECOVER DATABASE TO SCN 3000;
\n.<\/p>\n

References\/Related<\/strong><\/u><\/p>\n