Known Issues for Oracle

When the Replication Agent processes records with LOB for tables with partition by hash on Oracle 11.1 for HPIA64 and Windows platforms, this exception error is encountered:

Could not mine or match a RAW LogMiner record for record <...Operation <UNSUPPORTED> ... SQL Redo <Unsupported> > from SCN [<xxx>, <xxx>].>

Workaround: None.

Replication Server fails to load the Enterprise Connect for Oracle (ECO) library files on Windows x86 32-bit system due to missing Microsoft Visual C++ 2005 Service Pack 1 Redistributable Package MFC security update.

Workaround: Download and install the Microsoft Visual C++ 2005 security update:

http://www.microsoft.com/en-us/download/details.aspx?id=26347

Unable to support Oracle SecureFile LOB for all platforms.

Workaround: Contact the Sybase Technical Support.

Cannot create connection to Oracle replicate dataserver when tnsnames.ora file entry has Oracle Transparent Application Failover (TAF) enabled.

Workaround: Remove the "FAILOVER_MODE" entry from the replicate dataserver alias in the tnsnames.ora file.

OracleLogRecordProcessingException error is encountered in Oracle version 11.1.0.6.

When you alter a table with truncate partition in the primary database, where the table is a partitioned table with LOB and sub-parititions, an OracleLogRecordProcessingException error is encountered. This is encountered only in Oracle version 11.1.0.6.

Resume fails because Oracle LogMiner fails to start with start SCN <0>.

Workaround: Resume Replication Agent.

pdb_setrepproc procedure marking execution fails.

Replication Agent for Oracle fails to mark a procedure when the procedure owner (schema) is different than the pds_username user.

pdb_xlog command fails if xlog is created on Oracle 10g, and then recreated on Oracle 11g.

When xlog is created on Oracle 10g, removed, then recreated on Oracle 11g, the pdb_xlog command fails because the xlog remove process does not clear the RASD repository and keeps the installed_pdbver and installed_buildnum in the repository, so the current version is different from the installed_pdbver.

Workaround: None.

The DDL commands that SYS user execute are not filtered.

Workaround: Add SYS user to DDL filters.

IllegalArgumentException error is encountered when processing ANYDATA datatype column that contains an the off-row stored LOB with size larger than 2K.

Workaround: None.

Replication Agent fails to initiate when ra_admin_owner is different from pds_username.

Workaround: Grant dba to the pds_username.

Oracle LogMiner needs support for pdb_thread_filter.

pdb_thread_filter filters all activities in an Oracle instance redo log thread or threads during replication, and displays a list of threads being filtered. Currently, this configuration can be set in 15.7.1, but does not take effect.

Workaround: None.

Unable to put Replication Agent 15.7.1 in replicating mode. The Oracle LogMiner must be installed error is encountered.

The alter table DDL command fails in RepAgent.

In Oracle 10g, when a new column is added to a table with not null and default value, Oracle also updates the existing rows with the default column value. When the update to the existing rows is performed, an exception shows up since RepAgent has not processed the alter table DDL yet, which means it has not updated the article to add the new column. RepAgent has no way to determine whether this is a normal user table update or an internal update that is generated by DDL transaction.

1. Locate the internal update DML log record in the Replication Agent error log with LRTRACE set to on. Example:

   T. 2012/03/25 20:27:12.293 LRTRACE com.sybase.ds.oracle.logmnr.OracleOperationPr Processing LogMiner Record 
   <OPID <0x0000.00bab3a6.0000:0001.00000be3.000000bf.00f0>, Timestamp <2012-03-25 20:27:12.0>, XID <0x0004.002b.00000c39>, 
   Serial# <7528>, Session# <133>, Session Info <login_username=QAMUSER client_info= OS_username=wliao 
   Machine_name=rqavmrh1 OS_terminal= OS_process_id=31314 OS_program_name=dcoracle@rqavmrh1 (TNS V1-V3)>, User Name <QAMUSER>, 
   Object ID <93318>, REL_FILE# <5>, DATA_BLK# <893>, DATA_OBJD#<93318>, Operation <UPDATE>, Op Code <3> Rollback <0> SSN <0> 
   CSF <0> SQL Redo <update "QAMUSER"."QAM_INT" set "FEE_SUB_MNEM_CD" = ' ' where "FEE_MNEM_CD" = 'SYB' and 
   "FEE_TYP_DESC" = 'UNWIRED ENTERPRISE ' and "LST_UPDT_DTTI" = TO_TIMESTAMP('01/02/2009 00:00:00.000000000') and 
   "LST_UPDI_USER_ID" IS NULL and "FEE_SUB_MNEM_CD" IS NULL;> >.

2. Collect SCN, THREAD, and RBA of that update log record, and use pdb_skip_op command to skip it.

   pdb_skip_op add, SCN, THREAD, RBA

3. Resume Replication Agent.

Replication Agent for Oracle (RA) no longer requires direct access to the archive log, unless configured to do non-RMAN truncation since the switch to using Oracle LogMiner.

However, currently, RAO checks during pdb_archive_path configuration and displays error if the archive log is not visible or readable. This prevents you to configure RAO to run from a remote host. The requirement is for RAO to run from a remote host as long as the remote host platform is the same as the source database platform.

Workaround: When Replication Agent and the primary database are not located in the same host, set the pdb_archive_path parameter of Replication Agent to a valid local directory, which matches the actual database archive path on the remote host.

Replication Agent aborts with LTI formatting error.

The Replication Agent is aborted with LTI formatting error on a locator value due to Oracle LogMiner limitation on decimal precision support.

Workaround: None. Please contact Sybase Technical Support.

In Oracle 10g Release 2, if LogMiner uses a dictionary to scan the redo log files, these user-level SQL operations are missing from the V$LOGMNR_CONTENTS view:

• LOB_TRIM
• LOB_WRITE
• SEL_LOB_LOCATOR

Because these operations are used to update off-row XML data, Replication Agent for Oracle cannot replicate the rollback of transactions that use these operations on off-row XML data.

Workaround: None.

Workaround: None.

Oracle LogMiner zeroes out fractional second on timestamp columns.

Replication of millisecond section of timestamp datatype column fails if the primary Oracle version is earlier or equal to 10.2.0.4.

rasd_restore does not shutdown RepAgent instance when run with a parameter.

Workaround: Run rasd_restore without specifying a parameter.

Exadata Hybrid Columnar Compression (EHCC) not supported.

Replication Agent for Oracle does not support the replication of "columnar compressed data because Replication Agent for Oracle does not support Exadata. 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.

DDL statements introduced in Oracle 11g cannot be filtered.

Workaround: None.

Oracle resynchronization limitation.

Replication Agent for Oracle does not support the resynchronization scenario described in the Resynchronizing the Active and Standby Databases in a Warm Standby Application section in the Replication Server Heterogeneous Replication Guide.

Workaround: None.

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.

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

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.

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

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.

Incorrect lr_ntext_byte_order command default value in the output display.

The ra_config lr_ntext_byte_order command output incorrectly displays the default value as "<not_configured>" instead of big.

Workaround:See the Replication Agent Reference Manual for the correct information on this command.

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.

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.

Replicating a sequential update to a primary key column fails.

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;