Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

replacing an existing standby server in ws

5 posts in General Discussion Last posting was on 2011-09-21 22:40:42.0Z
Isabella Posted on 2011-09-21 17:01:55.0Z
From: Isabella <isabella.ghiurea@nrc-cnrc.gc.ca>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: replacing an existing standby server in ws
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4e7a1883$1@forums-1-dub>
Date: 21 Sep 2011 10:01:55 -0700
X-Trace: forums-1-dub 1316624515 10.22.241.152 (21 Sep 2011 10:01:55 -0700)
X-Original-Trace: 21 Sep 2011 10:01:55 -0700, vip152.sybase.com
Lines: 12
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9064
Article PK: 870227

Hi All,
we have a ws standby system with Rep server( ASE 15.03, Rep 15.2), we
plan to replace the standby server host with a new host with upgraded
hardware and version of ASE 15.5 latest one. I plan to create a db
copy( dump/load) of primary and shutdown the existing standby and bring
the new new host standby online with same ip and ASE 's names as old
standby, would this work with no issues for Rep server?
Later one after draining the rep stable queues, we switch over and
have the new_host standby as our main primary active ASE, are there any
concerns I should be aware ?
Thank you
Isabella


"Mark A. Parsons" <iron_horse Posted on 2011-09-21 18:17:36.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: replacing an existing standby server in ws
References: <4e7a1883$1@forums-1-dub>
In-Reply-To: <4e7a1883$1@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4e7a2a40@forums-1-dub>
Date: 21 Sep 2011 11:17:36 -0700
X-Trace: forums-1-dub 1316629056 10.22.241.152 (21 Sep 2011 11:17:36 -0700)
X-Original-Trace: 21 Sep 2011 11:17:36 -0700, vip152.sybase.com
Lines: 27
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9065
Article PK: 870230

You'll want to take a look at the manuals on the steps for resyncing the RDB ... as that is, in essence, what you've
suggested (ie, dump PDB, load dump into RDB). One of the issues you'd have to address is any inflight transactions
between the PDB and RDB which end up getting applied to the RDB after it's been loaded from the PDB dump (eg, you could
end up with duplicate data and/or other issues related to applying a transaction twice to a database) - the instructions
on resyncing the RDB addresses this issue.

I'm thinking the easier solution would be to suspend the DSI into the oldRDB, dump the oldRDB, load the oldRDB dump into
the newRDB, shutdown the oldRDS (to make sure the DSI goes down if the hardware switch leaves the RS pointing at the
oldRDB), make sure the network addressing for the newRDS is the same as the oldRDS, then resume the DSI. At this point
the RS should think it's connecting to the same exact RDB. (You could also use a new network address (ip and/or port#)
for the newRDS ... you'd just need to update the RS's interfaces file so that when it resumes the DSI it picks up the
new/correct address from the interfaces file.)

Later, when you want to to switch over the new standby host to serve as your primary host ... sounds like a 'normal' WS
switch operation (see the 'switch active' command). If you haven't done a WS switch before I'd suggest running a few
tests in a dev/test environment to insure you understand all the steps necessary to perform a WS switch.

On 09/21/2011 13:01, Isabella wrote:
> Hi All,
> we have a ws standby system with Rep server( ASE 15.03, Rep 15.2), we plan to replace the standby server host with a new
> host with upgraded hardware and version of ASE 15.5 latest one. I plan to create a db copy( dump/load) of primary and
> shutdown the existing standby and bring the new new host standby online with same ip and ASE 's names as old standby,
> would this work with no issues for Rep server?
> Later one after draining the rep stable queues, we switch over and have the new_host standby as our main primary active
> ASE, are there any concerns I should be aware ?
> Thank you
> Isabella


"Mark A. Parsons" <iron_horse Posted on 2011-09-21 18:21:44.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: replacing an existing standby server in ws
References: <4e7a1883$1@forums-1-dub> <4e7a2a40@forums-1-dub>
In-Reply-To: <4e7a2a40@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4e7a2b38@forums-1-dub>
Date: 21 Sep 2011 11:21:44 -0700
X-Trace: forums-1-dub 1316629304 10.22.241.152 (21 Sep 2011 11:21:44 -0700)
X-Original-Trace: 21 Sep 2011 11:21:44 -0700, vip152.sybase.com
Lines: 33
X-Authenticated-User: TeamSybase
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9066
Article PK: 870236

Obviously (?) the whole suspend-DSI-dump-oldRDB-load-into-newRDB-resume-DSI operation assumes that your RS has a large
enough stable device to hold any backlog of transactions that will pile up while the DSI is down.

