Thanks DBA's,

OK, I recently restored the "PROD" database to another NT server as "DEV". 
Thanks for all your input. The best way to learn is to test.
Before I could open the database, I had to use the
RECOVER DATABASE UNTIL CANCEL USING BACKUP CONTROLFILE; option.
After cancelling without applying any logs, I was able to open the database 
with the RESETLOGS option.

The "PROD" database in running in ARCHIVELOG mode.
I am running the "DEV" database in NOARCHIVELOG mode.

If I change the ARCHIVE MODE to ARCHIVELOG on "DEV", can I apply the 
archived logs from "PROD" to "DEV" database daily?

What are the procedures?

Also could I have used the option NORESETLOGS ARCHIVELOG with the CREATE 
CONTROLFILE statement?

What are the requirements?


BTW,
I observed some Archived Logs on the PROD database with sequence numbers 
having a greater range than the current sequence.
For example, the current logs have sequence like Arc3685.1 while there are a 
few created at random from April to August with sequence numbers like 
Arc5164.1 to Arc5214.1.
What controls the sequence numbering for archived log files?
How can you explain the change of sequence numbers at random?

Regards,

Denmark W.
"Knowledge is power, but it is only useful if it is shared!"


_________________________________________________________________
Get your FREE download of MSN Explorer at http://explorer.msn.com/intl.asp

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- 
Author: Denmark Weatherburne
  INET: [EMAIL PROTECTED]

Fat City Network Services    -- (858) 538-5051  FAX: (858) 538-5051
San Diego, California        -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).

Reply via email to