Release Bulletin Sybase® Replication Server® 15.0 for Sun Solaris
Document ID: DC71616-01-1500-03
Last revised: November 23, 2006
Accessing current release bulletin information
A more recent version of this release bulletin may be available on the Web. To check for critical product or document information added after the product release, use the Sybase Product Manuals Web site.Accessing release bulletins at the Sybase Product Manuals Web site
Enclosed is Replication Server® version 15.0, which is compatible with the following platform and operating system configurations:
If your operating system requires patches, install them before you install Replication Server components.
Contact your operating system provider for any patches recommended for your installation. Do not use a patch that is earlier than the version suggested for your operating system. Use the patch recommended by the operating system vendor, even if it supersedes the patch listed.
For details about the new features in Replication Server version 15.0, see What’s New in Replication Server Version 15.0?
Replication Manager, a plug-in to Sybase Central™, Java Edition, is a component in Replication Server 15.0. For details about the new features in Replication Manager 15.0, see What’s New in Replication Server Version 15.0?
Replication Monitoring Services
Replication Monitoring Services (RMS) is a new component in Replication Server 15.0. RMS is the new middle-management monitoring layer that replaces the existing Replication Server Manager and provides monitoring services for large and complex replication environments. For details about the new features in Replication Monitoring Services 15.0, see What’s New in Replication Server Version 15.0?
Replication Server on Solaris 8, Solaris 9, and Solaris 10 (Opteron) supports Internet Protocol Version 6 (IPv6).
Master database replication
With Adaptive Server Enterprise version 15.0, ESD #2, the master database can now be replicated with any version of Replication Server that supports warm standby, including Replication Server version 12.0 and later. Replication of the master database is limited to system procedures and the commands used to manage logins and roles, and includes but is not limited to:
This section lists the optional features available for Replication Server. To purchase any of these licensed options, contact your Sybase sales representative.
Replication Agent and Enterprise Connect Data Access
Sybase Replication Agent™ and Enterprise Connect™ Data Access are available as a product called Replication Server Options, which is available separately from Replication Server. You must already have Replication Server to obtain Replication Server Options.
You can use Replication Server Options with Replication Server for bidirectional replication across distributed, heterogeneous systems to enable different operational and decision-support tasks.
The Replication Server Options are compatible with the same platform and operating system configurations with which Enterprise Connect Data Access 12.6 and Sybase Replication Agent 12.6 are compatible. For specific hardware and software requirements, see the documentation for Enterprise Connect Data Access 12.6 and Sybase Replication Agent 12.6.
There are four Replication Server Options available. Each option contains licenses for accessing data only in the specified data source: Informix, Microsoft, Oracle, or DB2 UDB.
In addition to the two components, each option contains an Adaptive Server® Enterprise (ASE) and an EBF for jConnect™ for JDBC™.
Special installation instructions
This section includes special installation instructions that are not in the installation guide for your platform.
Selecting an installation directory for Replication Server
You must choose carefully whether to install Replication Server in its own product directory or in a directory with your other Sybase products. In some cases, installing Replication Server on top of existing Sybase applications can adversely and irreversibly affect those applications.
Installing Replication Server in an existing directory
Installing Replication Server in an existing directory that contains other Sybase products may result in Replication Server and other Sybase products not working correctly. Before you install Replication Server in an existing directory, take note of the following:
Installing Replication Server in a unique directory
You can install Replication Server in a unique directory without affecting existing Sybase environment variables. Follow the standard installation instructions in the Replication Server Installation Guide for UNIX.
Note:When you install Replication Server in a unique installation directory, you must maintain two interfaces files—one interfaces file for Replication Server components and another for your other Sybase applications.
Installing Replication Server on 64-bit machines
On 64-bit machines, you cannot install Replication Server version 15.0 in the same directory structure as Adaptive Server.
Co-existing with earlier versions of SySAM
Replication Server version 15.0 uses a newer version of the Sybase Software Asset Management System (SySAM) licensing technology and an updated license format. On any machine, you can have only one instance of a license server running. You must make some adjustments to use earlier versions of Sybase products with Replication Server 15.0. To make these adjustments, see “Co-existing with earlier versions of SySAM,” in Chapter 1, “Before You Begin” in the Replication Server Installation Guide for Linux.
Other sources of installation information
This section describes Replication Server installation and configuration issues. For more information, see:
If you are using a pre-11.5 version of Adaptive Server Enterprise, see its installation and configuration documentation regarding upgrading replicated databases.
Special upgrade and downgrade instructions
The Replication Server Configuration Guide for UNIX contains detailed upgrade and downgrade instructions. Sybase strongly recommends that you read this information before you upgrade or downgrade Replication Server.
This section documents special upgrade and downgrade instructions in Replication Server version 15.0.
Preparing to upgrade
For upgrading, the Replication Server version should be 12.0 or later and the Adaptive Server containing the RSSD should be 12.5 or later. Upgrading from any earlier version requires an intermediate upgrade.
Upgrading route versions
If you have a primary Replication Server version 12.0 or 12.1 that you plan to upgrade to version 15.0 and you have a replicate Replication Server already upgraded to version 15.0, use the Upgrade Route option in Replication Manager instead of the rs_fast_route_upgrade stored procedure to upgrade the related route to the replicate Replication Server.
In Replication Manager, right-click on the Replication Server object containing the route to be upgraded, select the Upgrade Route option, select the route to be upgraded from the dialog box that appears, and select Upgrade.
A route version should reflect the lower value between the site version of your primary Replication Server and the site version of your replicate Replication Server. For example, if the site version of your primary Replication Server is 12.1 and the site version of your replicate Replication Server is 12.0, the route version should be 1200.
However, the version of rs_fast_route_upgrade provided in Replication Server version 12.1 and earlier erroneously sets the route version to the higher value. For this reason, the earlier version of rs_fast_route_upgrade automatically upgrades the route version to 1500 even if your primary Replication Server has not yet been upgraded to version 15.0.
If this applies to your replication system and you are upgrading to Replication Server version 15.0, the upgrade script stops and tells you to fix the route version before upgrading to version 15.0.
Updating LTL version
When the RepAgent connects to the Replication Server, it returns a Log Transfer Language (LTL) version.
When you upgrade to Replication Server version 15.0, the RepAgents are still connected to Replication Server using the older negotiated LTL version. Restart the RepAgents to use the new LTL version.
New and changed functionality
For detailed descriptions of the new features and functionality in Replication Server 15.0, see What’s New in Replication Server Version 15.0?
This section documents known problems in Replication Server version 15.0. These problems are identified with Change Request (CR) numbers, to which you can refer when contacting Sybase Technical Support. Workarounds are provided where available.
Problem report location
This section identifies where problem reports are located.
Open and fixed problem reports for Replication Server software are in the $SYBASE/$SYBASE_REP/install/SPR directory. The following files contain problem reports for Replication Server version 15.0:
Replication Manager plug-in
Open and fixed problem reports for the Replication Manager plug-in are in the $SYBASE/RMP-15_0/install/SPR directory.
The following files contain problem reports for this version of the Replication Manager plug-in for Sybase Central:
Replication Monitoring Services
Open problem reports for the Replication Monitoring Services that interfaces with the Replication Manager plug-in are in the $SYBASE/ua/plugins/com.sybase.rms/install/SPR directory. The following file contains the problem reports for RMS:
Highlighted problems with Replication Server
This section describes problems with Replication Server.
delete command for multiple rows may not replicate correctly
[CR #203009] A delete command that affects multiple rows at the primary database may not replicate successfully at the replicate database if the primary database contains self-referential foreign-key constraints.
Workaround: Use any one of the following workarounds:
DSI shuts down
DSI shuts down if transaction owner and standby maintenance user have same name
[CR #219525] In a warm standby configuration, the Replication Server shuts down the Data Server Interface (DSI) with an error if the data definition language (DDL) transaction owner and warm standby maintenance user have the same name.
Workaround: When you are configuring a warm standby replication environment, do not create the standby database maintenance user with the same user name as the DDL transaction owner.
Warm standby replication definition not recognized for non-database owner qualified table with more than 128 columns
Workaround: Re-create table as database owner.
Decimal with exponent incorrectly translated
[CR #233839] When using a user-defined datatype that defines a decimal type, if the decimal data contains an exponent, when replicating that column to a column of integer type, it may be incorrectly translated. For example, 5.62E3 is translated to 6 instead of 5620.
Effects of alter replication definition not immediate
[CR #235302] If rows are inserted too quickly after an alter replication definition command completes, the first few rows may not recognize the changes made by the alter replication definition command.
Workaround: Before inserting rows, wait at least 60 seconds after an alter replication definition command completes.
DSI error 5147 for replication definitions with several text columns if replication definitions do not allow NULL
[CR #270741] If you create a replication definition with three or more text columns that does not allow the NULL value, the DSI stops responding, and generates error 5147 if you replicate a row from a table that allows the NULL value.
Adaptive Server row-level locking may cause System Table Services cache problems
[CR #276758] When using Adaptive Server row-level locking for System Table Services (STS) tables, Replication Server can report that an STS object does not exist when in fact it does exist in the RSSD. This happens because with Adaptive Server row-level locking, when there are two concurrent transactions, one transaction deletes and then inserts a row, while the other transaction tries to select the same row. When this occurs, the select command fails to retrieve the row.
Workaround: You can either restart Replication Server, or use the following command for the appropriate table when it has a row that exists in the RSSD but is missing from the cache:
sysadmin stscache, fillcache, tablename
Replication Server does not preprocess table names qualified with database name
[CR #332068] When you use the Adaptive Server plug-in to issue data definition language (DDL), the plug-in uses fully a qualified identifier in the DDL. If you use multisite availability (MSA) to replicate this DDL, and the replicate database does not have the same name as the primary database, MSA cannot apply the DDL, and Data Server Interface is suspended.
Workaround: Do not use the Adaptive Server plug-in for Sybase Central to create tables for use in this environment, and do not use fully qualified table names when using MSA to replicate DDL.
Dropping a subscription that has failed causes a stack trace
Workaround: Restart Replication Server.
Turning on hibernation mode may cause a stack trace
Language modules not listed
[CR #419838] When you select Full Install, the French, Chinese, and Japanese language modules are not shown in the list of Replication Server language modules. These languages are installed as part of a Full Install even though they are not listed by InstallShield.
Cannot start Replication Server without -S flag
[CR #65722] You cannot use the DSLISTEN environment variable to specify the Replication Server name. Replication Server stops responding after it prints the message “Contacting the idserver for a siteid.”
Workaround: You must specify the Replication Server name with the -S flag on the repserver command line.
Replication Manager problems
This section discusses problems with the Replication Manager.
New active connection suspends when created
[CR #336879] When you create a logical connection from an existing physical connection, the Replication Agent on the active connection becomes suspended, and you see an error in the Replication Server’s log that the -W warm standby option must be set in the active database’s Replication Agent.
Workaround: The plug-in correctly configures the Replication Agent properties for the database, but you must manually resume the active connection after creating the logical connection.
Plug-in must be unregistered after uninstallation
[CR #337408] The uninstallation process for the Replication Manager plug-in does not unregister the plug-in from Sybase Central. When you log in to Sybase Central and unregister the plug-in, Sybase Central displays an error when you restart your machine that says it cannot find the Replication Manager plug-in.
Workaround: You can ignore the message. Start Sybase Central and unregister the Replication Manager plug-in.
Configure Replication wizard may not work under certain circumstances
[CR# 371403] Using the Configure Replication wizard to set up a replicate database where the primary database is an existing warm-standby logical connection does not result in a working replication environment.
Workaround: Use Replication Manager to create each individual component in the replication environment such as the connection, the database replication definition, and the database subscription.
Cannot specify owner and password when creating subscriptions
[CR# 386456] When you create a subscription, Replication Manager does not allow you to specify a login and password. You have to use the same "sa" login and password that Replication Manager uses for adding servers to the replication environment.
If you are using atomic materialization, the "sa" login and password must be the same as that used on the Adaptive Server data server, or atomic materialization will not work. This restriction does not apply when you create a database subscription as it does not include the atomic materialization option.
Workaround: Use the same "sa" login and password for creating subscriptions in Replication Manager that you use for adding servers, and that you use for the Adaptive Server.
Status not updated when monitoring is turned on
Workaround: Perform a manual refresh to update the status. Do this from the Sybase Central main menu, selecting either View | Refresh Folder or View | Refresh All.
RM does not report a failure
Workaround: Check the log files for the components that are involved, to determine the reason for the failure to add the server. When you have resolved the problem, try adding the server to the environment again.
RM does not report reason for a secondary RMS with SUSPECT state
[CR #418026] When you add a secondary Replication Monitoring Services (RMS) under a primary RMS, and the secondary RMS status is reported as SUSPECT, Replication Manager does not immediately report any information about this in the Reason column of the List view or in the Details pane of the suspect RMS.
RM may not accurately reflect status in a three-tier environment
[CR #418128] When the Adaptive Server in a three-tier management environment is in a SUSPECT state, it is not reflected in the Tree view and Details view of Replication Manager. In the Properties dialog of the Details view, the status of the Adaptive Server displays as ACTIVE.
Replication Monitoring Services problems
This section discusses problems with Replication Monitoring Services (RMS).
RMS cannot start RepAgent if sp_addserver is not run on Adaptive Server
Workaround: Before you use RMS to start RepAgent, run sp_addserver on Adaptive Server to define the name of the local server:
sp_addserver pds01, local
where pds01 is the name of the Adaptive Server on which you want to run RepAgent and local is the class parameter value, since the Adaptive Server is the local server. See Chapter 1, “System Procedures,” in the Adaptive Server Reference Manual: Procedures for more information on sp_addserver.
Sybase Central problems
This section discusses problems with Sybase Central.
Users must have write privileges to home directory
[CR# 343973] Sybase Central writes a registry file in the user’s home directory, and uses this registry file to store environment information from the Replication Manager. Users must have write privileges on their home directory, or Sybase Central cannot save the environment information.
Workaround: Ensure that each user has write privileges to his or her home directory.
scjview.sh file cannot reference RMPlugin.jar in CLASSPATH definition
[CR #377040] If you add a reference to the RMPlugin.jar file in the CLASSPATH definition of the scjview.sh file, it causes the Replication Manager plug-in to lose certain components and not function correctly.
Workaround: Do not include a reference to the RMPlugin.jar file in the CLASSPATH definition when you manually register the Replication Manager plug-in into Sybase Central.
Sybase Central stops responding when command log fills up
[CR #387922] Sybase Central provides a central log where each plug-in can write error messages and details about its execution. The Replication Manager (RM) plug-in uses this Sybase Central command logging feature to provide a log of all commands sent by RM to managed servers.
If command logging is turned on, commands at every monitoring interval are written to the Sybase Central log. Sybase Central does not limit the number of entries in the log, the log can fill up and cause Sybase Central to stop responding.
Workaround: Monitor the log closely. You may archive the log or delete entries in the log to clear the memory.
Highlighted rs_init problems
This section discusses problems with rs_init, the Replication Server configuration utility.
rs_init does not update interfaces file automatically
[CR #171729] When attempting to add a Replication Server entry to the interfaces file through rs_init using a resource file, a message displays indicating that the interfaces file has been updated. However, the file is not updated, and Replication Server does not start.
Workaround: Create the entry in the interfaces file manually before using rs_init with the resource file.
Cannot use korean/eucksc character set to configure Replication Server with us_english/iso_1
[CR #415971] Replication Server does not start if you use korean with the euckcs
character set on the rs_init command
Workaround: Use korean with the euckcs character set on the rs_init command line and configure Replication Server for korean and euckcs.
rs_init does not support the mac character set
[CR #419737] You cannot use rs_init to configuration Replication Server if you use the mac character set and the configured Replication Server character set is defined to mac. A syntax error is reported by rs_init and the Replication Server does not start.
Workaround: Use any character set other than mac when starting rs_init.
Default size for the RSSD log device is too small
[CR #420216] The rs_init default RSSD log device size of 16MB is too small when you are using an Adaptive Server 15.0 for the RSSD database. The rs_init process fills the RSSD log device before the RSSD is created, and rs_init reports the following message from the Adaptive Server hosting the RSSD:
SQL Server message: msg 7415, level 10, state 1 "The transaction log in database RSSD Database is almost full. Your transaction is being suspended until space is made available in the log."
Workaround: If this situation occurs, you must expand the RSSD log device before rs_init can continue. Use:
After the additional log space is provided, rs_init completes the initialization of the RSSD and Replication Server will function correctly. Avoid this problem by creating the RSSD log device with a size of 25MB or larger.
Incompatible character set specification using rs_init
[CR #68642] rs_init does not prevent you from creating a configuration file using an RS_charset parameter that is incompatible with the character set defined in the CONFIG_charset parameter. For example, if the configuration file defines an English character set but the CONFIG_charset parameter is set to a Japanese character set, the installation proceeds but behaves unpredictably.
Workaround: Use compatible character sets.
rs_init does not correct run files
Workaround: Edit the run files manually.
The following Adaptive Server operations may cause incorrect replicated data:
This section contains information about products that are compatible with Replication Server version 15.0.
Replication Server version 15.0 is fully compatible with both 32-bit and 64-bit versions of Adaptive Server Enterprise version 12.0 and later.
See the documentation for Adaptive Server version 12.0 and later for more information on product requirements.
A replication system can include Adaptive Servers, Replication Servers, DirectConnect products, and RepAgents on multiple platforms.
Note:SQL Server versions 11.0.x and earlier are no longer supported.
Interoperability of Adaptive Server, Open Client/Server, and Replication Server
Table 1 shows the interoperability of Adaptive Server, Open Client/Server products, and Replication Server across versions.
Replication Server is a 32-bit application and it has been certified on both the 32-bit and 64-bit versions of the HP-UX, IBM AIX, and Sun Solaris operating systems listed in Table 1.
Even though two or more products may be interoperable, new features introduced in a newer version of a product are not likely to be supported by older versions of the same products.
For the latest information on the interoperability of these product and other compatibility reports, see the Interoperability Matrix Technote.
Documentation updates and clarifications
This section contains updates and clarifications to the Replication Server documentation.
Replication Manager online help
This section describe updates to the Replication Manager online help.
Corrections to the Using the Interface book
In the Using the Interface book, the last topic listed in the left pane, “Using the stored procedure replication interface,” is incomplete and contains inaccurate information. The updated information is below:
Managing stored procedure replication
Replication Manager lets you manage stored procedure replication. The replication definition for stored procedure replication is called a “function replication definition,” or a “function rep def.” Replication Server limits you to one function replication definition per stored procedure. Stored procedure subscriptions are supported.
You can find function replication definition in the Function Replication Definitions folder under the individual stored procedure, which is in the Stored Procedures folder. For example, to find the function replication definition mySP_repef for stored procedure mySP, navigate through Sybase Central by selecting Stored Procedures | mySP | Function Replication Definitions | mySP_repdef.
Stored Procedure Properties dialog box
When you right-click a Stored Procedure, and select Properties from the Stored Procedures context menu, the Stored Procedures Properties dialog box opens. From the Stored Procedures Properties dialog box, you have access to the following tabs:
Adding a function replication definition
The Add New Function Replication Definition dialog box enables you to create a new replication definition for the selected stored procedures, displaying several tabs:
Using the Function Replication Definition context menu
Right-click the function replication definition to access the Function Replication Definition context menu, which gives you access to the following commands:
Adding a subscription
You must create a function replication definition before you can subscribe to it. Typically, you create the function replication definition for a stored procedure under its primary database, and subscribe to the function replication definition under its replicate database.
The Add New Subscription dialog box enables you to create a new subscription for the selected stored procedures, displaying several tabs:
Using the Subscription context menu
Right-click the subscription to access the Subscription context menu, which gives you access to the following commands:
This section describes updates to the Replication Server Administration Guide.
startup delay configuration parameter
With Adaptive Server Enterprise version 15.0, ESD #2, the startup delay configuration parameter is added to the list of configuration parameters for the sp_config_rep_agent system procedure in “Table 5-1: Configuration parameters affecting RepAgent,” in Chapter 5, “Setting Up and Managing RepAgent” in the Replication Server Administration Guide: Volume 1.
For example, to delay RepAgent start-up by 50 seconds, enter:
sp_config_rep_agent dbname, 'startup delay', '50'
This section describes updates to the Replication Server Reference Manual.
startup delay configuration parameter
With Adaptive Server Enterprise version 15.0, ESD #2, the startup delay configuration parameter is added to the list of configuration parameters for the sp_config_rep_agent system procedure in Chapter 5, “Adaptive Server Commands and System Procedures” in the Replication Server Reference Manual.
For example, to delay RepAgent start-up by 50 seconds, enter:
sp_config_rep_agent dbname, 'startup delay', '50'
recovery_foreground configuration parameter
With Adaptive Server Enterprise version 15.0, ESD #2, the recovery_foreground configuration parameter is added to the list of parameters for the sp_start_rep_agent system procedure in Chapter 5, “Adaptive Server Commands and System Procedures” in the Replication Server Reference Manual.
For example, to display the recovery progress information for database dbname for which you want to start a RepAgent, where connect_dataserver is the data server used to recover offline logs and connect_database is the database used to recover offline logs, enter:
sp_start_rep_agent dbname, 'recovery_foreground', 'connect_dataserver', 'connect_database'
Language and globalization issues
This section describes language and globalization issues for Replication Server.
Hankaku Katakana conversion
In general, Japanese character sets are compatible. However, Hankaku Katakana characters, although they exist in both the eucjis and sjis character sets, cannot be converted. Converting data that contains Hankaku Katakana characters between eucjis and sjis will not work. This conversion problem occurs with character datatypes and the text datatype. It is documented in Chapter 20, “Configuring Client/Server Character Set Conversions,” of the Adaptive Server Enterprise System Administration Guide.
This conversion problem affects both Adaptive Server and the Sybase Open Client/Open Server libraries. Because Replication Server uses these libraries for all conversions, this problem also affects Replication Server.
In Replication Server, this type of failure is treated in the same way as is the case of a single character missing from the target character set. The remainder of the conversion succeeds and replication proceeds, and problem characters are replaced by question marks in the target data area. There is currently no way to escape this restriction with the Sybase connectivity libraries. However, in Adaptive Server, if you turn on trace flag number 2402, you can remove this restriction.
Using trace flag 2402
Generally, Sybase recommends that you set up your replication system so that Replication Server handles all character set conversions at the replicate Replication Server and prevents the replicate data server from performing any conversions. In this case, you can work around the Hankaku Katakana restriction if you set up your system so that the replicate data server performs the conversion.
The following table shows how this might look if the primary data server used the sjis character set and the replicate data server used eucjis. Communication in this system is between each data server and its Replication Server and between the two Replication Servers.
The primary and replicate Replication Servers are configured to use the same character set as the primary data server. (If only one Replication Server manages the primary and replicate data servers, configure it with the character set of the primary data server.)
In this configuration, when the replicate Replication Server connects to the replicate data server with character set sjis, the replicate data server detects this condition and converts data into its own character set, eucjis. If trace flag 2402 is activated in the replicate data server, then the conversion includes the Hankaku Katakana characters.Setting up this workaround
Changing default date format for a language
If you modify the common.loc file to change the default date format for a given language, make the corresponding change to the syslanguages table on all affected Adaptive Servers.
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.
Other sources of information
Use the Sybase Getting Started CD, the SyBooks CD, and the Sybase Product Manuals Web site to learn more about your product:
Sybase certifications on the Web
Technical documentation at the Sybase Web site is updated frequently.Finding the latest information on product certifications
Set up a MySybase profile. MySybase is a free service that allows you to create a personalized view of Sybase Web pages.
Sybase EBFs and software maintenanceFinding the latest information on EBFs and software maintenance
This document is available in an HTML version that is specialized for accessibility. You can navigate the HTML with an adaptive technology such as a screen reader, or view it with a screen enlarger.
Replication Server and the HTML documentation have been tested for compliance with U.S. government Section 508 Accessibility requirements. Documents that comply with Section 508 generally also meet non-U.S. accessibility guidelines, such as the World Wide Web Consortium (W3C) guidelines for Web sites.
Note:You might need to configure your accessibility tool for optimal use. Some screen readers pronounce text based on its case; for example, they pronounce ALL UPPERCASE TEXT as initials, and MixedCase Text as words. You might find it helpful to configure your tool to announce syntax conventions. Consult the documentation for your tool.
For information about how Sybase supports accessibility, see Sybase Accessibility. The Sybase Accessibility site includes links to information on Section 508 and W3C standards.