Database Upgrades

Important information about database upgrades.

For detailed information about installing and upgrading SAP Sybase IQ, see the Installation and Configuration Guide.
CR# Description
750748
  • Shut down all products that use $SYBASE before upgrade – The SYBASE variable identifies the location of the common parent directory shared by SAP Sybase applications like SAP Adaptive Server Enterprise and Sybase Open Client.
    Failure to shut down all products that use $SYBASE may generate signal 11 (SIGSEGV) errors when you upgrade SAP Sybase IQ.
  • Workaround – Shut down all SAP Sybase applications, restart the SAP Sybase IQ server, and retry the upgrade.
702052
  • Drop all JOIN and all LD indexes. On multiplex, drop all logical servers named AUTO, COORDINATOR, ALL or DEFAULT – If you do not drop these objects and try to run an ALTER DATABASE UPGRADE in SAP Sybase IQ 16.0, the upgrade fails and the server returns a message that indicates that a database upgrade is not possible when these objects are in use.
  • Recovery Information – To recover from a failed upgrade, shut down the 16.0 server, open the database with SAP Sybase IQ 15.x, and drop all LD and all JOIN indexes as well as any named logical servers before proceeding with the migration.
675890
  • ALTER DATABASE UPGRADE Fails with the Error "Not allowed while 'DBA' is using the database" – Database upgrade procedures in the Installation and Configuration Guide instruct you to use several startup flags to start or restart a server. If SAP Control Center is running, or another process that automatically connects to SAP Sybase IQ, you must increase the number of connections using the -gm flag or the upgrade fails.

    In an environment where many processes automatically connect to SAP Sybase IQ, consider temporarily starting SAP Sybase IQ on a different port using the -x flag. This option prevents all existing processes from connecting to IQ since the port will be unknown to them. You can also use this method for any maintenance task that requires SAP Sybase IQ connectivity to be limited.

    For example, the SAP Sybase IQ upgrade procedure follows this sequence for a simplex server:
    1. Shut down the server, then restart with these startup flags:

      -gm 1 -iqro 1

    2. Run ALTER DATABASE UPGRADE.

      SAP Sybase IQ returns a Not allowed while 'DBA' is using the database error.

    Similarly, the IQ multiplex upgrade procedure follows this sequence:
    1. Shut down the multiplex, then restart the coordinator with these startup flags:

      -iqmpx_sn 1 -gm 1 -iqro 1

    2. Run ALTER DATABASE UPGRADE.

      IQ returns a Not allowed while 'DBA' is using the database error.

  • Workaround 1 – The -gm switch controls the number of connections when you start the server.
    1. Start the server with -gm 2 (which allows two connections), or drop the existing connection which is used by SCC when the server starts.
    2. Verify the number of connections using the sp_iqconnection command.
    3. If necessary, drop any connections used by SCC (or other processes) using the DROP CONNECTION <id_number> command.
  • Workaround 2 – Temporarily start IQ on a different port using the –x switch: The –x switch controls the port that IQ uses when you start the server.
    • On a simplex server, use the –x switch to specify a new port number:

      start_iq @yourserver.cfg yourdb.db -x 'tcpip{port=<new_port>}'

    • On a multiplex server, use both the –x switch and the iqmpx override switch to specify a new port number:

      start_iq @yourserver.cfg yourdb.db -iqmpx_ov 1 -x 'tcpip{port=<new_port>}'