You don't need to rebuild when a datafile is added. Once the recovery fails
you just issue the create datafile command on the standby.
Jay Miller
-Original Message-
Sent: Tuesday, November 05, 2002 12:34 PM
To: Multiple recipients of list ORACLE-L
2k
First off, your process is doing a
Right. Stand-by is exactly what you are trying to simulate. The archive logs
will reproduce 99% of what happens in the production environment. In
addition, it will provide for a quicker recovery.
AT
From: Miller, Jay [EMAIL PROTECTED]
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients
Yechiel Adar,
Use standby database, and you won't lost any transaction if your
online redo log is there.
To add a datafile, just add it in the standby database , no need to
rebuild the standby database.
Global name have nothing to do with standby,
Hello
You did not write if you bring both databases on every night or the backup
is down until needed.
If it is down you have no problem.
If you bring both up you can change the global name :
Alter database rename global_name to backupdb;
BTW - I am not sure that 8.1.7 need global_name=true.
We
First off, your process is doing a lot of unnecessary work.
Standby databases are available in 7.3.4. I believe that
would be somewhat simpler than your current procedure.
I haven't tried it though, so I could be wrong.
Even with your current procedure, you don't need to copy
all of the files,
Hello Jared
If I run the database in Standby mode, once my production server fails, can
the standby database be opened for users to make changes (i.e. read an
write) and how do I accomplish that.
Also, once my production server is back on line, how do you suggest I should
synchronize the
Hi Arif,
Please read the article Note: 76373.1 on Metalink about Standby database.
Regards,
Quamrul Polash
From: "Arif Khan (GWL)" <[EMAIL PROTECTED]>
Reply-To: [EMAIL PROTECTED]
To: Multiple recipients of list ORACLE-L <[EMAIL PROTECTED]>
Subject: RE: Clone Production Server to Stand by
