Results 1 to 2 of 2
  1. #1
    Join Date
    Dec 2014

    Unanswered: Migration from AES 11.9.2to 16.0

    Hi all,
    I'm at a customer site running Sybase ASE 11.9.2 on Windows 2000. I wish to migrate their set of databases to ASE 15.7 or 16.0 hosted on Server 2012 (for obvious reasons)
    I've downloaded and installed ASE 16.0 developer edition on a new Windows 2012 virtual server and and am moving to the database migration stage....
    From what I have read, a single step migration from 11.9.2 to 15.7 is possible, thus I assume a migration to 16.0 might also be possible.
    What I have done:
    i) Dumped the existing database and transaction logs from ASE 11.9.2 to some files on disk.
    ii) Created a datastore for data and logs and created a database with 'load on' the ASE 16.0 environment
    iii) loaded a 11.9.2 database and transaction logs into the blank database on ASE 16.0 environment (successful)
    iv) run an 'online database DBNAME' (failing)
    From what I have read, schema conversion etc. occurs during the online database action, not the initial load. This is the error i'm getting:

    1> online database Cust201213
    2> go
    Started estimating recovery log boundaries for database 'Cust201213'.
    Database 'Cust201213', checkpoint=(677861, 3), first=(677861, 3), last=(677861, 3).
    Completed estimating recovery log boundaries for database 'Cust201213'.
    Started ANALYSIS pass for database 'Cust201213'.
    Completed ANALYSIS pass for database 'Cust201213'.
    Recovery of database 'Cust201213' will undo incomplete nested top actions.
    Database 'Cust201213' appears to be at an older version '12.5' than the present installation at version '16.0'; ASE will assess it, and upgrade it as required.
    Database 'Cust201213': beginning upgrade step [ID 2]: validate basic system type data
    Database 'Cust201213': beginning upgrade step [ID 3]: alter table (table sysindexes)
    (182 rows affected)
    Msg 644, Level 21, State 5:
    Server 'SYBASE', Line 1:
    Index row entry for data row id (232233, 0) is missing from index page 232225 of index id 2 of table 'sysindexes' in database 'Cust201213'. Xactid is (677873,8). Drop and re-create the i
    Msg 3469, Level 20, State 1:
    Server 'SYBASE', Line 1:
    Database 'Cust201213': upgrade failed to create index 2 on table 'csysindexes'. Please refer to previous error messages to determine the problem. Fix the problem, then try again.
    Msg 3461, Level 20, State 1:
    Server 'SYBASE', Line 1:
    Database 'Cust201213': upgrade could not install required upgrade item '3'. Please refer to previous error messages to determine the problem. Fix the problem, then try again.
    Msg 3452, Level 20, State 1:
    Server 'SYBASE', Line 1:
    Database 'Cust201213': upgrade item 1134 depends on item 3, which could not be installed. Please refer to previous messages for the cause of the failure, correct the problem and try agai
    Msg 3451, Level 20, State 1:
    Server 'SYBASE', Line 1:
    Database 'Cust201213': upgrade has failed for this database. Please refer to previous messages for the cause of the failure, correct the problem and try again.
    Msg 3454, Level 20, State 1:
    Server 'SYBASE', Line 1:
    Database 'Cust201213': ASE could not completely upgrade this database; upgrade item 1134 could not be installed.
    ASE could not bring database 'Cust201213' online.

    As the database is not online of ASE 16.0 i've been unable to conduct must troubleshooting on that version, so I have clones a copy of the database on the 11.9.2 instance instead to work on.
    From the error I assume that the sysindexes system table is corrupt. I've read various forum entries that talk about running a dbcc reindex etc. however the Sybase knowledge base states that such a command cannot be run on the sysindexes table.
    Can anyone give me some advice on rebuilding a corrupt sysindexes table please. Go easy on me; I've only been exposed to Sybase ASE for 2 days so i'm learning.....
    Mike Squirrell
    Last edited by mikesqui; 12-18-14 at 04:19.

  2. #2
    Join Date
    Jun 2009
    Hi Mike,
    Plz check the below steps. These steps could help you

    To ensure a successful upgrade, review and perform the preupgrade tasks as necessary. Depending on the old server configuration, you may not need to perform all preupgrade tasks.

    If you are upgrading Adaptive Server:
    •The upgrade process modifies the sysaudits tables in the sybsecurity database. Sybase recommends that you archive any auditing data and truncate these tables before you upgrade. This reduces the chances of a failed upgrade due to lack of space in the sybsecurity database.
    •Stored procedure text in the syscomments table is required for upgrade.
    •To a private installation, see Upgrading to a Private Installation.

    1.Shut down the clusters that use an earlier version of the Cluster Edition.
    2.Install the Cluster Edition onto your system in a new location.
    3.Check system and upgrade requirements.
    4.Verify the name and location of the runserver file, as well as that you renamed it to RUN_servername, where servername is the name of the old server, as it appears in the interfaces file.
    The default RUN_servername file for a server SYBASE is called RUN_SYBASE. If the RUN_servername file for your current server is named differently, use the actual name of your server during the upgrade process.

    5.While the upgrade process for Adaptive Server requires that the previously installed version of the server is running, the upgrade process for Backup Server, Historical Server, and XP Server, requires those servers to be shut down.
    6.Verify that the text of all stored procedures you upgrade is available in syscomments by either:◦Reinstalling the procedures with text, or,
    ◦Removing and reinstalling the procedures after the upgrade.

    This step can allow you to inspect the stored procedures for any hidden or unwanted text.

    7.Make sure reserved words use quoted identifiers.
    8.Verify that users are logged off.
    9.Use dbcc to check for database integrity.
    10.Back up databases.
    11.Dump the transaction log.
    12.Verify that master is the default database for the "sa" user.
    13.Prepare the database and devices for upgrade using the preupgrade utility:a.Create a sybsystemdb database if it does not already exist.
    b.Disable auditing by running sp_configure 'auditing', 0.
    c.Disable Job Scheduler.
    d.Obtain the current audit settings for the pre-15.7 Adaptive Server using sp_displayaudit; you use this saved information to reenable auditing after you complete the installation. See Reenabling Auditing.
    e.Disable disk mirroring.

    Note: Cluster Edition version 15.7 does not support disk mirroring.

    f.Verify that your SYBASE environment variable points to the location of the new server software files you just installed.

    Fix any problems that preupgrade utility reports.
    You can safely ignore any warnings Adaptive Server issues about configuration parameters not being set to the default, as these are only for your information.

    14.If you are upgrading from a nonclustered 12.5.4, 15.0.2, or 15.5 server, and archive database access has been applied in the lower version server, disable the related functionality before upgrade.
    15. If you are upgrading from a 12.5.3 installation with cache bindings on sybsystemdb, drop the cache bindings for sybsystemdb that are bound to user-defined caches before running preupgrade.

    If you do not do this, you see this error: Current process... infected with 11 If you do receive this error, re-run preupgrade after you have dropped the cache bindings.
    16.Ensure that the procedure cache size is at least 150 percent of the default procedure cache size, or between 53,248 and 2,147,483,647 2K pages.
    17.Copy these files from earlier versions of the server to their corresponding Adaptive Server 15.x installation locations:
    ◦$SYBASE/$SYBASE_ASE/servername.cfg– where servername is your server name.

    18.If you have enabled the Java in the database feature, create the sybpcidb database and disable the feature during the installation.
    19.Set the OLDSYBASE_ASE variable to the SYBASE_ASE appropriate to your older server. If you are upgrading from 12.5 for example, it should be ASE-12_5.
    20.When you upgrade a server to the Cluster Edition, index and table-level statistics become inaccurate, and must be updated. Execute update index statistics on these tables:

    Upgrade System Table and Stored Procedure
    When you upgrade Adaptive Server, drop and re-create syscomments to include the new and changed tables.
    The runserver File Location
    Be sure the runserver file for your current server is located in $SYBASE/$SYBASE_ASE/install/RUN_servername.
    Reserved Words
    Reserved words are pieces of SQL syntax that have special meaning when used as part of a command.
    Upgrading to a Private Installation
    Upgrade from a shared installation to a private installation.
    The sybprocsdev device
    Sybase system procedures are stored in the sybsystemprocs database, which is stored in the sysprocsdev device. You may need to increase the size of sysprocsdev before upgrading Adaptive Server.

    For more info please refer:

Tags for this Thread

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts