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.

using alter replication definition on running environment

3 posts in replicator Last posting was on 2006-11-21 14:07:50.0Z
Roberto Lammoglia Posted on 2006-11-21 09:39:28.0Z
From: "Roberto Lammoglia" <NOSPAMrlamm@becromal.it>
Newsgroups: sybase.public.ase.replicator
Subject: using alter replication definition on running environment
Lines: 21
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
NNTP-Posting-Host: 213.255.6.161
X-Original-NNTP-Posting-Host: 213.255.6.161
Message-ID: <4562d760$1@forums-1-dub>
Date: 21 Nov 2006 02:39:28 -0700
X-Trace: forums-1-dub 1164105568 213.255.6.161 (21 Nov 2006 02:39:28 -0700)
X-Original-Trace: 21 Nov 2006 02:39:28 -0700, 213.255.6.161
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.replicator:160
Article PK: 103365

Dear all,
I need to modify some replication definition in two ASE tables changing to
replicate minimal column.

I cannot do this on "test environ".

Can I use command "alter replication definition....." directly on my running
environ without stop replication services ?
If no, what is mode to keep integrity of my data ?

VERSIONS ARE:
2 x Adaptive Server Enterprise/11.9.2.4/P/SWR 9690(Data General)
1 x Replication Server/11.5.1/P/SWR 9493(Data General)


TIA
Bob


"Mark A. Parsons" <iron_horse Posted on 2006-11-21 12:14:11.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.7.2) Gecko/20040804 Netscape/7.2 (ax)
X-Accept-Language: en-us, en
MIME-Version: 1.0
Newsgroups: sybase.public.ase.replicator
Subject: Re: using alter replication definition on running environment
References: <4562d760$1@forums-1-dub>
In-Reply-To: <4562d760$1@forums-1-dub>
Content-Type: text/plain; charset=us-ascii; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: adsl-66-142-154-18.dsl.hstntx.swbell.net
X-Original-NNTP-Posting-Host: adsl-66-142-154-18.dsl.hstntx.swbell.net
Message-ID: <4562fba3$1@forums-1-dub>
Date: 21 Nov 2006 05:14:11 -0700
X-Trace: forums-1-dub 1164114851 66.142.154.18 (21 Nov 2006 05:14:11 -0700)
X-Original-Trace: 21 Nov 2006 05:14:11 -0700, adsl-66-142-154-18.dsl.hstntx.swbell.net
Lines: 59
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.replicator:161
Article PK: 103366

1 - suspend repagent activity from the primary database (eg, sp_stop_rep_agent, shutdown LTM - if still using an LTM, suspend log transfer from primary database)

2 - quiesce (ie, flush) the replication system to insure all transactional activity has flown through to the replicate database(s)

3 - (optionally) suspend DSI connection

4 - alter repdef

5 - (if previously suspended) resume DSI connection

6 - resume log transfer from the primary database (eg, sp_start_rep_agent, start up LTM - if still using an LTM, resume log transfer from primary database)

--------------------------

If 'down time' (or latency build up) is an issue for you I'd recommend you perform the above steps during a lull in primary database activity ... and when replication queues are relatively small (ie, they can be quiesced/flushed quickly).

I'd also recommend having your repdef modifications already written down so that all you have to do is cut-n-paste into a command window (or submit as a script against the repserver).

--------------------------

If you're not sure about some of the above steps I'd really suggest you test it out on a development/test environment before touching your production system. The steps are pretty straight forward but it can't hurt to be 100% confident of your methodology *BEFORE* you go modifying production.

Worse case scenario ... setup a dummy database in your primary and replicate (production) dataservers ... get replication setup between the 2 dummy databases ... then perform the above steps on against your dummy databases.

NOTE: Step #2 (quiescing/flushing) replication system may not be doable if your 'real' production databases have constant activity. This is ok as long as you are sure replication has ceased for the dummy databases (eg, stop activity in the primary dummy db, insert a heartbeat record in a table, when heartbeat comes out other end you know replication has been flushed of all transactions for your dummy database).

The time it takesto setup a test replication environment will be time well spent ... especially when compared to the down time you may experience if you 'mess up' the production environment performing steps you're not familiar with.

--------------------------

I've seen manuals, documents, presentations and classroom notes that state all you have to do is 'stop transactional activity' in the primary database ... then wait for the replication system to clear itself ... then make your changes.

I've never seen a production environment where *ALL* primary database activity stops just because the DBA says 'stop for a few minutes' ... someone, or more likely some process, will always perform some transactional activity in the primary database at the most inopportune time.

Taking the time to insure no primary database activity makes it's way into the replication system (eg, stop repagent/LTM) is a relatively easy step and it removes the possibility of any errant activity in the primary database screwing up your modifications.

