Show TOC

admin translateLocate this document in the navigation structure

Performs a datatype translation on a value, displaying the results in delimited literal format.

Syntax
admin translate, <value>, <source_datatype>, <target_datatype>
Parameters
value

The literal representation of the value that is to be translated.

source_datatype

The name of a datatype (either a Replication Server native datatype or a datatype definition that describes the content and format of <value>).

target_datatype

The name of a datatype (either a Replication Server base datatype or a datatype definition that is the requested output for the translation).

Examples
Example 1

This examples translates the DB2 <TIMESTAMP> value ‘1999-06-22-14.35.23.123456’ to the Oracle <DATE> value ‘22-Jan-99.’

admin translate, '1999-06-22-14.35.23.123456',
rs_db2_timestamp, rs_oracle_date
Example 2

This example translates the Adaptive Server binary value 0x1122aabb to the Oracle binary value ‘1122aabb.’

admin translate, 0x1122aabb, 'binary(4)',
        'rs_oracle_binary(4)'
Usage
  • Delimit <value> according to the delimitation requirements of the base datatype of the source datatype.

  • If <source_datatype> or <target_datatype> requires a length specification, for example <char(255)>, enclose the datatype name in single quotes.

  • The source and target datatypes may differ depending on whether you want to test class-level or column-level translations. Thus:
    • For class-level translations – use the published datatype for <source_datatype>.

    • For column-level datatypes – use the declared datatype for <source_datatype> and the published datatype for <target_datatype>.

  • Use admin translate with the diagnostic version of Replication Server to trace errors in translations.

  • For information about supported datatype translations, see the Replication Server Heterogeneous Replication Guide. For information about translating datatypes using heterogeneous datatype support (HDS), see the Replication Server Administration Guide Volume 1.

Permissions

Any user may execute this command.