Re: What not to do in a standby environment ?
- From: Scott Dial <smd@xxxxxxxxxxxxxxxxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Tue, 7 Dec 2004 07:36:44 -0500
A few things I might add:
Don't take your database out of archivelog mode (obviously). You'll have to
start planning out your upgrades when you move into higher releases a lot more
carefully.
We have automated the creation of datafiles, so when one is created on the
primary servers, the log eventually gets sent to the standby server. When the
db apply process runs and figures out a file is missing, it automatically stops
and adds the file, then restarts. Just make sure your unix admins are onboard,
because when they add space to local servers they'll need to make sure they're
doing the same at your DR site.
If you use EMC, they have some tools (SRDF) that can be used to completely
avoid the use of Oracle's DR (Disaster Recovery) products in favor of shipping
every changed block to the DR site.
http://www.emc.com/products/networking/srdf.jsp
smd
+++ Prem Khanna J [07/12/04 10:40 -0000]:
> Hi Friends,
> I would like to know the list of "NOT TO DO" on
> Primary database in Standby database environment.
> And how to rectify, in case , it's done.
>
> i have a partial list like ...
> NOLOGGING , CLEAR ARCHIVE , RECREATE CONTROL FILE,
> RESETLOGS , ARCHIVE LOG STOP
>
> Please do let me know if you have come across
> anything that's it left out from the docs in case
> of standby database DONT'S.
>
> Note:120855.1 has got some , but it seems to miss
> things like NOLOGGING operations . If someone has
> one such list , can you share it with me ?
>
> The environment is oracle 8.1.7.4/Solrais 9.
>
> Any pointers would be of immense help.TIA.
>
> Regards,
> Prem.
> --
> //www.freelists.org/webpage/oracle-l
- smd
------------------------------
http://triquetra.homelinux.org
AIM Screen Name: orclrox
ICQ: 320591667
------------------------------
--
//www.freelists.org/webpage/oracle-l
Other related posts:
