Release Bulletin Sybase® Replication Agent™ Version 15.0 for Linux, Microsoft Windows, and UNIX
Document ID: DC78260-01-1500-01
Last revised: November 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 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
Replication Agent™ extends the capabilities of Replication Server® by allowing non-Sybase database servers to act as primary data servers in a replication system based on Sybase replication technology.
Sybase Replication Agent 15.0 runs on the platform and operating system configurations listed in Table 1.
Replication Agent version 15.0 supports the database servers and versions listed in Table 2.
Sybase Replication Agent 15.0 is compatible with the other Sybase products listed in Table 3.
Sybase Replication Agent 15.0 requires a JDBC 2.0-compliant driver to communicate with the primary data server. Table 4 lists the JDBC drivers that are compatible with Sybase Replication Agent 15.0.
Special installation instructions
This section documents installation issues not covered in the Replication Agent Installation Guide.
Empty directories after uninstalling
After uninstalling Sybase Replication Agent software, some empty directories might be left. You can safely remove these directories. To remove them, go to the installation directory and delete the Replication Agent directory (RAX-15_0) and all its subdirectories and their contents.
Operating system patch requirements
Sybase Replication Agent 15.0 is compatible with Microsoft Windows 2000 and 2003, as well as several UNIX operating systems. See “Product summary” for more information on operating system versions supported by Replication Agent 15.0.
There might be Java-related patches for the Solaris, HP-UX, and AIX operating systems that you should install before installing the Java Runtime Environment (JRE) 1.4.2 (32-bit) included with Replication Agent. The following sections describe how to find any operating system patches that might be required for Sybase Replication Agent 15.0.
See the Web site for your operating system to verify that the patches for your database server are current.
HP-UX PA-RISC patches can be found at the following URL:
Solaris SPARC patches can be found at the following URL:
AIX patches can be found at the following URL:
Special upgrade instructions
Customers using Replication Agent version 12.5 or 12.6 can migrate to Replication Agent 15.0 by following the migration instructions in Appendix A of the Replication Agent Primary Database Guide.
This section describes known problems in Sybase Replication Agent 15.0 at the time of release. These problems are identified with Change Request (CR) numbers, to which you can refer when contacting Sybase Technical Support. Workarounds are provided where available.
Known issues for the Sybase Installer
This section describes known issues with the Sybase Installer that are not specific to a particular data server type.
Cannot view text fields properly when using a Hummingbird Exceed client
If you use Hummingbird Exceed from a Windows work station 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 Installer, or run the Sybase Installer in console or silent mode. See the Replication Agent Installation Guide for details.
Sybase Central fails to open after Replication Agent uninstallation
[CR# 399954] After the uninstallation of Replication Agent, the SYBASE system environment variable is removed and Sybase Central does not open.
Workaround: Redefine the SYBASE system environment variable.
Known generic issues for Replication Agent 15.0
This section describes known issues in Sybase Replication Agent 15.0 that are not specific to a particular environment or data server type.
Edits on pending property changes
[CR#211427] Validation of changes made to Replication Agent configuration parameters might not occur until the Replication Agent instance is restarted. If you enter an invalid configuration parameter value, an error might not be returned until the Replication Agent instance is restarted.
Workaround: Restart the Replication Agent instance immediately after you change a configuration parameter that requires a restart to take effect.
New implementation of JISAutoDetect
The following JREs that have the Daylight Saving Time fix also have a bug associated with the use of the JISAutoDetect character set: Solaris SPARC, Linux, Windows: 1.4.2_12, HP PA-RISC: 1.4.2_11
Replication Agent currently does not support this character set. The JISAutoDetect character set “Detects and converts from Shift-JIS, EUC-JP, ISO 2022 JP (conversion to Unicode only).”
Known issues for IBM DB2 UDB
This section describes known issues in Replication Agent version 15.0 that are specific to the IBM DB2 UDB.
NoClassDefFoundError if library path contains two colons
On HP, if the SHLIB_PATH contains two colons (::) with no intervening directory, when you resume the Replication Agent you get the following error message:
Workaround: Add a line to the $SYBASE/RAX-15_0/bin/ra.sh script to source your UDB instance’s db2profile (which does not have the same problem as the db2cshrc). For example, if your UDB instance directory is “/home/db2inst1”, edit your Replication Agent script as follows:
elif [ $os = HP-UX ] then SRVR=-server SHLIB_PATH=$ASA_LIB:$RAX_DIR/lib/hpux:$SHLIB_PATH export SHLIB_PATH
elif [ $os = HP-UX ] then . /home/db2inst1/sqllib/db2profile SRVR=-server SHLIB_PATH=$ASA_LIB:$RAX_DIR/lib/hpux:$SHLIB_PATH export SHLIB_PATH
Known issues for Microsoft SQL Server
This section describes known issues in Replication Agent version 15.0 that are specific to the Microsoft SQL Server data server.
Microsoft isql tool
The interactive query tool provided with Microsoft SQL Server is Microsoft isql. You must use Microsoft isql (or a compatible tool) to access the Microsoft SQL Server database to execute some of the test scripts documented in the Replication Agent Primary Database Guide.
Note:Although the name of the Microsoft isql tool is the same as the Sybase tool called isql, the Sybase and Microsoft tools are not compatible. For example, you cannot use the Sybase isql tool to access the Microsoft SQL Server data server, and you cannot use the Microsoft isql tool to access the Replication Agent administration port.
If you have both Sybase and Microsoft isql tools loaded on the same machine, you might need to change an environment variable (possibly the PATH variable) to avoid problems when you invoke one of the isql tools.
Known issues for Oracle
This section describes known issues in Replication Agent version 15.0 that are specific to the Oracle data server.
rasd_database and rasd_tran_log commands fail with default value
[CR# 386246] When you use the rasd_database and rasd_tran_log properties with the default value, the commands fail.
Workaround: Supply a specific value.
Oracle-to-Oracle LOB replication fails
[CR# 400077] Replicating large-object data in an Oracle-to-Oracle environment fails.
Workaround: Download Enterprise Connect Data Access Option for Oracle version 12.5.7 or 12.6.1. See “Sybase EBFs and software maintenance” for details on downloading.
pdb_setrepddl enable fails when use_rssd is set to false
[CR# 404985] If you are using a database replication definition and use_rssd is set to false, the pdb_setrepddl enable command fails.
Workaround: Set use_rssd to true.
Viewing trace log in vi returns error
[CR# 404994] Viewing a trace log
in vi may return a “
Workaround: View the trace log using a different editor.
alter type DDL command has limited support
[CR# 405206] During replication of the alter type command, the type change does not propagate to the dependents of the type.
Workaround: The Replication Agent must be re-initialized to recognize the changed type.
create table DDL has limited support for UDD object types
[CR# 405207] UDD object types with nested object types are not supported for create table DDL commands.
Workaround: The Replication Agent must be re-initialized to recognize the new table.
pdb_setreptable may fail for a table that contains a column with a new UDD object type
[CR# 405269] The pdb_setreptable command may fail for a table that contains a column with a UDD object type that has been created after initialization and before resuming replication.
Workaround: Resume replication, wait, and mark the table again.
Disabling the recyclebin in Oracle 10.1
The Oracle “recyclebin” configuration property was not added until Oracle 10.2. To disable the recycle bin in Oracle 10.1, you must set the Oracle hidden property:
ALTER SYSTEM SET “_recyclebin”=FALSE SCOPE = BOTH;
Documentation updates and clarifications
This section describes changes made to the Replication Agent documentation.
Replication Agent Primary Database Guide
(This additional information applies only to Oracle.) Similar to the support for table and procedure replication, Oracle Sequences are individually marked for replication using the new Replication Agent pdb_setrepseq command. For a description of the pdb_setrepseq command, refer to the Sybase Replication Agent Reference Guide.
Chapter 3, Replication for Oracle
The following information for the “Understanding Oracle Sequence replication” section needs to be added.
Logging of Oracle Sequence information
Individual sequence changes are not logged in the Oracle database log file; however, changes to Oracle Sequences do impact (update) the Oracle sys.seq$ table. These changes do not occur with each new sequence value generated. Instead, the sys.seq$ table is updated periodically, based on sequence caching refresh activity or other system changes. The value stored in the sys.seq$ table for a sequence is the “next” value to be assigned “after” the existing cache of values has been exhausted.
For example, a newly created sequence starts with a value of 1, increments by 1, and has a cache value of 20. (These are all default values and can be customized.) The value stored in the sys.seq$ record for this new sequence is 21. This indicates that the “next” value to be used by the sequence, after the existing cache of 20 numbers is used, is 21. The record in sys.seq$ does not change until the sequence value hits 21. At that time, Oracle will cache the next 20 values for the sequence, and the sys.seq$ record will be updated to 41. It is this value (41), recorded in change to the sequences sys.seq$ record, that will be used for replication. The key point is to recognize that not every individual sequence update is recorded in the log and therefore is not available for replication.
Replicating sequence changes
When a sequence is marked for replication, changes to that sequence against sys.seq$ are captured and sent to Replication Server in the form of parameters passed to a procedure. The procedure (rs_update_sequence) must be installed at the standby site as part of system setup, as well as a function replication definition for that procedure. At the standby site, an implementation of rs_update_sequence will increment a same-named sequence until its value is equal to the value at the primary site. Scripts are provided with installation to create the rs_update_sequence stored procedure and function replication definition and are located as follows:
$SYBASE/RAX-15_0/scripts/ oracle_create_replicate_sequence_proc.sql $SYBASE/RAX-15_0/scripts/ oracle_create_rs_sequence_repdef.sql
Compared to the performance of incrementing a sequence at the primary database, particularly where sequence values are cached, the effort to increment the same sequence at the standby site may be less efficient. The stored procedure must dynamically determine the sequence to increment and must loop internally, incrementing the sequence until the primary value has been reached. The loop is required because there is no way to assign a specific value to a sequence.
Because the name of the sequence is passed as a parameter, Oracle cannot pre-compile the procedure for efficiency. With the addition of the looping activity required to properly increment the sequence, the performance of the solution may impact some environments where a large number of highly used sequences is the norm.
Sequence replication alternatives
If the performance of sequence replication is a concern, other alternatives to replication are available that support primary and standby use of the same sequence. These alternatives are currently suggested by Oracle and others interested in providing sequence coordination between multiple sites:
Replication Agent permissions (Oracle only)
Replication Agent for Oracle uses the pds_username command to connect to Oracle. You must grant the Oracle permissions that are currently identified in the Sybase Replication Agent Primary Database Guide, including the addition of the following:
Flashback enhancements (replace this section with the following)
Oracle's new flashback feature available in Oracle version 10g is not supported in Replication Agent for Oracle. Because flashback is not supported, it requires that you disable the recycle bin:
In Oracle 10.2, to view the contents of the recycle bin:
select * from dba_recyclebin;
In Oracle 10.2, to view the current recycle bin configuration:
select value from v$parameter where name = “recyclebin”;
Sybase Replication Agent Reference Manual
The following is a correction to the existing documentation.
Chapter 1, Command Reference
The following correction specifies the use of the command pdb_setreptable using the keyword owner.
Specifying the owner of a table in a replication definition
Table-marking behavior has changed when you specify the owner of a table in a replication definition. Now, you must always use the owner keyword if you want to enable the SEND OWNER mode. When marking, if you do not specify the replicate owner, it defaults to the primary owner.
In the following examples, the leading letter indicates either primary (p) or replicate (r):
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.To find 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 maintenanceTo find 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.
Sybase Replication Agent 15.0 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.