Switch to standard view 
  Sybase logo

Release Bulletin Mirror Replication Agent™ 15.2 for Linux, Microsoft Windows, and UNIX


Document ID: DC00713-01-1520-01

Last revised: May 2009


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

  1. Go to Product Manuals.

  2. Select a product and language and click Go.

  3. Select a product version from the Document Set list.

  4. Select the Release Bulletins link.

  5. From the list of individual documents, select the link to the release bulletin for your platform. You can either download the PDF version or browse the document online.


Product summary

Mirror Replication Agent™, which is a component of Mirror Activator™, 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.

Platforms and operating systems

Mirror Replication Agent 15.2 software requires one of the platforms and operating system versions listed in Table 1.

Table 1: Platform and operating system requirements


Operating system version

HP Itanium

HP-UX 11.31 (64-bit only)

IBM RISC System/6000

IBM AIX 5.3, 6.1 (64-bit only)


Linux x86 and x64a:

  • Red Hat Enterprise Linux 4.4:Kernel version 2.6.9-22.EL

  • Red Hat Enterprise Linux 5.1:Kernel version 2.6.18-8.e15

  • SuSE Linux Enterprise Server 10:

    Kernel version

Microsoft Windows

Windows x86 and x64a:

  • Windows Server 2003

  • Windows Server 2008

  • Windows Server XP Professional

  • Windows Server Vista 6.0.6000

Sun Solaris (SPARC)

Sun Solaris 9, 10 (64-bit only)

a. Mirror Replication Agent binary is 32-bit word size that runs on both the 32-bit and 64-bit platforms.

Note:Before you install the Mirror Replication Agent 15.2 software, you must install the most recent operating system patches recommended by your operating system vendor for Java 6.0 support. For details, see “Operating system patch requirements”.

Table 2 lists the minimum physical memory, storage, and media device requirements on the Mirror Replication Agent host machine. Your Mirror Replication Agent configuration may require more memory and disk space than the minimums listed in Table 2.

Table 2: Memory, disk space, and media device requirements


Disk space

Media device


300MB hard disk

CD drive

Compatible products

Table 3 lists the database server versions supported by Mirror Replication Agent 15.2.

Table 3: Databases compatible with Mirror Replication Agent



Adaptive Server Enterprise (ASE)

Cluster Edition 15.0.1 ESD #2 and later 15.0.2 ESD #4 and later 15.0.3

Oracle Server

10g (10.1, 10.2), 11g (11.1)

Mirror Replication Agent requires a JDBC 3.0-compliant driver for the primary data server. Table 4 lists the JDBC driver versions required to support connectivity between Mirror Replication Agent 15.2 and the primary data server.

Table 4: Drivers compatible with Mirror Replication Agent



Oracle JDBC

10.2 or 11.1 for JDK 1.4 and 1.5

Mirror Replication Agent 15.2 is compatible with the Sybase products listed in Table 5.

Table 5: Mirror Replication Agent compatibility

Sybase product


Replication Server

15.0.x, 15.1, 15.2

ECDA Option for Oracle

15.0 ESD #3 and later

Sybase Software Asset Management (SySAM)



Special installation instructions

This section explains installation issues that are not covered in the Mirror Replication Agent Installation Guide.

Operating system patch requirements

Mirror Replication Agent 15.2 is compatible with several Microsoft Windows and several UNIX operating systems. See “Product summary” for more information on operating system versions supported by Mirror Replication Agent 15.2.

There might be Java-related patches for the Solaris, HP-UX, and AIX operating systems that you should install before installing Mirror Replication Agent. The following sections describe how to find any operating system patches that might be required for Mirror Replication Agent 15.2.

Note:See the Web site for your operating system to verify that the patches for your database server are current.


See the list of HP-UX patches for HP Itanium http://docs.hp.com/en/HPUXJAVAPATCHES/index.html


See the list of Solaris SPARC patcheshttp://java.sun.com/javase/downloads/index.jsp


See the list of AIX patcheshttp://www.ibm.com/developerworks/java/jdk/aix/service.html


Special upgrade instructions

If you are using earlier versions of Mirror Replication Agent, you can upgrade to Mirror Replication Agent 15.2 by following the upgrade instructions in Appendix A of the Mirror Replication Agent Primary Database Guide.


Known issues

This section describes known issues in Mirror Replication Agent 15.2 at the time of release. Some of these issues are identified with Change Request (CR) numbers to which you can refer when contacting Sybase Technical Support. Workarounds are provided where available.

Note:For issues relating to Replication Server 15.2. see the appropriate Mirror Replication Server Release Bulletin, and for Enterprise Connect Data Access 15.0, see the appropriate Enterprise Connect Data Access Release Bulletin.