Roberto Lammoglia wrote:
> Dear all,
> I need to modify some replication definition in two ASE tables changing to
> replicate minimal column.
>
> I cannot do this on "test environ".
>
> Can I use command "alter replication definition....." directly on my running
> environ without stop replication services ?
> If no, what is mode to keep integrity of my data ?
>
> VERSIONS ARE:
> 2 x Adaptive Server Enterprise/11.9.2.4/P/SWR 9690(Data General)
> 1 x Replication Server/11.5.1/P/SWR 9493(Data General)
>
>
> TIA
> Bob
>
>
>
>


Roberto Lammoglia Posted on 2006-11-21 14:07:50.0Z
From: "Roberto Lammoglia" <NOSPAMrlamm@becromal.it>
Newsgroups: sybase.public.ase.replicator
References: <4562d760$1@forums-1-dub> <4562fba3$1@forums-1-dub>
Subject: Re: using alter replication definition on running environment
Lines: 100
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Response
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
NNTP-Posting-Host: 213.255.6.161
X-Original-NNTP-Posting-Host: 213.255.6.161
Message-ID: <45631646$1@forums-1-dub>
Date: 21 Nov 2006 07:07:50 -0700
X-Trace: forums-1-dub 1164121670 213.255.6.161 (21 Nov 2006 07:07:50 -0700)
X-Original-Trace: 21 Nov 2006 07:07:50 -0700, 213.255.6.161
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.replicator:162
Article PK: 103367

Mark, thank you very much for your cooperation.

Bob

"Mark A. Parsons" <iron_horse@no_spamola_compuserve.com> wrote in message
news:4562fba3$1@forums-1-dub...
>1 - suspend repagent activity from the primary database (eg,
>sp_stop_rep_agent, shutdown LTM - if still using an LTM, suspend log
>transfer from primary database)
>
> 2 - quiesce (ie, flush) the replication system to insure all transactional
> activity has flown through to the replicate database(s)
>
> 3 - (optionally) suspend DSI connection
>
> 4 - alter repdef
>
> 5 - (if previously suspended) resume DSI connection
>
> 6 - resume log transfer from the primary database (eg, sp_start_rep_agent,
> start up LTM - if still using an LTM, resume log transfer from primary
> database)
>
> --------------------------
>
> If 'down time' (or latency build up) is an issue for you I'd recommend you
> perform the above steps during a lull in primary database activity ... and
> when replication queues are relatively small (ie, they can be
> quiesced/flushed quickly).
>
> I'd also recommend having your repdef modifications already written down
> so that all you have to do is cut-n-paste into a command window (or submit
> as a script against the repserver).
>
> --------------------------
>
> If you're not sure about some of the above steps I'd really suggest you
> test it out on a development/test environment before touching your
> production system. The steps are pretty straight forward but it can't
> hurt to be 100% confident of your methodology *BEFORE* you go modifying
> production.
>
> Worse case scenario ... setup a dummy database in your primary and
> replicate (production) dataservers ... get replication setup between the 2
> dummy databases ... then perform the above steps on against your dummy
> databases.
>
> NOTE: Step #2 (quiescing/flushing) replication system may not be doable
> if your 'real' production databases have constant activity. This is ok as
> long as you are sure replication has ceased for the dummy databases (eg,
> stop activity in the primary dummy db, insert a heartbeat record in a
> table, when heartbeat comes out other end you know replication has been
> flushed of all transactions for your dummy database).
>
> The time it takesto setup a test replication environment will be time well
> spent ... especially when compared to the down time you may experience if
> you 'mess up' the production environment performing steps you're not
> familiar with.
>
> --------------------------
>
> I've seen manuals, documents, presentations and classroom notes that state
> all you have to do is 'stop transactional activity' in the primary
> database ... then wait for the replication system to clear itself ... then
> make your changes.
>
> I've never seen a production environment where *ALL* primary database
> activity stops just because the DBA says 'stop for a few minutes' ...
> someone, or more likely some process, will always perform some
> transactional activity in the primary database at the most inopportune
> time.
>
> Taking the time to insure no primary database activity makes it's way into
> the replication system (eg, stop repagent/LTM) is a relatively easy step
> and it removes the possibility of any errant activity in the primary
> database screwing up your modifications.
>
>
> Roberto Lammoglia wrote:
>> Dear all,
>> I need to modify some replication definition in two ASE tables changing
>> to replicate minimal column.
>>
>> I cannot do this on "test environ".
>>
>> Can I use command "alter replication definition....." directly on my
>> running environ without stop replication services ?
>> If no, what is mode to keep integrity of my data ?
>>
>> VERSIONS ARE:
>> 2 x Adaptive Server Enterprise/11.9.2.4/P/SWR 9690(Data General)
>> 1 x Replication Server/11.5.1/P/SWR 9493(Data General)
>>
>>
>> TIA
>> Bob
>>
>>
>>