Document ID: 74486-01-1201-01
1. Accessing current release bulletin information
A more recent version of this release bulletin may be available on the World Wide Web. To check for critical product or document information added after the release of the product CD, use the Sybase Technical Library Product Manuals Web site.
To access release bulletins at the Technical Library Product Manuals Web site:
2. Product summary
Enterprise Connect Complete is the combination of Enterprise Connect Data Access and Enterprise Connect Data Movement on each platform. Since each of these Integrated Product Sets is discussed in detail in the following sections, Enterprise Connect Complete will not be discussed separately.
2.1 Version Contents
The following sections describe the contents of each Integrated Product Set, including current version numbers.
2.1.1 Enterprise Connect Data Access
2.1.2 Enterprise Connect Data Movement
3. Special installation instructions
This section describes special instructions for installing Enterprise Connect 12.1.
Read through this entire section before you begin installing any Enterprise Connect 12.1 components.
3.1 Instructions for Enterprise Connect
This section contains installation instructions for all Integrated Product Sets delivered as part of Enterprise Connect.
3.1.1 Products don’t appear in configuration utility after installation
If you have previously installed Sybase products and are now installing additional products in the same $SYBASE directory, the configuration utility may not show your new products as available for configuration. If this happens, click Cancel to exit the configuration utility, then follow the product documentation to configure each product without the use of the configuration utility.
3.1.2 Drivers fail during installation (NT and 2000)
On Microsoft Windows NT and Windows 2000, after client installation of DB2 Universal Database for Windows version 7.1, Open Client/Server and third-party ODBC drivers fail.
The problem is that the DB2 Universal Database installation sets an environment variable called LC_ALL. In the case of ODBC, the driver reads this variable and fails to connect. In the case of Open Client/Server, the isql session will fail to connect.
Workaround: Users must remove the LC_ALL environment variable to restore the environment. Removing this variable does not affect ODBC driver connectivity or isql connectivity.
3.1.3 License certification utility runs in GUI mode only
In non-GUI (Graphical User Interface) mode, you are not prompted to enter license certificate information.
During a command line installation, the license prompt asks whether you have already entered your license at a central server. The problem is that if you respond “no,” you get the default license provided on the installation CD.
In setting up a silent or command file installation, you can enter network license information at the end of the command file. The problem is that you must have already entered the license keys somewhere else.
Workaround 1: After a command line installation, and before or after a command file installation, you can run the License Manager utility.
This utility starts the Studio Installer GUI in license mode.
Workaround 2: Manually execute the SySAM daemons.
To start SySAM and the SySAM daemons from Windows:
To stop the SySAM daemons from Windows:
To start SySAM and the SySAM daemons from UNIX:
To stop the SySAM daemon from UNIX:
3.1.4 “Missing font” error messages (Solaris 2.6)
In jre1.2/lib/font.properties the default font, fontset.default, is set to Monotype Arial. Monotype Arial is not part of a standard Solaris 2.6 installation but is part of the optional font set. If Monotype Arial is not installed before you start a Java application, you will receive a large number of error messages regarding missing fonts. In addition, the Java application will not be able to display some text. This problem occurs because the application cannot explicitly set a particular font that is available on the system.
Workaround: Install the optional font set from the package, SUNWi1of.
3.1.5 ESD#1 incorporated in ASE 12.0
In the release bulletin for ASE, sections 9.2, 9.3, and 9.4 refer to downloading ESD#1 to correct some known problems. The fixes contained in the ESD#1 are incorporated in the version of ASE delivered with Enterprise Connect 12.x.
For more information on the specific problems corrected in the ASE 12.0 ESD#1, see “6.1.1 Problems corrected by ESD#1 incorporated in ASE 12.0”.
3.1.6 ESD#3 incorporated in Enterprise Connect 12.1
ESD#3 is incorporated in Enterprise Connect 12.1 and corrects some known problems. For information about what problems are resolved in this version, see the documentation accompanying ASE 12.00.03 on the World Wide Web.
3.1.7 Studio Installer will not run when environment variables change (UNIX)
On UNIX platforms, the Studio Installer will not run after environment variables are changed by the Sybase environment variables shell script (SYBASE.csh or SYBASE.sh). The shell script resides in the $SYBASE directory after an initial install.
If you need to run the Studio Installer after environment variables are changed by the SYBASE.csh or SYBASE.sh script (or changed as specified in that script), open a new window that does not use that environment.
The uninstall program will run normally even after environment variables are changed by the SYBASE.csh or SYBASE.sh environment variables shell script.
3.1.8 Null pointer exception when exiting Studio Installer
Under some circumstances, a null pointer exception might be displayed when the installer is exiting. The message will include the string “invalid peer.” This problem will be fixed in a future release and should not affect the current installation of any product.
3.1.9 Uninstalling Sybase software
In the Installation Guide of some Enterprise Connect Integrated Product Set 12.1 components, including ASE 12.0, the uninstall function of the Studio Installer is not documented correctly. This section describes the uninstall procedure.
Before uninstalling Sybase software, shut down all Sybase applications and processes that will be affected by the uninstall procedure.
The uninstall procedure does not uninstall Sybase directories created by the user. You should remove these directories before executing the uninstall procedure.
To start the uninstall procedure from Windows:
You can also execute the uninstall batch file uninstall.bat directly from a DOS window:
You must be in the %SYBASE% directory when you invoke the uninstall batch file.
To start the uninstall procedure from UNIX:
To uninstall the Sybase software:
Windows NT does not delete open files or files currently in use.
3.2 Instructions for Enterprise Connect Data Access
This section contains installation instructions that are unique to Enterprise Connect Data Access.
If you have an existing installation of DirectConnect 12.0 or greater, do not install Enterprise Connect Data Access. Enterprise Connect Data Access contains DirectConnect 12.0. For information about the current version of DirectConnect, see the documentation accompanying DirectConnect for DRDA version 12.00.03 or later. Check the World Wide Web for availability.
3.2.1 New installation for DirectConnect 12.0
The installation for DirectConnect 12.0 has changed completely from the 11.7 version. You must follow the installation steps in the Installation Guide for DirectConnect to install DirectConnect 12.0.
3.2.2 Error messages during installation (Windows NT)
If you receive the message, “The current user doesn’t have administrator privileges...”
If you do not log in as “system administrator” before running Studio Installer, the message, “The current user doesn’t have administrator privileges, log in as administrator and continue installation,” appears followed by a Yes and No button. This message appears if you use any user ID other than “system administrator,” even when that user ID has administrator privileges. Dismiss this message and proceed with installation by choosing Yes.
If you are prompted to replace the existing msvcrt.dll file
During the Studio Installer installation process, you might receive a message asking if you want to replace the existing msvcrt.dll file. Select the most recent file by choosing Yes or No, depending on the dates.
3.3 Instructions for Enterprise Connect Data Movement
This section contains the installation instructions that are unique to Enterprise Connect Data Movement.
3.3.1 Uninstall on Solaris requires a local display
On Solaris, to uninstall Enterprise Connect Data Movement software, you must use a local disk and a local display.
3.4 Instructions for Enterprise Connect Complete
This section contains installation instructions unique to Enterprise Connect Complete.
If you have an existing installation of DirectConnect 12.0 or greater, do not install Enterprise Connect Complete. Enterprise Connect Complete contains DirectConnect 12.0. For information about the current version of DirectConnect, see the documentation accompanying DirectConnect for DRDA version 12.00.03 or later. Check the World Wide Web for availability.
3.4.1 Installing ASE with Enterprise Connect Complete Integrated Product Set
To ensure that the ASE 12.0 license management feature works properly, Sybase recommends that you install only one copy of the ASE software. A single copy of ASE can be used for both functions described above.
4. Changed functionality in this version
Enterprise Connect 12.1 functionality changes are described in the following sections. For more details about new features see the release bulletins for the specific components of Enterprise Connect.
4.1 Support for DB2 Universal Database for UNIX and Windows
Enterprise Connect Data Movement now supports replication from DB2 Universal Database for UNIX and Windows NT. For more information about specific components and their support of DB2 Universal Database, see the release bulletins for those components.
An enhancement to DirectConnect for DRDA that includes access to DB2 Universal Database for Windows and UNIX platforms will be available in DirectConnect for DRDA version 12.00.03 or later. Check the World Wide Web for availability.
4.2 Support for Informix 9
Enterprise Connect Data Movement now supports replication from Informix Version 9.0. For more information about this new functionality, see the release bulletin for Sybase Replication Agent 12.1.
4.3 Support for Microsoft SQL Server 2000
Enterprise Connect Data Movement now supports replication from Microsoft SQL Server 2000. For more information about this new functionality, see the release bulletin for Sybase Replication Agent 12.1.
5. Product compatibilities
If you have previously installed Sybase products using the configuration utility, you may not see a product you’ve just installed on your list of products to configure. If this happens, click Cancel to exit the configuration utility. Restart the configuration utility and continue with configuration.
6. Documentation updates and clarifications
This section describes documentation updates and clarifications that apply to the manuals and online documentation for the Enterprise Connect 12.1 components.
6.1 Enterprise Connect
This section describes documentation updates and clarifications that apply to all Enterprise Connect Integrated Product Sets.
6.1.1 Problems corrected by ESD#1 incorporated in ASE 12.0
In the release bulletin for ASE, sections 9.2, 9.3, and 9.4 refer to downloading ESD#1 to correct some known problems. The fixes contained in the ESD#1 are incorporated in the version of ASE delivered with Enterprise Connect Data Movement Integrated Product Set 12.x.
6.1.2 Studio Installer uninstall feature
In the Adaptive Server Enterprise Installation Guide, the uninstall function of the Studio Installer is documented as not working. This problem is corrected in the Studio Installer distributed with Enterprise Connect Integrated Product Sets version 12.x. For more information about the uninstall procedure, see “3.1.9 Uninstalling Sybase software”.
6.2 Enterprise Connect Data Movement
This section describes documentation updates and clarifications that uniquely apply to Enterprise Connect Data Movement.
6.2.1 Path to rsmgen program
In Chapter 6, the Replication Server Configuration Guide for UNIX Platforms lists the path to the rsmgen executable incorrectly. It states: To use rsmgen to create a RUN file, enter:
The rsmgen executable actually resides in the install directory, and the config directory is not in the install directory.
To use rsmgen to create a RUN file, enter the following command instead of the command shown in the Replication Server Configuration Guide for UNIX Platforms:
6.2.2 Upgrading RSM to version 12.x
In Chapter 6, the Replication Server Configuration Guide, instructions are incomplete for upgrading earlier versions of Replication Server Manager (RSM) to version 12.x.
Use the procedures in the following sections to upgrade RSM Server version 11.x to version 12.x.
To upgrade RSM to version 12.x on UNIX platforms
To upgrade RSM to version 12.x on Windows NT platforms
7. Technical support
Each Sybase installation that has purchased a support contract has one or more designated people who are authorized to contact Sybase Technical Support. If you have any questions about this installation or if you need assistance during the installation process, ask the designated person to contact Sybase Technical Support or the Sybase subsidiary in your area.
8. Other sources of information
8.1 Sybase certifications on the Web
Technical documentation at the Sybase Web site is updated frequently.
For the latest information on product certifications
For the latest information on EBFs and Updates
To create a personalized view of the Sybase Web site (including support pages)
Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.