Skip to Content
avatar image
Former Member

Best Practices for Migrating Sybase ASE 15.5 from SUN Solaris to RH6

I am currently running: "Adaptive Server Enterprise/15.5/EBF 18657 SMP ESD#4/P/Sun_svr4/OS 5.8/asear155/2545/64-bit/FBO/Thu Jun 16 10:29:40 2011" with following databases sizes:

267,000.0 MB

122,000.0 MB

  78,500.0 MB

and, of course, many more much smaller in size. I am looking for the best practices, detail steps (and gotchas) of moving these databases from Sybase ASE 15.5 on SUN Solaris to ASE 15.7 on Linux (RH6 64-bit).  I used the cross-platform dump-n-load many years ago to migrate from the same databases from Windows to SUN, and now need to move to company's enterprise platform.  I will be working on testing the process and procedures in test environment starting next week.

By-the-way, what EBF/ESD/SP level should I install?

Thanks for insight and direction.

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Jan 07, 2015 at 12:55 PM

    Joe,

    Read about:

    sp_dumpoptimize "archive_space = maximum"

    and

    http://scn.sap.com/thread/3400442...

    I started to use the dumpoptimize option so that all of the pages would exist in the dump image.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Jens Gleichmann

      Jen:  thanks so much for the heads up on the hugepages -- i use them on our Oracle installs, but had not considered the use of them on this migration -- so, will enable their usage based upon the blog you provided.  I had already perused the other blog regarding the migration.

      this migration for OLTP databases.

      thanks again,

      joe

  • Jan 08, 2015 at 12:17 AM

    Are you changing the dataserver page size, character set and/or sort order?

    If you're keeping everything the same then a cross platform dump-n-load (XPDL) will likely be the easiest.  Just make sure you've properly quiesced the source database before performing the dump. [ASE 15.5, System Admin Guide, Volume 2,  Chapter 11-Developing a  Backup and Recover Plan, Section-Using the dump and load commands, SubSection-Dumping and loading databases across platforms] "Duh, Mark!" ?

    If you're changing dataserver page size then obviously you'll need to use bcp and/or sybmigrate. [It's been my experience that some custom scripting will perform much better than sybmigrate, ymmv.]

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

    What kind of a window do you have in which to perform the switchover?

    If working with a (somewhat) small time window, and you have Repserver, then setting up either a WS or MSA from Solaris/SPARC to RH should help reduce the window in which to perform the switchover.

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

    If I remember correctly ASE 15.5+ uses a machine-independent method for storing passwords in syslogins, so you should be able to bcp those records across to the new ASE.

    Obviously you'll need to decide on what other system tables to migrate (eg, sysloginroles, syssrvroles, etc).

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

    As for which version of ASE to use ...

    The easiest method would be to limit the number of things you're changing, ie, stick with the ASE version you've got ... assuming you can dig up a copy of the same ESD for ASE 15.5 on linux.

    Unless of course you're a sadist and you really, Really, REALLY want to juggle a migration and upgrade at the same time, not to mention (possibly) complicating your test/verification process before letting the users/applications into the newly migrated/upgraded ASE-on-linux instance(s).

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member Former Member

      From the version string in the original post, it appears that the source is a Solaris/SPARC system.  But for the benefit of anyone not using SPARC, the Solaris to Linux migration from non-SPARC is not actually a cross-platform migration.

      I've done some testing from
      SunOS pedb 5.10 Generic_137112-03 i86pc i386 i86pc

      Adaptive Server Enterprise/15.0.2/EBF 15658 ESD#4/P/Solaris AMD64/OS 5.10/ase1502/2528/64-bit/FBO/Sat Apr  5 11:32:17 2008 

      to

      Linux pedb3 2.6.32-431.el6.x86_64 #1 SMP Sun Nov 10 22:19:54 EST 2013 x86_64 x86_64 x86_64 GNU/Linux

      Adaptive Server Enterprise/16.0 GA PL03/EBF 23024 SMP/P/x86_64/Enterprise Linux/ase160sp00pl02/3572/64-bit/FBO/Wed Aug 13 05:46:56 2014

      I had read all about the cross-platform issues involving Solaris to Linux migrations, and was surprised when sp_post_xpload told me that my data-base "is not a database that was loaded from a byte-swapped architecture".  Upon reflection, of course, I realized why (duh).  Nevertheless, I don't recall any of the documentation, blob posts, etc. discussing Solaris to Linux migration mentioning the significance of SPARC Solaris vs. non-SPARC Solaris.

      Andy