The issues are grouped by the database targets that they affect:

Known issues for all database targets

This section describes known issues in Mirror Replication Agent 15.2 that are not specific to a particular environment or data server type.

Objects in encrypted tablespace are not supported

[CR #552991] Sybase does not support replication from objects (tables and columns) stored in an encrypted tablespace.

Workaround: None.

Error while loading shared libraries when running on Red Hat Linux 5.0

You may be unable to start Mirror Replication Agent due to this error message:

Error while loading shared libraries.

Workaround: Check the system configuration and change the firewall configuration from enforcing to permissive. You must have root or sudo permission to make this change.

Known issue for ASE

This section describes known issues in Mirror Replication Agent 15.2 that are specific to ASE.

Marking and unmarking tables and procedures with insufficient time allocated

[CR #568916] When the Mirror Replication Agent is used to control the marking or unmarking of a table or procedure (commands pdb_setreptable, pdb_setrepproc), the timing for when the marking or unmarking takes affect is based on the approximate end of the transaction log at the time the Mirror Replication Agent command is executed. Because of the approximate determination, the commands should not be used to control precise marking or unmarking of activity in the second or sub-second time frame.

Workaround: Allow time to elapse (seconds) before assuming the related marking or unmarking command has taken effect.

Known issues for Oracle

This section describes known issues in Mirror Replication Agent 15.2 that are specific to Oracle.

ROWID relationship in the primary and replicate or standby database

[CR #565698] When Sybase identifies support for replicating the ROWID datatype, the value replicated always represents the value that was stored in the table in the primary database and has no relationship to the ROWID values in the standby or replicate database. There is no attempt to convert or adjust that value to match the replicate or standby database.

Workaround: None.

Cannot identify a partitioned table defined in encrypted tablespace

[CR #565564] When trying to mark a table with a partition defined in an encrypted tablespace, Replication Agent cannot identify this type of table and so does not allow it to be marked using the pdb_setreptable mark command.

Workaround: None.

Mirror Replication Agent does not support LOB in ETS and SecureFiles

[CR #564730] Mirror Replication Agent does not support LOBs in Encrypted Table Space (ETS) or defined as SecureFiles, and, if you attempt to mark an encrypted table for replication, the command fails. If you subsequently alter an existing table and change it to ETS or SecureFiles, Mirror Replication Agent does not detect it.

Workaround: None.

Mirror Replication Agent does not recognize non-encrypted tables that follow encrypted tables

[CR #563463] If the first table modified by a transaction is stored in an encrypted table space and subsequent table modifications for the same transaction occur against non-encrypted tables, the Mirror Replication Agent neither recognizes nor replicates the subsequent non-encrypted operations.This is an issue only when the first operation is for an encrypted table. If the operation against the encrypted table is not the first, only the encrypted operation is ignored. All prior and subsequent non-encrypted operations are processed.

Workaround: None.

Mirror Replication Agent fails with an error during table redefinition

[CR #563430] In Oracle 11g, during table redefinition, Mirror Replication Agent goes to ADMIN state with an IteratorException error. In Oracle 10g, after a table redefinition, all DML commands against the source table fails to replicate to the replicate site, as Mirror Replication Agent sends an incorrect table name in LTL, which causes the DSI to go down.

Workaround: None.

Replication Server and Mirror Replication Agent do not update metadata when a schema changes

[CR #545932] The Mirror Replication Agent caches a copy of the table-level replication definition that it reads from Replication Server so does not know when a replication definition has been changed in Replication Server.

Workaround: If you have changed a table-level replication definition in Replication Server, suspend and resume replication in the Mirror Replication Agent, to ensure that the Mirror Replication Agent clears and refreshes its cache.

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 when a table that contains a column with a UDD object type that was created after initialization and before replication was resumed.

Workaround: Resume replication, wait, and mark the table again.

create table DDL has limited support for UDD object types

[CR# 405207] User-defined datatype (UDD) object types with nested object types are not supported for create table DDL commands.

Workaround: Reinitialize the Mirror Replication Agent.

alter type data definition language (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: Reinitialize the Mirror Replication Agent.

Disabling the recyclebin in Oracle 10.1

The Oracle “recyclebin” configuration property was not added until Oracle 10.2 and is available in Oracle 11g. To disable the recycle bin in Oracle 10.1, set the Oracle hidden property:



Documentation updates and clarifications

This section describes changes made to the Mirror Replication Agent documentation.

Replication Agent Primary Database Guide

[CR #568178] Add the following to the Mirror Replication Agent Primary Database Guide, Chapter 2, “Replication Agent for Oracle,” immediately following the section titled “Oracle large object (LOB) support.”

Replicating CLOB and NCLOB datatypes

Oracle NCLOB (National Character Large Object) is a datatype that stores large character data using a multibyte national character set. Similarly, the CLOB datatype may also store character data using a multi-byte national character set, when the Oracle database is defined with a double-byte or variable-width character set.By default, the byte order of the multi-byte characters stored in the NCLOB datatype (and CLOB when the database is defined with a double-byte or variable-width character set) is converted during replication to big-endian byte order. This allows the data to be transmitted over networks using big-endian order, which is the common network byte order.The datatype in a replication definition for an NCLOB or CLOB should be unitext. This prevents Replication Server from attempting character set conversion on the data. If the Replication Server version does not support unitext (Replication Server version 12.6 and earlier) use the image datatype.If the target database that is to receive this NCLOB or CLOB data is installed on a little-endian platform, the database may not automatically convert the replicated data from the sent big-endian order to the little-endian order. To support replicating NCLOB or CLOB data to a database server that does not provide the necessary conversion from big-endian (network order) to little-endian, force the byte order to be sent by the Replication Agent using the lr_ntext_byte_order parameter by specifying a value of big (for big-endian) or little (for little-endian).The lr_ntext_byte_order parameter is available for Oracle, and is important for replication between two different database types and between databases that reside on different operating systems. For example, to replicate data stored in the big-endian byte order at the primary database to a replicate database that stores data in the little-endian byte order, set the lr_ntext_byte_order parameter to little to force Replication Agent to convert the data to the little-endian byte order. Before starting replication, determine the byte order expected by the replicate database and set the lr_ntext_byte_order parameter accordingly. When replication occurs between Oracle and Oracle using CLOB data (and the primary database is defined with a double-byte or variable-width character set), the CLOB data will contain multi-byte national character sets and is replicated. For ECDA for Oracle to correctly apply this data, set the ECDA configuration property rep_unitext to “1”. This configuration in ECDA for Oracle instructs ECDA to tell Oracle the incoming CLOB data is in multi-byte format.

Note:The default behavior of Replication Agent for Oracle is to force any Unicode data to big-endian order as defined by the ltl_big_endian_unitext configuration parameter. To allow the lr_ntext_byte_order configuration parameter to successfully override the Oracle byte order, you must also set the ltl_big_endian_unitext configuration parameter to false, whenever the lr_ntext_byte_order parameter is used.

The ltl_big_endian_unitext parameter specifies whether unitext data should be converted from little-endian to big-endian before sending LTL to the Replication Server. Valid values are true and false. When setting this parameter, you must know how lr_ntext_byte_order is set. If lr_ntext_byte_order is set to send the correct byte order for the replicate database, ltl_big_endian_unitext must be set to false so that the byte order is not changed. ltl_big_endian_unitext parameter is true, by default. The ltl_big_endian_unitext and lr_ntext_byte_order configuration parameters have differences:

lr_ntext_byte_order forces the result of Unicode data that is read from the transaction log to be in the correct byte order, regardless of how it normally exists in the transaction log file.

Replication Agent Reference Manual

(CR #566163) Correct the syntax for the pdb_setrepproc command in Chapter 2, “Command Reference,” in the Syntax section:


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.


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

  1. Point your Web browser to Technical Documents.

  2. Click Certification Report.

  3. In the Certification Report filter select a product, platform, and time frame and then click Go.

  4. Click a Certification Report title to display the report.

Finding the latest information on component certifications

  1. Point your Web browser to Availability and Certification Reports.

  2. Either select the product family and product under Search by Base Product; or select the platform and product under Search by Platform.

  3. Select Search to display the availability and certification report for the selection.

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

  1. Point your Web browser to Technical Documents.

  2. Click MySybase and create a MySybase profile.

Sybase EBFs and software maintenance

Finding the latest information on EBFs and software maintenance

  1. Point your Web browser to the Sybase Support Page.

  2. Select EBFs/Maintenance. If prompted, enter your MySybase user name and password.

  3. Select a product.

  4. Specify a time frame and click Go. A list of EBF/Maintenance releases is displayed.

    Padlock icons indicate that you do not have download authorization for certain EBF/Maintenance releases because you are not registered as a Technical Support Contact. If you have not registered, but have valid information provided by your Sybase representative or through your support contract, click Edit Roles to add the “Technical Support Contact” role to your MySybase profile.

  5. Click the Info icon to display the EBF/Maintenance report, or click the product description to download the software.


Accessibility features

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.

Mirror Replication Agent 15.2 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.

For a section 508 compliance statement for Mirror Replication Agent, go to the Voluntary Product Assessment Template

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.

Back to Top
© Copyright 2010, Sybase Inc.