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.

ASE migration from 12.5 to 15.7

2 posts in General Discussion Last posting was on 2013-01-29 23:50:02.0Z
RGS Posted on 2013-01-29 20:19:29.0Z
Sender: 23a7.5107f52d.1804289383@sybase.com
From: RGS
Newsgroups: sybase.public.ase.general
Subject: ASE migration from 12.5 to 15.7
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <51082ed1.37ed.1681692777@sybase.com>
NNTP-Posting-Host: 172.20.134.41
X-Original-NNTP-Posting-Host: 172.20.134.41
Date: 29 Jan 2013 12:19:29 -0800
X-Trace: forums-1-dub 1359490769 172.20.134.41 (29 Jan 2013 12:19:29 -0800)
X-Original-Trace: 29 Jan 2013 12:19:29 -0800, 172.20.134.41
Lines: 25
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31683
Article PK: 1307352

Hi!

We are plannig to migrate ASE from 12.5 version to 15.7

Our system is very big, we have 3,000 tables. 1,000 of these
are partitioned

We are worried about the time that will take the next tasks
after migration:

1) Partitionnig 1,000 tables
2) Distribute data of partioned tables in its partitions


We ony have a weekend (48 hours) for all migrate tasks,
including both tasks of partitions

What happens if the time needed for partitions tasks is very
high? Which alternatives would we have to migrate in a
weekend?

(Assume that we need the tables partitioned, because
performance)

Thanks!


"Mark A. Parsons" <iron_horse Posted on 2013-01-29 23:50:02.0Z
From: "Mark A. Parsons" <iron_horse@no_spamola.compuserve.com>
User-Agent: Mozilla/5.0 (Windows; U; Windows NT 6.1; en-US; rv:1.9.2.13) Gecko/20101207 Lightning/1.0b2 Thunderbird/3.1.7
MIME-Version: 1.0
Newsgroups: sybase.public.ase.general
Subject: Re: ASE migration from 12.5 to 15.7
References: <51082ed1.37ed.1681692777@sybase.com>
In-Reply-To: <51082ed1.37ed.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
X-Antivirus: avast! (VPS 130112-1, 01/12/2013), Outbound message
X-Antivirus-Status: Clean
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <5108602a$1@forums-1-dub>
Date: 29 Jan 2013 15:50:02 -0800
X-Trace: forums-1-dub 1359503402 172.20.134.152 (29 Jan 2013 15:50:02 -0800)
X-Original-Trace: 29 Jan 2013 15:50:02 -0800, vip152.sybase.com
Lines: 55
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub sybase.public.ase.general:31684
Article PK: 1307355

While not necessarily *easy*, but most likely to require minimal downtime ...

- setup warm standby replication from 12.5 to 15.7, then sync 15.7 with a dump-n-load (or replicate to 12.5,
sync-via-dump-n-load, and then upgrade replicate to 15.7); if going between different endians then you'll need to incur
the extra overhead for post-cross-platform-load processing

- when it comes time to 'upgrade' you take a brief outage to shutdown applications, quiesce replication, run the
repserver 'switch active' command, and start up applications with sql.ini/interfaces pointing to the 15.7 dataserver

The nice thing about the above is that you can take all the time you want to get the 15.7 database(s) configured, and
tables repartitioned, before letting your users lose in the 15.7 dataserver. And when you do go to switch users to the
15.7 dataserver, the switch should take no more than a few minutes (if rehearsed), otherwise probably no more than an
hour or so.

Last time I checked the upgrade from 12.5 to 15.7 will cause all tables to be unpartitioned, after which it was
necessary to manually repartition the tables. So make sure all tables have been repartitioned before switching
application to run against the 15.7 dataserver.

Using the warm standby/switch active method (ie, maintaining replication from 15.7 to 12.5) means switching back to 12.5
(in case of show-stopper problems with 15.7) should be much easier. [This assumes that you won't be implementing any
15.x-specific features that can't replicate to a 12.5 dataserver **** I highly recommend not implementing any 15.7
features until you've successfully completed the switch if simply because switching back to 12.5 will be much easier.]

As always, and particularly in this situation, I'd recommend doing all of the above in a development and/or test
environment so you can work out any details.

I'm also assuming that you've done a good bit of work in the development/test environments to insure your code will run
properly/efficiently in 15.7. ("Duh, Mark!" ?)

On 01/29/2013 13:19, RGS wrote:
> Hi!
>
> We are plannig to migrate ASE from 12.5 version to 15.7
>
> Our system is very big, we have 3,000 tables. 1,000 of these
> are partitioned
>
> We are worried about the time that will take the next tasks
> after migration:
>
> 1) Partitionnig 1,000 tables
> 2) Distribute data of partioned tables in its partitions
>
>
> We ony have a weekend (48 hours) for all migrate tasks,
> including both tasks of partitions
>
> What happens if the time needed for partitions tasks is very
> high? Which alternatives would we have to migrate in a
> weekend?
>
> (Assume that we need the tables partitioned, because
> performance)
>
> Thanks!