Known Issues for Oracle

Learn about known issues and workarounds for Replication Agent that are specific to Oracle.

Replication Agent for Oracle Issues
CR#	Description
650347	Setting ra_direct_read before Replication Agent is initialized results in an error. Workaround: Initialize Replication Agent before you set ra_direct_read. If ra_direct_read cannot be set, check the Replication Agent log for messages. To do this, the Replication Agent administrator that started the Replication Agent instance process must have permission to read the underlying block devices, turn all traces on, and run ra_updatedevices.
645980	Exadata Hybrid Columnar Compression (EHCC) not supported. Replication Agent for Oracle does not support the replication of data compressed with EHCC because the compression algorithm may result in unexpected logging behavior. Do not use the compress for query clause or the compress for archive clause in an Oracle table definition because these clauses are intended only for EHCC data. Workaround: None.
645883	Oracle table compression limitation. Replication Agent for Oracle 15.6 does not support table compression for Oracle 10g. Replication Agent for Oracle 15.6 does not support direct-path inserts—appending data directly to a file, bypassing buffer cache—to Oracle 11g tables that use table compression. In Oracle 11g, if the table has been partitioned and the compress option has been set to compress, compress for all operations, or OLTP, while the data in the table is compressed, updating the table can generate multiple chained operations—operations which act upon the results of a previous operation. Processing these chained operations can cause Replication Agent errors such as failure in parsing Oracle `date` and `timestamp` values, or incorrectly duplicating values. Workaround: None.
641011	DDL statements introduced in Oracle 11g cannot be filtered. pdb_setrepddl does not filter these DDL statements introduced in Oracle 11g: Oracle 11.1 – create flashback archive, alter flashback archive, and drop flashback archive. Oracle 11.2 – alter database link, create edition, and drop edition. Workaround: None.
630089	Oracle resynchronization limitation. Replication Agent for Oracle does not support the resynchronization scenario described in section “Resynchronizing the active and standby databases in a warm standby application,” in Chapter 13, “Resynchronizing Oracle Replicate Databases,” of the Replication Server Heterogeneous Replication Guide. Workaround: None.
624026	Supplemental logging not enabled error. The initialization of the Replication Agent for Oracle can fail with a message that supplemental logging is not enabled even if the supplemental logging requirements specified in the Replication Agent Primary Database Guide are met. This happens when the Replication Agent initialization has already failed because of a disabled supplemental logging configuration before the configuration was corrected. Replication Agent caches the primary database supplemental logging configuration on initial communication with the primary database after start-up, but does not refresh it after a configuration change. Workaround: Shut down and restart Replication Agent after you enable supplemental logging in the primary database.
620157	Database resynchronization feature support. Replication Agent cannot use the Replication Server 15.5 database resynchronization feature. Workaround: To use the database resynchronization feature, install Replication Server 15.5 ESD #1 or later.
619663	Replication Agent reports an incorrect number of RMAN-deleted archive redo log files when RMAN utility locale is not English. Replication Agent searches for the word “Deleted” when counting the number of deleted archive redo log files that have been truncated by the Oracle Recovery Manager (RMAN) utility. For language modules other than English, the count fails because Replication Agent cannot find the word “Deleted.” Workaround: Specify the locale behavior of your Oracle software by setting the NLS_LANG Oracle environment parameter to a supported English character set such as american_america.zhs16gbk. For example: On Windows: `set nls_lang=american_america.zhs16gbk` On UNIX: `setenv NLS_LANG american_america.zhs16gbk`
615023	Replication definition is not created when table owner is not specified. When your primary database is Oracle and the recycle bin is enabled, rs_create_repdef cannot create a replication definition for marked tables unless you specify a table owner. Workaround: Specify a table owner in the rs_create_repdef syntax. For example: rs_create_repdef qaxuser.qax_tab1 where `qaxuser` is the table owner.
596320	Owner information is not supported in function replication definition for Oracle. Replication Server does not support specifying owner information of stored procedures in the function replication definition for Oracle. As such, Replication Agent does not send that information to Replication Server. Because the owner information is not available, the replicated stored procedure fails to execute at the Oracle standby database. Workaround: For each stored procedure replicated from active to standby database, create a corresponding function string that specifies the owner information of the target stored procedure. To alter the function string class of the standby connection to a customized function string class, which is inherited from rs_oracle_function_class: alter connection to `dco2stb.ordb` (standby connection) set function string class to my_oracle_function_class go
585513	Initialization failure when isolation level is set to serializable in an Oracle RAC environment. In an Oracle Real Application Clusters (RAC) environment, Replication Agent may fail during initialization when you set the isolation level to serializable. This failure is due to an internal Oracle error. Workaround: Install the Oracle Clusterware Release 2 (10.2.0.4) patch set for Oracle Database 10g Release 2 or upgrade to Oracle Database 11g Release 1.
562889	Replication Agent fails with an error during table redefinition. In Oracle 11g, during table redefinition, Replication Agent goes to ADMIN state with an IteratorException error. In Oracle 10g, after a table redefinition, all DML commands against the source table fail to replicate to the replicate site as Replication Agent sends an incorrect table name in LTL, which causes the DSI to go down. Workaround: None.
405207	create table DDL has limited support for UDD object types. Replication of a create table DDL command is not supported for tables with UDDs, when a UDD has a nested object type. Workaround: Reinitialize the Replication Agent.
405206	alter type DDL command has limited support. During replication of the alter type command, the type change does not propagate to the dependents of the type. Workaround: Reinitialize the Replication Agent.
397826	Replicating a sequential update to a primary key column fails. For example, this update will not be replicated correctly: update test_table set pkey = pkey + 1 Workaround: Change the primary key column or add a unique index that is more broad.
	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: ALTER SYSTEM SET “_recyclebin”=FALSE SCOPE = BOTH;