Learn about known installer issues and workarounds. Known issues are listed in descending order of Change Request (CR) numbers.
CR # | Description |
---|---|
709431 |
SAMPLE_RS cannot be created after RS 15.7.1
installed upon ASE 15.7 ESD#2
When Adaptive Server 15.7 ESD #2 and Replication Server 15.7.1 are installed in the same directory, the creation of a sample Replication Server will fail. Workaround: Do not install Replication Server and Adaptive Server in the same directory. |
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.
|
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, and then uninstall Adaptive Server, you cannot then start Sybase Central for IQ. This problem occurs because shared files are removed by Adaptive Server uninstaller. Workaround: Use the following workaround if the version of Sybase Central installed with IQ 15.4 cannot be started after you uninstall Adaptive Server 15.7:
|
683486 |
Cannot use DBISQL from Sybase Central after
installing RMP 15.2 and RMP 15.7. 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" Note: In some cases single quotes are used to enclose the directory path.
Check the existing file to determine whether to use single or double quotes.
|
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' |
611780 |
Installing Adaptive Server 15.5 Cluster Edition in the same directory as ECDA
15.0 ESD #2 and earlier versions results in errors.
The Unified Agent does not start after this installation; and you cannot create a cluster from Sybase Central.
Workaround: Sybase strongly recommends that you install the Adaptive
Server Enterprise 15.5 Cluster Edition into its own directory. If you must
install Adaptive Server 15.5 Cluster Edition in the same directory as ECDA
15.0, then:
|
593410 |
Cannot run installer with non-default "tar" tool.
If the GNU tar utility is listed in the path before the
OS-supplied tar when you invoke the
tar command, the installer fails with this
error:
The included VM could not be unarchived (TAR). Please try to download the installer again and make sure that you download using 'binary' mode. Please do not attempt to install this currently downloaded copy. Workaround: Define /usr/bin/tar in $PATH. |
593148 |
Installation fails on Sun Solaris x86 and SPARC.
When the file descriptor limit is set to "unlimited," the installer fails
with this
message:
awk: insufficient memory for string storage Context is: >>> <<< Workaround: Set the file descriptor limit to a number. |
590282 |
You cannot use the tab and arrow keys to navigate the Choose Product
Features pane of the installation or uninstallation program.
Workaround: Use the mouse to click in the Install or Uninstall window. This sets the focus on the window and allows you to navigate using your keyboard. |
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:
|
586169 |
gzip must be installed on the machine for installer to succeed.
The installer reports:
gzip: Not Found Workaround: Install gzip on your machine and make sure it is included in the path. |
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. |