archivelog and hot back

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.


Oracle LazyDBA home page