Re: Advice on setting up a standby database of an OPS cluster

Standby setup in an OPS environment is a little tricky; but not too difficult. Unfortunately MetaLink doesn't provide a step-by-step doc to achieve the same. Here is a rough cut of the steps and of course, it's not perfect.

(1) You have mentioned it's a two node cluster; so you must have two threads of redo log files. Make sure the archive log has the SID name and the thread number in their names, along with sequence numbers.

(2) On the init.ora of the standby site, use the parameter STANDBY_NAME_CONVERT="PRIMDB",'STDBY" or something similar.

(3) On the primary use the command "ALTER DATABASE CREATE STANDBY CONTROLFILE AS '/tmp/ctl';"

(4) Ftp the file /tmp/ctl to the standby's controlfiles.

(5) Bring up the standby instance STARTUP NOMOUNT

(6) ALTER DATABASE MOUNT STANDBY DATABASE; (7) Now you have to make sure there are two threads on standby site, too. If not you have to manually create them. For example:

ALTER DATABASE ADD LOGFILE THREAD 2 GROUP XX ('...','...') SIZE 500K; (8) RECOVER STANDBY DATABASE UNTIL CANCEL; (9) On both nodes of the primary do a few log switches, ftp the archived logs to the STANDBY_ARCH_DEST of the standby and apply them. After the last one from all nodes of primary, issue a CANCEL.

(10) RECOVER MANAGED STANDBY DATABASE (11) Tail -f alert.log of the standby to see the archived logs are actually being applied.

Problems

The biggest problems you will face is the unequal load on the nodes of the OPS cluster. One node may generate an archive at a rate of one every fifteen minutes whereas the other generates at one every hour. Therefore the number of archived logs per thread will be different and may complicate the recovery process as the recovery has to be held till the SCN number from the late log can be applied. To simplify this, you could place a cron job to do an "ALTER SYSTEM SWITCH LOGFILE" every fifteen minutes on each node so that the archived logs are at least regularly applied to the standby.

Hope this helps.

Arup Nanda
www.proligence.com

• Original Message ----- To: "Multiple recipients of list ORACLE-L" <ORACLE-L_at_fatcity.com> Sent: Tuesday, April 08, 2003 9:48 AM

> My company is setting up a disaster recovery site for our node OPS
cluster.
> At the disaster recovery site we are setting up a non ops standby database
> for the cluster.
>
> My question is that,
> In the cluster we have 2 sets of archive logs being produced and each set
of
> archive logs the name contains the oracle sid for the node that produced
it.
> Will this cause problems with the automated recovery of the standby
> database?
>
> Database version 8.1.7.4
> O/S HP-UX 11.0
>
>
> Thank you,
>
> Bryan Rodrigues
> Elcom, Inc.
> Oracle Database Administrator
> --
> Please see the official ORACLE-L FAQ: http://www.orafaq.net
> --
> Author: Rodrigues, Bryan
> INET: BRodrigues_at_elcom.com
>
> Fat City Network Services -- 858-538-5051 http://www.fatcity.com
> San Diego, California -- Mailing list and web hosting services
> ---------------------------------------------------------------------
> To REMOVE yourself from this mailing list, send an E-Mail message
> to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
> the message BODY, include a line containing: UNSUB ORACLE-L
> (or the name of mailing list you want to be removed from). You may
> also send the HELP command for other information (like subscribing).
>
>

-- 
Please see the official ORACLE-L FAQ: http://www.orafaq.net
-- 
Author: Arup Nanda
  INET: orarup_at_hotmail.com

Fat City Network Services    -- 858-538-5051 http://www.fatcity.com
San Diego, California        -- Mailing list and web hosting services
---------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: ListGuru_at_fatcity.com (note EXACT spelling of 'ListGuru') and in
the message BODY, include a line containing: UNSUB ORACLE-L
(or the name of mailing list you want to be removed from).  You may
also send the HELP command for other information (like subscribing).