Expected datatype translations do not occur

The most common reason for a datatype translation failure is an incomplete installation of the necessary user-defined datatypes (UDDs) and translations.

StepsValidating UDD and translation installation

  1. Restart the Replication Servers. Replication Server caches all function-string information at start-up.

    Subsequent changes to the function strings stored in the RSSD do not take effect until the Replication Server is restarted.

  2. Verify that class-level translations have been applied to the replicate Replication Server.

    The Replication Server connection profile provides the SQL statements necessary to apply class-level translations to the RSSD of the replicate Replication Server for a specific combination of non-ASE primary databases to non-ASE replicate databases.

    NoteThe connection profile is required for any non-ASE replicate database. For example, if you are replicating from ASE to Oracle, the rs_ase_to_oracle connection profile for translations must be applied to ensure Replication Server updates to the rs_lastcommit table are properly translated and applied to the replicate database.

    You can re-run these connection profiles without failure. Verify that your copy of the connection profiles has been updated with the correct use statement for the database name of the RSSD.

  3. Verify that your replicate database Replication Server connection is associated with the appropriate function-string class.

    To take advantage of class-level translations, the replicate Replication Server connection must use the correct non-ASE function-string class.

    You can use the Replication Server rs_helpdb command to determine which function-string class is defined for a database connection.

    Function-string classes for replicate databases are:

    • Adaptive Server Enterprise – rs_sqlserver_function_class

    • DB2 UDB on IBM z/OS platforms – rs_db2_function_class

    • DB2 UDB on UNIX and Windows platforms – rs_udb_function_class

    • Microsoft SQL Server – rs_msss_function_class

    • Oracle – rs_oracle_function_class

    Use the Replication Server admin show_function_classes command to display a list of active function-string classes.

    Use the Replication Server alter connection command to change the function-string class of an existing database connection.

  4. Verify that the non-ASE function-string classes have been updated with appropriate function strings.

    Replication Server connection profile rs_xxx_xxx provides the SQL statements necessary to apply function strings to the RSSD of the replicate Replication Server for a specific non-ASE replicate database.

    For each function string, the connection profile issue a delete followed by an insert. You can re-run these connection profiles without failure.

    Verify that your copy of the connection profile has been updated with the correct use statement for the database name of the RSSD.

  5. Use the Replication Server admin translate command.

    The admin translate command allows you to verify the results of a specific translation. Use this command to verify that the translation engine is providing the translation results you expect.

    For more information about heterogeneous datatype support (HDS) and the admin translate command, refer to the Replication Server Administration Guide.