Category:OpenSwitch - Revision history

Psap at 19:31, 27 January 2008

2008-01-27T19:31:37Z

Psap at 13:39, 17 March 2006

2006-03-17T13:39:33Z

Psap at 13:37, 17 March 2006

2006-03-17T13:37:08Z

Psap at 13:35, 17 March 2006

2006-03-17T13:35:36Z

Psap at 13:34, 17 March 2006

2006-03-17T13:34:39Z

Psap at 13:32, 17 March 2006

2006-03-17T13:32:31Z

New page

==Manual Failover==
The failback procedure for an active-standby ASE setup (with OpenSwitch and optionally RCM) has been documented by Sybase but a manual failover not. This procedure is documented below. You can use it when you want to perform maintenance on the active database server and need to transfer connections in a controlled manner to the standby ASE.
The procedure assumes you are using RCM.
* Logon to OpenSwitch as the administrative user
* Lock the active database server so new connections cannot be made: rp_server_status <active-ase>,locked
* Stop sessions from invoking new transactions: rp_stop null,<active-ase>,null,1,1
* Logon to the active ASE
* Monitor the progress of the RepAgent until all transactions have been transfered to the Replication Server: sp_help_rep_agent <database>,"scan"
* Kill the cmon user in ASE and do a shutdown: kill <cmon-user-spid> shutdown
* Logon to OpenSwitch as the administrative user
* Resume session activity: rp_start null,<active-ase>,null
* Change the server-status to up: rp_server_status <active-ase>,up
* Initiate a new session to the active ASE through OpenSwitch: isql -U<user> -P<password> -S<openswitch>. When you have done this RCM will see that the active ASE is down and it will start the failover process.
When you have used this procedure you can be sure that all connections are transfered without the need to logon again. Also, all transactions made on the active ASE are guaranteed to be delivered at the Replication Server.

[[Category:OpenSwitch]]

← Older revision	Revision as of 19:31, 27 January 2008
Line 1:	Line 1:
	+	[[image:osw.jpg]]

	+	This page serves as an index to topics related to the Open Switch product of Sybase.

← Older revision		Revision as of 13:39, 17 March 2006
Line 1:		Line 1:
−	~~[[Configuration Settings]]~~	+

← Older revision	Revision as of 13:37, 17 March 2006
Line 1:	Line 1:
−	+	[[Configuration Settings]]

← Older revision		Revision as of 13:35, 17 March 2006
Line 1:		Line 1:
−	~~[[Manual Failover]]~~	+

@@ Line 1: / Line 1: @@
-==Manual Failover==
+[[Manual Failover]]
-The failback procedure for an active-standby ASE setup (with OpenSwitch and optionally RCM) has been documented by Sybase but a manual failover not. This procedure is documented below. You can use it when you want to perform maintenance on the active database server and need to transfer connections in a controlled manner to the standby ASE.
-The procedure assumes you are using RCM.
-* Logon to OpenSwitch as the administrative user
-* Lock the active database server so new connections cannot be made: rp_server_status <active-ase>,locked
-* Stop sessions from invoking new transactions: rp_stop null,<active-ase>,null,1,1
-* Logon to the active ASE
-* Monitor the progress of the RepAgent until all transactions have been transfered to the Replication Server: sp_help_rep_agent <database>,"scan"
-* Kill the cmon user in ASE and do a shutdown: kill <cmon-user-spid> shutdown
-* Logon to OpenSwitch as the administrative user
-* Resume session activity: rp_start null,<active-ase>,null
-* Change the server-status to up: rp_server_status <active-ase>,up
-* Initiate a new session to the active ASE through OpenSwitch: isql -U<user> -P<password> -S<openswitch>. When you have done this RCM will see that the active ASE is down and it will start the failover process.
-When you have used this procedure you can be sure that all connections are transfered without the need to logon again. Also, all transactions made on the active ASE are guaranteed to be delivered at the Replication Server.
-−
-[[Category:OpenSwitch]]