Hi all,
I'm upgrading a ASE 12.5.0.3 to 12.5.4.
I upgraded the test environment sucessfully and now it's time to
upgrade the production which have a
replication server.
First of all, I'm not sure about the replication data, because I
don't have access to it.. ( yeah you know... IT stuff ),
but I'm supposed to test the upgrade and give some support.
There are some tips and precautions in this special situation?

ASE 12.5.0.3 -> 12.5.4
Solaris 8

Thanks!
Guto.

On Apr 15, 6:10*pm, Guto <gutom... (AT) gmail (DOT) com> wrote:
Few things you might want to check before you start upgrading your
system
What is your plan for upgradation ? dump and load ?

(1) Replication sever is quieseced
(2) Insert a row to a dummy table and verify if row gets replicated
successfully to replicate site
(3) if you are going to load primary database make sure your genid for
the database is higher than replicate one

-HTH
Manish Negandhi
[TeamSybase]

On Apr 16, 2:58*am, Manish Negandhi <negandhi.man... (AT) gmail (DOT) com> wrote:
Thanks Manish!
The upgrade process will be actually a binary installation over the
old version,
and the database upgrade itself is made when the we bring the server
on line.
Those are some steps I got from a very experienced Sybase DBA, and
I'll follow it,
If you or anybody else have any concerns about it, please advise me:

ALL THE STEPS MUST BE IN THE PRIMARY SERVER:

1)Turn off replication during the upgrade

2)In each replicated database ( nobody using it and empty queues ):
To check this status ( no users and empty queues ):
3) admin quiesce_check
go
the response must be quiesced

4) on each replicated database:
dbcc settrunc(ltm, ignore)
go
5) clean the log:
dump tran <db> with truncate_only
go

6)UPGRADE procedure on both servers, bring both instances on line

7)go to the replication catalog (RSSD)
run:
rs_zeroltm <PRIMARY_SERVER>,<DB PRIMARY_SERVER>
go

8) on each replicated database:
run dbcc settrunc(ltm, valid)
go

9) ativate the replicator agents

On Apr 16, 7:26*pm, Guto <gutom... (AT) gmail (DOT) com> wrote:
I dont see anything wong in the given steps. If you have more than one
repserver in your environment , its better to be extra careful in
terms of checking if each repserver is in quiesced state. Sometimes it
might be possible that transaction is sitting at replicate repserver
outbound queue but primary repserver is quiesced. Upgradation is also
possible without actually *disabling* replication but nothing wrong in
disabling. I would also perfom a dummy transaction manually in
replication environment exactly before starting upgrade and finishing
to make sure my replication environment is all set !

-HTH
Manish Negandhi
[TeamSybase]