I would simplify step #7 by adding a second ADDRESS entry in the tnsnames.ora file. Below is a snippet of one of our tnsnames.ora file that could be used for automating the re-pointing of the users. Actually, it's more of a silent redirection than an automation of a manual step. The TNS layer will try to connect to dbname on the primary host. If it doesn't reach a listener then it will attempt to connect to dbname on the standby host. For this to work properly it is very important that steps #6 and #8 are completed in order. If TNS finds a listner on the primary host (port 4321 in the example) it will attempt to connect to the database on it and, not finding the instance, will fail returning a TNS-125..... error. This setup can be a real time-saver when you have many distributed clients that use local TNS files, especially the troubleshooting of post-standby activation connectivity problems.
HTH
Tony Aponte
dbname.world=
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS =
(COMMUNITY = tcp.world)
(PROTOCOL = TCP)
(Host = primaryhost)
(Port = 4321)
)
(ADDRESS =
(COMMUNITY = tcp.world)
(PROTOCOL = TCP)
(Host = standbyhost)
(Port = 1521)
)
)
(CONNECT_DATA =
(SID = dbname)
)
)
-----Original Message-----
From: Kevin Lange [mailto:[EMAIL PROTECTED]]
Sent: Monday, October 22, 2001 4:40 PM
To: Multiple recipients of list ORACLE-L
Subject: RE: switchover with standby database
A broad process overview:
Process:
1. Notification comes in of a down production. -- This needs to be very
reliable.
2. Make sure production is completely down. --> Look for pmon and smon
processes and see if connections are possible.
3. Bring any remaining logs over to the standby --> Use your same process
you are using now or a seperate script.
4. Perform an "alter database activate standby database" on the standby -->
simple script using svrmgrl on a unix box.
5. Apply the logs --> Recover database command
6. Shut down the listener --> lsnrctl stop
7. Copy in the new listener configuration files so that users are now
pointing to the standby --> simple os copy command
8. Bring up the listener -- lsnrctl start
All of this could easily be done in an os script.
-----Original Message-----
Sent: Monday, October 22, 2001 1:57 PM
To: Multiple recipients of list ORACLE-L
Thanks a lot Kevin !
I thought of it , hope everything will work , i have no choice actually.
Regarding bullet #3 - this is exactly what i'm asking - how can i automate
the open of the standby ?
Thanks a lot !
-----Original Message-----
Sent: Monday, October 22, 2001 8:25 PM
To: Multiple recipients of list ORACLE-L
Keep a couple things in mind when you talk about automating a standby
process:
1. You need to make sure your logs are completely up to date.
2. When you do change from live to the standby, you need to change your
listeners.
3. You would need to automate the open of the standby as well.
4. You need to make sure this is foolproof. I would hate to have my standby
come up prematurely. Remember, after it goes into live mode, you can not
put it back as a standby. At that point, you re rebuilding the standby.
-----Original Message-----
Sent: Monday, October 22, 2001 12:50 PM
To: Multiple recipients of list ORACLE-L
Dear gurus !
I'm about to implement Oracle standby database using oracle 8.0.5 .
I need automatic switchover in case of primary site failure , i.e. i need
the standby (secondary) database to get opened automatically should the
primary site fail.
Is there a way to achieve this ?
I know that there is automated failover capability in 8i managed standby ,
but we use 8.0.5 :-(
Thanks in advance .
Andrey
--
Please see the official ORACLE-L FAQ: http://www.orafaq.com
--
Author: Andrey Bronfin
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (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.com
--
Author: Kevin Lange
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (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.com
--
Author: Andrey Bronfin
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (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.com
--
Author: Kevin Lange
INET: [EMAIL PROTECTED]
Fat City Network Services -- (858) 538-5051 FAX: (858) 538-5051
San Diego, California -- Public Internet access / Mailing Lists
--------------------------------------------------------------------
To REMOVE yourself from this mailing list, send an E-Mail message
to: [EMAIL PROTECTED] (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).
