Known Issues

The DA server license is not checked in after the JVM is terminated with Ctrl+C.

If the JVM for the DA server process fails or is terminated from the operating system, DA server cannot complete tasks it would normally perform before shutdown, such as checking in the license. DA server may also not check in the license if its JVM is terminated with Ctrl+C on a Windows machine.

Workaround: Stop DA server from isql with the Replication Server shutdown command.

Uninstallation issues occur when Replication Server DA Option is installed in the same directory as older Sybase products which used InstallShield.

If new Sybase products that use InstallAnywhere (like DA Option) are installed in the same directory as the older Sybase products which used InstalledShield, uninstalling one of the products may make the others unusable because some of the shared components are removed by the uninstaller.

For example, if DA is installed in the same directory as Replication Server 15.2 and Replication Manager (RM) plug-in 15.2, and the RM plug-in is uninstalled, the DA server cannot be started because the JRE on the /shared directory has been removed.

Starting DA server or agent on Windows 7 fails

DA server or agent can not start properly on Windows 7 if you run the RUN_instance_32.bat or RUN_instance_64.bat script using the Run option.

Workaround: Use the Run as Administrator option instead of the Run option when running the start-up scripts.

Sybase Central™ fails to start after installing Replication Manager plug-in 15.2 in the same directory as Replication Server DA Option

If you install Replication Manager plug-in in the same directory as DA Option and the machine has Microsoft Visual C++ 2005 Redistributable Package for DA Option, the value of JRE_DIRECTORY in the scjview.ini file is changed from %SYBASE%\Shared\JRE-6_0_6_32BIT to %SYBASE%\Shared\JRE-6_0_6_64BIT, which causes error when starting Sybase Central.

Workaround: Change the JRE_DIRECTORY value in the scjview.ini file to %SYBASE%\Shared\JRE-6_06_32BIT.

When you use a served partition-level license generated from the Sybase Product Download Center or the SAP® Service Marketplace (SMP) to start a SySAM server, you see a message that you are using an invalid license key, similar to:

(SYBASE) Invalid license key (inconsistent authentication code)
(SYBASE) License server system started on hpiabou
(SYBASE) No features to serve, exiting
(SYBASE) EXITING DUE TO SIGNAL 49 Exit reason 4
(lmgrd) SYBASE exited with status 49 (No features to serve)
(lmgrd) SYBASE daemon found no features.  Please correct
(lmgrd) license file and re-start daemons.
(lmgrd)
(lmgrd) This may be due to the fact that you are using
(lmgrd) a different license file from the one you expect.
(lmgrd) Check to make sure that:
(lmgrd) /remote/cat_fc/nli/iq152.hpia/SYSAM-2_0/licenses/18965_hpiabou_
(lmgrd) is the license file you want to use.

Workaround: Use the old host IDs for the license running on the license server.