Known Issues for Replication Agent

Known issues and workarounds for Replication Agent.

Replication Agent Issues
CR#	Description
689941	RepAgent for Adaptive Server handles some of the normalization errors from Replication Server as warnings, which may result in data loss. Workaround: Upgrade to Replication Server 15.7. If you are using a version of Adaptive Server earlier than 15.7, the RepAgent log may show incorrect normalization errors. For example: Column unknown.unknown status 'always_replicate' in replication definition does not match database status 'replicate_if_changed'. Use 'alter replication definition' to set 'replicate_if_changed' status, at least until existing transactions have been processed. (Refer to Troubleshooting Guide for recovery procedures.) See the accurate error information in the Replication Server log. For example: E2011/11/16 09:17:11. ERROR #32057 REP AGENT(ost_replnxb9_32.pdb1) - /nrm/nrm.c(4175) The value given for 'blurbs.copy' cannot be translated from datatype 'text_status' to the required datatype 'varchar'. If you are using a version of Adaptive Server later than 15.7, the RepAgent log shows the correct error information. For example, the RepAgent log shows: 00:0002:00000:00018:2011/11/16 09:17:11.71 server RepAgent(4): Received the following error message from the Replication Server: Msg 32057. The value given for 'blurbs.copy' cannot be translated from datatype 'text_status' to the required datatype 'varchar'.
630089	Replication Agent for Oracle does not support the resynchronization scenario described in the Replication Server Heterogeneous Replication Guide > Oracle Replicate Databases Resynchronization > Database Resynchronization Scenarios Resynchronization topic. Workaround: None.
596321, 596320	Replication Server does not support specifying owner information of stored procedures in the function replication definition for Oracle. Therefore, Replication Agent cannot 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 that is replicated from an active to a standby database, create a corresponding function string. Specify owner information in the target stored procedure. To customize the function-string class of the standby connection, which is inherited from rs_oracle_function_class, enter: alter connection to dco2stb.ordb (standby connection) set function string class to my_oracle_function_class go