Known Issues for the Replication Agent Installer

Learn about known issues and workarounds for the Replication Agent installer.

Replication Agent Installer Issues
CR# Description
625227

SPDC-generated served partition-level licenses may not work.

When you use a served partition-level license generated from the Sybase Product Download Center 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 default host ID obtained from the lmutil lmhostid utility for the license server. Do not use subcapacity host IDs obtained from the sysamcap utility.

594586

Inaccurate disk space information.

The installation program displays inaccurate disk space requirement.

Workaround:

Refer to the Replication Agent Installation Guide for the correct disk space requirement for your platform.

593410

Installation program cannot uncompress the Replication Agent archive.

On UNIX and Linux platforms, if you specify the tar utility from the GNU collection before the operating system-supplied tar utility in the $PATH environment variable, the GNU tar utility is invoked when you issue a tar command, and 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: In the $PATH environment variable, specify the operating system-supplied tar utility before the GNU tar utility.