Known Issues for the Replication Agent for Oracle Installer

The resource file cannot be used to create the pds_username.

When create_pds_username is set to yes in the resource file, the creation results to an error:

Apr 23, 2012 10:27:54 AM com.sybase.ra.admin.oracle.RAOAdmin verifyPDSConnections 
ERROR: Length of user ID <RA_USER_CREATED> exceeds the maximum 30 characters. Apr 23, 2012 10:27:54 AM 
com.sybase.ra.admin.oracle.RAOAdmin verifyPDSConnections ERROR: Length of password <[C@40f6a33b> exceeds
 the maximum 30 characters.

Workaround: Create the pds_username manually (outside of the instance creation).

Replication Agent installation on AIX platform fails.

When installing Replication Agent on AIX, only SySAM gets installed and Replication Agent components fail.

Workaround: Set the IATEMPDIR environment variable to a location that contains sufficient space and restart the Replication Agent installer.

The SySAM lmgrd daemon is not installed unless you provide a served license during installation.

Workaround:

To install a SySAM server during the installation of Replication Agent, specify a served license.

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

(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.

Licenses directory is not always created.

When you install Replication Agent using an unserved license, licenses, the default license directory, is not created. Because Replication Agent does not have access to the license file, it uses the grace license, which expires after 30 days.

Issues when installing using a served license.

When you install Replication Agent using a served license, SySAM Utilities is installed twice, and two copies of the Java Runtime Environment (JRE) are installed. These issues do not impact the Replication Agent and can be ignored.

Workaround: None.

Issues when reinstalling Replication Agent on IBM AIX.

Reinstalling Replication Agent on IBM AIX after you create, start, and stop a Replication Agent instance results in an error from the installation program. This error does not affect subsequent Replication Agent instances and can be ignored.

Workaround: None.

SySAM Server and SySAM Utilities installation information not displayed.

When you install Replication Agent with a served license, the SySAM Utilities and SySAM Server Install screen should display the installation progress of the SySAM components. However, when you install in console or GUI mode on a Windows XP or Windows 2003 machine, the SySAM Utilities and SySAM Server Install screen does not display the expected information.

Workaround: Wait for the Sybase Software Asset Management screen to appear and continue with your installation. The installation program has installed the SySAM components even if the progress bar had not been shown.

Available License Check window does not display correct database name.

When you enter an invalid license on the Sybase Software Asset Management License Panel and click Next, you will see this message in the Available License Check window:

Replication Agent for database_type, license not found

If you click Previous, change the database type, and click Next, the error message displays again if the license is still invalid. However, the message does not reflect the new database type.

Workaround: Ignore the message and ensure that you enter a valid license.

Cannot view text fields properly when using Hummingbird Exceed from a Windows workstation.

If you use Hummingbird Exceed from a Windows workstation to install Replication Agent on a UNIX host, you might not be able to view all of the text fields on the Sybase installer screens.

Workaround: Use a native X-Windows session to run the Sybase installation program, or run the Sybase installation program in console or silent mode. See the Replication Agent Installation Guide.

Installation program cannot create installation directory on Microsoft Windows 2008.

On Microsoft Windows 2008, the installation program can create the Replication Agent installation directory only when you are logged in as an administrator, even if your role has permission to create directories.

Workaround: Create the installation directory before running the installation program.

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.

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.

./setup.bin: !: not found message appears when installing Replication Agent on Solaris.

You see this error message when you install Replication Agent on Solaris:

Preparing to install...
./setup.bin: !: not found
Extracting the installation resources from the installer archive...
Configuring the installer for this system's environment...

Workaround: Ignore the message and continue.