Known Installation Issues for Adaptive Server Cluster Edition

Learn about known installer issues and workarounds. Known issues are listed in descending order of Change Request (CR) numbers.

CR #Description
739079
Update of Adaptive Server returns "Arithmetic overflow occurred" error for database size check.

If any system database is greater than 2GB, updating an Adaptive Server with the Adaptive Server installer, or updatease (on UNIX) or updatease.exe (on Windows) utility, will fail with the error "Arithmetic overflow occurred."

Workaround: To update an Adaptive Server, manually run the updatease utility, or for Windows the updatease.exe utility with the -k argument. The -k option tells the utility to skip the database size check.

The utilities are located here:

  • UNIX – $SYBASE/ASE-15_0/bin/updatease
  • Windows – %SYBASE%\ASE-15_0\bin\updatease.exe
736300
Replication Manager Plug-in (RMP) cannot be loaded after Adaptive Server is installed upon RMP

Installing Adaptive Server and Sybase Central into the same directory as Replication Server and Replication Manager Plug-in can cause the Replication Manager Plug-in to not load properly.

Workaround: Unset the SYBASE_JRE7 environment variable that is set in the SYBASE {csh | env | sh} file before starting Sybase Central.

Rather than unsetting the SYBASE_JRE7 environment variable in the SYBASE file by commenting out the line, unset it on the command line in the same window that is used to start Sybase Central. This prevents other processes from being affected. Regardless of platform, do the following:
  1. Open a new window.
  2. Source the SYBASE file.
  3. Unset the SYBASE_JRE7 environment variable. See commands below.
  4. Execute the runSybaseCentral script.
  • for C-Shell (SYBASE.csh):

    unsetenv SYBASE_JRE7

  • for Bourne Shell (SYBASE.sh):

    SYBASE_JRE7=export SYBASE_JRE7

  • for Bash(?) Shell (SYBASE.env):

    SYBASE_JRE7=

692496
Configuring tempdb device for HA

When installing an Adaptive Server to be used in an HA configuration, the sp_companion stored procedure configure command may fail due to duplicate device names for the tempdbdev logical device.

Workaround: Do not specify the "Tempdb Device" (set the value of this field to blank) when configuring the secondary server during ASE installation.

  • If additional tempdb space is required on either server, log in to this server after installation is complete and use the alter database command to increase the size of tempdb.
  • If additional disk space is required to allocate the tempdb database, use the disk init command to create a new database device for tempdb.
  • If a new device is created, the logical device name should be unique between the two servers.
688101
Cannot start Sybase Central for Sybase IQ 15.4 after uninstalling Adaptive Server 15.7.

If you install Adaptive Server Enterprise 15.7 and Sybase IQ 15.4 in the same directory, then uninstall Adaptive Server, you cannot then start Sybase Central for IQ. This problem occurs because shared files are removed by the Adaptive Server uninstaller.

Workaround: If the version of Sybase Central installed with IQ 15.4 cannot be started after you uninstall Adaptive Server 15.7:

  1. Re-create the $SYBASE/shared/JavaHelp-2_0 if necessary.
  2. Copy $SYBASE/IQ-15_4/java/jh.jar to the $SYBASE/shared/JavaHelp-2_0 directory.
  3. Reload or register the IQ plug-in in Sybase Central.
678912
Cannot use DBISQL from Sybase Central after installing RMP on top of Adaptive Server 15.7.

Workaround: To enable DBISQL to launch, add the following into scjview.sh java arguments.

-Disql.repositoryDirectory="$SYBROOT/DBISQL/bin"

   
671351
Installing Adaptive Server 15.7 on top of Replication Agent™ 15.2 causes SySAM errors.

Workaround: Before installing Adaptive Server 15.7, modify the SySAM file permissions to include write permissions.

639623

Cannot Start Adaptive Server Interactive SQL from Sybase Central.

If you install Replication Manager into the same directory as Adaptive Server, the Interactive SQL cannot start from Sybase Central, and issues: Interactive SQL could not load the "SQL Anywhare plugin", its "saip11.jar" file has been removed or has been deleted. You will not be able to connect to the databases handled by that plugin.

Workaround:
  • Before installing Replication Manager, rename shared/sybcentral600/scjview.sh toshared/sybcentral600/scjview.sh.save.
  • After installing Replication Manager, rename shared/sybcentral600/scjview.sh.save back toshared/sybcentral600/scjview.sh.
.
589483
If the df command stops responding, the installation stops responding before the pre-installation summary pane appears.
Workaround:
  1. Identify the network file system (NFS) mounts that may have problems:

    strace -e statfs, statfs64 df

  2. Use the umount command to unmount an identified NFS mount:

    umount -l <path>

  3. Repeat the above steps until there are no more NFS mounts that have stopped responding.

The umount command requires root permission.

If umount command failed to unmount the offending NFS, you may need to fix the problem at the source or restart the machine.

588793
Installing Adaptive Server 15.5 and later versions that use Install Anywhere on older directories that have been installed with InstallShield Multiplatform can lead to incompatibility issues.
These issues occur while using products installed with different installer technologies:
  • If you install products using Install Anywhere or InstallShield Multiplatform on top of a product installed using the other installer, the same files included in both installers are silently overwritten by the later installation.
  • If you run either the Install Anywhere or InstallShield Multiplatform uninstaller, the same files installed by both installers are removed without any indicating messages.
Workaround: Do not install products that use Install Anywhere and products that use InstallShield Multiplatform in the same directory.
583979
The installer does not validate feature names specified in the response file when you install in silent mode.

Workaround: Ensure that the specified feature names are correct.