On 09/21/2011 14:17, Mark A. Parsons wrote:
> You'll want to take a look at the manuals on the steps for resyncing the RDB ... as that is, in essence, what you've
> suggested (ie, dump PDB, load dump into RDB). One of the issues you'd have to address is any inflight transactions
> between the PDB and RDB which end up getting applied to the RDB after it's been loaded from the PDB dump (eg, you could
> end up with duplicate data and/or other issues related to applying a transaction twice to a database) - the instructions
> on resyncing the RDB addresses this issue.
>
> I'm thinking the easier solution would be to suspend the DSI into the oldRDB, dump the oldRDB, load the oldRDB dump into
> the newRDB, shutdown the oldRDS (to make sure the DSI goes down if the hardware switch leaves the RS pointing at the
> oldRDB), make sure the network addressing for the newRDS is the same as the oldRDS, then resume the DSI. At this point
> the RS should think it's connecting to the same exact RDB. (You could also use a new network address (ip and/or port#)
> for the newRDS ... you'd just need to update the RS's interfaces file so that when it resumes the DSI it picks up the
> new/correct address from the interfaces file.)
>
> Later, when you want to to switch over the new standby host to serve as your primary host ... sounds like a 'normal' WS
> switch operation (see the 'switch active' command). If you haven't done a WS switch before I'd suggest running a few
> tests in a dev/test environment to insure you understand all the steps necessary to perform a WS switch.
>
> On 09/21/2011 13:01, Isabella wrote:
>> Hi All,
>> we have a ws standby system with Rep server( ASE 15.03, Rep 15.2), we plan to replace the standby server host with a new
>> host with upgraded hardware and version of ASE 15.5 latest one. I plan to create a db copy( dump/load) of primary and
>> shutdown the existing standby and bring the new new host standby online with same ip and ASE 's names as old standby,
>> would this work with no issues for Rep server?
>> Later one after draining the rep stable queues, we switch over and have the new_host standby as our main primary active
>> ASE, are there any concerns I should be aware ?
>> Thank you
>> Isabella


Isabella Posted on 2011-09-21 19:22:42.0Z
Message-ID: <4E7A3981.7040800@nrc-cnrc.gc.ca>
From: Isabella <isabella.ghiurea@nrc-cnrc.gc.ca>
User-Agent: Thunderbird 2.0.0.19 (X11/20090105)
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
To: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
Subject: Re: replacing an existing standby server in ws
References: <4e7a1883$1@forums-1-dub> <4e7a2a40@forums-1-dub> <4e7a2b38@forums-1-dub>
In-Reply-To: <4e7a2b38@forums-1-dub>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 21 Sep 2011 12:22:42 -0700
X-Trace: forums-1-dub 1316632962 10.22.241.152 (21 Sep 2011 12:22:42 -0700)
X-Original-Trace: 21 Sep 2011 12:22:42 -0700, vip152.sybase.com
Lines: 61
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9067
Article PK: 870233

Hi Mark,
Thank you for feedback, yes the stable rep queues is a decent size
around 40GB ,my concerns is this the new RDB host is a newer version of
ASE than old_RDB , so any issues for Rep here?
I have done the switch over from primary to standby server in the past
without to many issues .
Isabella
,

Mark A. Parsons wrote:
> Obviously (?) the whole
> suspend-DSI-dump-oldRDB-load-into-newRDB-resume-DSI operation assumes
> that your RS has a large enough stable device to hold any backlog of
> transactions that will pile up while the DSI is down.
>
>
>
> On 09/21/2011 14:17, Mark A. Parsons wrote:
>> You'll want to take a look at the manuals on the steps for resyncing
>> the RDB ... as that is, in essence, what you've
>> suggested (ie, dump PDB, load dump into RDB). One of the issues you'd
>> have to address is any inflight transactions
>> between the PDB and RDB which end up getting applied to the RDB after
>> it's been loaded from the PDB dump (eg, you could
>> end up with duplicate data and/or other issues related to applying a
>> transaction twice to a database) - the instructions
>> on resyncing the RDB addresses this issue.
>>
>> I'm thinking the easier solution would be to suspend the DSI into the
>> oldRDB, dump the oldRDB, load the oldRDB dump into
>> the newRDB, shutdown the oldRDS (to make sure the DSI goes down if the
>> hardware switch leaves the RS pointing at the
>> oldRDB), make sure the network addressing for the newRDS is the same
>> as the oldRDS, then resume the DSI. At this point
>> the RS should think it's connecting to the same exact RDB. (You could
>> also use a new network address (ip and/or port#)
>> for the newRDS ... you'd just need to update the RS's interfaces file
>> so that when it resumes the DSI it picks up the
>> new/correct address from the interfaces file.)
>>
>> Later, when you want to to switch over the new standby host to serve
>> as your primary host ... sounds like a 'normal' WS
>> switch operation (see the 'switch active' command). If you haven't
>> done a WS switch before I'd suggest running a few
>> tests in a dev/test environment to insure you understand all the steps
>> necessary to perform a WS switch.
>>
>> On 09/21/2011 13:01, Isabella wrote:
>>> Hi All,
>>> we have a ws standby system with Rep server( ASE 15.03, Rep 15.2), we
>>> plan to replace the standby server host with a new
>>> host with upgraded hardware and version of ASE 15.5 latest one. I
>>> plan to create a db copy( dump/load) of primary and
>>> shutdown the existing standby and bring the new new host standby
>>> online with same ip and ASE 's names as old standby,
>>> would this work with no issues for Rep server?
>>> Later one after draining the rep stable queues, we switch over and
>>> have the new_host standby as our main primary active
>>> ASE, are there any concerns I should be aware ?
>>> Thank you
>>> Isabella


