Impact on changing log_archive_format parameter

From: Mandal, Ashoke <ashoke.k.mandal_at_medtronic.com>
Date: Tue, 3 Jul 2012 21:05:23 -0500
Message-ID: <6548C7B531E1364BAE8F77112F31A119BDE2E905_at_MSPM1BMSGM22.ent.core.medtronic.com>



Hello all,

I am standardizing the archive log file format for all of my databases and implemented the log_archive_format parameter as follows: In mydb1:
 %t_%s_%r.dbf was changed to mydb1_%s_%t_%r.arc. In mydb2:
mydb2_%s_%t_%r.log was changed to mydb2_%s_%t_%r.arc.

Do you anticipate any issue for recovery of the database from a stage prior to the log_archive_format change?

Thanks,
Ashoke

[CONFIDENTIALITY AND PRIVACY NOTICE] Information transmitted by this email is proprietary to Medtronic and is intended for use only by the individual or entity to which it is addressed, and may contain information that is private, privileged, confidential or exempt from disclosure under applicable law. If you are not the intended recipient or it appears that this mail has been forwarded to you without proper authority, you are notified that any use or dissemination of this information in any manner is strictly prohibited. In such cases, please delete this mail from your records.  

To view this notice in other languages you can either select the following link or manually copy and paste the link into the address bar of a web browser: http://emaildisclaimer.medtronic.com

--
http://www.freelists.org/webpage/oracle-l
Received on Tue Jul 03 2012 - 21:05:23 CDT

Original text of this message