Jay,
The parameter log_archive_start starts the archiver process. The 'alter
database archivelog' sets the database in archivelog mode so that archive
logs are not overwritten before they are archived.
Cheers,
Barry
Barry Scott
M&G Technical Services
Tel: 020 7548 3110
eMail: barry.[Email address protected]
|---------+--------------------------------------------------------->
| | "j" |
| | <oracledba-ezmlmshield-x52946469.[Email Address Removed] | azyDBA.com> |
| | |
| | 14/09/2004 09:57 |
| | |
|---------+--------------------------------------------------------->
>------------------------------------------------------------------------------------------------|
| |
| To: "LazyDBA Discussion" <[Email address protected] |
| cc: (bcc: Barry Scott/LON/M&G) |
| Subject: archivelog and hot back |
>------------------------------------------------------------------------------------------------|
Dear All,
I have two specific queries:
1) While changing from noarchivelog mode to archivelog mode , why it is
necessary to do "alter database open archivelog" even if log_archive_start
=true is set in the init.ora file.
2) During hot back when we give "alter tablespace <TSname> begin backup",
the header of datafiles are freezed, then where are transactions
associated with these datafiles are written?
Jay
DISCLAIMER: The information contained in this message is intended only and
solely for the addressed individual or entity indicated in this message and
for the exclusive use of the said addressed individual or entity indicated
in this message (or responsible for delivery
of the message to such person) and may contain legally privileged and
confidential information belonging to Tata Consultancy Services Limited. It
must not be printed, read, copied, disclosed, forwarded, distributed or
used (in whatsoever manner) by any person other than the
addressee. Unauthorized use, disclosure or copying is strictly prohibited
and may constitute unlawful act and can possibly attract legal action,
civil and/or criminal.
The contents of this message need not necessarily reflect or endorse the
views of Tata Consultancy Services Limited
on any subject matter. Any action taken or omitted to be taken based on
this message is entirely at your risk and neither the originator of this
message nor Tata Consultancy Services Limited takes any responsibility or
liability towards the same. Opinions, conclusions and any other
information contained in this message that do not relate to the official
business of Tata Consultancy Services Limited shall be understood as
neither given nor endorsed by Tata Consultancy Services Limited or any
affiliate of Tata Consultancy Services Limited. If you have received this
message in error,
you should destroy this message and may please notify the sender by e-mail.
Thank you.
--------
website: http://www.LazyDBA.com
Please don't reply to RTFM questions
Oracle documentation is here: http://tahiti.oracle.com
To unsubscribe: see http://www.lazydba.com/unsubscribe.html
To subscribe: see http://www.lazydba.com
By using this list you agree to these terms:
http://www.lazydba.com/legal.html
Message ID - T6c08c989dec0a8131154c
The information contained in this message may be CONFIDENTIAL and is intended for the addressee only. Any unauthorised use, dissemination of the information, or copying of this message is prohibited. If you are not the addressee, please notify the sender immediately by return e-mail and delete this message. Although this e-mail and any attachments are believed to be free of any virus, or other defect which might affect any computer or system into which they are received and opened, it is the responsibility of the recipient to ensure that they are virus free and no responsibility is accepted by M&G for any loss or damage from receipt or use thereof.
Please note that all e-mail messages are subject to interception for lawful business purposes.
Oracle LazyDBA home page