"Mark A. Parsons" <iron_horse Posted on 2011-09-21 22:40:42.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 5.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.rep-server
Subject: Re: replacing an existing standby server in ws
References: <4e7a1883$1@forums-1-dub> <4e7a2a40@forums-1-dub> <4e7a2b38@forums-1-dub> <4E7A3981.7040800@nrc-cnrc.gc.ca>
In-Reply-To: <4E7A3981.7040800@nrc-cnrc.gc.ca>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <4e7a67ea@forums-1-dub>
Date: 21 Sep 2011 15:40:42 -0700
X-Trace: forums-1-dub 1316644842 10.22.241.152 (21 Sep 2011 15:40:42 -0700)
X-Original-Trace: 21 Sep 2011 15:40:42 -0700, vip152.sybase.com
Lines: 61
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.rep-server:9068
Article PK: 870232

I'm not aware of any issues with upgrading a RDS from 15.0.3 to 15.5. [NOTE: I haven't done a lot of 15.0.3-to-15.5
upgrades in a replicated environment, but I'm sure I've never run into problems with replicating to a RDS with a higher
version number than the PDS.]

Obviously (?) the 15.5 dataserver should be backwards compatible with anything the 15.0.3 dataserver can send through
the replication system, so there shouldn't be any issues.

---------

I'm assuming that you're upgrading with the same dataserver page size? (otherwise the dump-n-load won't work ... "Duh,
Mark!" ?)

And if jumping between little/big endian platforms you're aware of the cross platform dump-n-load issues? For a cross
platform dump-n-load scenario I might want to run some tests in a dev/test environment to make sure you don't run into
any issues with the replication of binary data into the RDS, eg, blobs, varbinary() strings, encrypted columns
(replicated as varbinary), etc).

On 09/21/2011 15:22, Isabella wrote:
> Hi Mark,
> Thank you for feedback, yes the stable rep queues is a decent size around 40GB ,my concerns is this the new RDB host is
> a newer version of ASE than old_RDB , so any issues for Rep here?
> I have done the switch over from primary to standby server in the past without to many issues .
> Isabella
> ,
>
> Mark A. Parsons wrote:
>> Obviously (?) the whole suspend-DSI-dump-oldRDB-load-into-newRDB-resume-DSI operation assumes that your RS has a large
>> enough stable device to hold any backlog of transactions that will pile up while the DSI is down.
>>
>>
>>
>> On 09/21/2011 14:17, Mark A. Parsons wrote:
>>> You'll want to take a look at the manuals on the steps for resyncing the RDB ... as that is, in essence, what you've
>>> suggested (ie, dump PDB, load dump into RDB). One of the issues you'd have to address is any inflight transactions
>>> between the PDB and RDB which end up getting applied to the RDB after it's been loaded from the PDB dump (eg, you could
>>> end up with duplicate data and/or other issues related to applying a transaction twice to a database) - the instructions
>>> on resyncing the RDB addresses this issue.
>>>
>>> I'm thinking the easier solution would be to suspend the DSI into the oldRDB, dump the oldRDB, load the oldRDB dump into
>>> the newRDB, shutdown the oldRDS (to make sure the DSI goes down if the hardware switch leaves the RS pointing at the
>>> oldRDB), make sure the network addressing for the newRDS is the same as the oldRDS, then resume the DSI. At this point
>>> the RS should think it's connecting to the same exact RDB. (You could also use a new network address (ip and/or port#)
>>> for the newRDS ... you'd just need to update the RS's interfaces file so that when it resumes the DSI it picks up the
>>> new/correct address from the interfaces file.)
>>>
>>> Later, when you want to to switch over the new standby host to serve as your primary host ... sounds like a 'normal' WS
>>> switch operation (see the 'switch active' command). If you haven't done a WS switch before I'd suggest running a few
>>> tests in a dev/test environment to insure you understand all the steps necessary to perform a WS switch.
>>>
>>> On 09/21/2011 13:01, Isabella wrote:
>>>> Hi All,
>>>> we have a ws standby system with Rep server( ASE 15.03, Rep 15.2), we plan to replace the standby server host with a
>>>> new
>>>> host with upgraded hardware and version of ASE 15.5 latest one. I plan to create a db copy( dump/load) of primary and
>>>> shutdown the existing standby and bring the new new host standby online with same ip and ASE 's names as old standby,
>>>> would this work with no issues for Rep server?
>>>> Later one after draining the rep stable queues, we switch over and have the new_host standby as our main primary active
>>>> ASE, are there any concerns I should be aware ?
>>>> Thank you
>>>> Isabella