Re: DBPITR and ORA-16005 Error: database requires recovery.
Date: Fri, 2 May 2008 12:53:43 -0700 (PDT)
Message-ID: <edaf1264-acea-4cc1-8e89-5113a22d32d4@c65g2000hsa.googlegroups.com>
Hi David,
I don't think I understand. I was using the value of CURRENT_SCN from
V$DATABASE to identify the target SCN in the DBPITR process.
If I query my database :
SQL> SELECT CURRENT_SCN, CHECKPOINT_CHANGE# , RESETLOGS_CHANGE# FROM V
$DATABASE;
CURRENT_SCN CHECKPOINT_CHANGE# RESETLOGS_CHANGE#
----------- ------------------ ----------------- 8279191460 8279155540 8279155539
So CHECKPOINT_CHANGE# and RESETLOGS_CHANGE# are almost the same and lower than CURRENT_SCN.
If I force a checkpoint global and query again:
SQL> alter system checkpoint global;
System altered.
SQL> SELECT CURRENT_SCN, CHECKPOINT_CHANGE# , RESETLOGS_CHANGE# FROM V
$DATABASE;
CURRENT_SCN CHECKPOINT_CHANGE# RESETLOGS_CHANGE#
----------- ------------------ ----------------- 8279192016 8279192003 8279155539
Now, CHECKPOINT_CHANGE# and CURRENT_SCN are almost the same while RESETLOGS_CHANGE# remains constant to the SCN were the last RESETLOGS took place.
I am afraid that using RESETLOGS_CHANGE# in a DBPITR where I want to take the database up to a recent SCN will not be very helpful. Maybe I miss something, could you please explain what you mean?
Thanks,
Gonzalo. Received on Fri May 02 2008 - 14:53:43 CDT