Skip to main content

Transformation type

In the Transformation type step of the New Transformation Rule wizard, you define the type of transformation you want to be performed.

Information note

You can only create one rule for each transformation type on the same object (e.g. a column). If you create multiple rules for a single transformation type on the same object, only the last rule you create will be valid. For example, if you create the following rules (in order) to rename a schema:

Rename Schema: Add Prefix

Rename Schema: Add Suffix

OR

Rename Column: Add Prefix

Rename Column: Add Suffix

Only the second rule (adding a suffix) will be executed.

  1. Enter a name for the rule.

    The name cannot exceed 32 characters, contain non-Latin characters, or contain any of the following characters: \/:*?"<>|

  2. Select one of the following:

    Table or Schema:

    • Rename schema: Select this to change the schema name for multiple tables. For example, if you want all HR tables to be renamed PERS.
    • Rename table: Select this to change the name of multiple tables. For example, if you want all tables named SALARY to be called WAGES.

    Tablespace:

    • Change table tablespace: Select this to change the table tablespace on the target. You can change the table tablespace regardless of what objects it contains or you can specify a condition for it to be renamed. For example, change all table tablespaces that contain the table Employees in the schema Company.

      By default (i.e. when this option is not selected), the tables will either be created in the source table tablespace on the target (when replicating from an Oracle source) or in the default database tablespace (when replicating from any other source).

      Information note

      This option is only available for tasks with an Oracle target endpoint.

    • Change index tablespace: Select this to change the index tablespace on the target. You can change the index tablespace regardless of what objects it contains or you can specify a condition for it to be renamed. For example, change all table tablespaces that contain the table Employees in the schema Company.

      By default (i.e. when this option is not selected), the indexes will either be created in the source table tablespace on the target (when replicating from an Oracle source) or in the default database tablespace (when replicating from any other source).

      Information note

      This option is only available for tasks with an Oracle target endpoint.

    Column:

    • Rename column: Select this to change the name of multiple columns. For example, if you want to change all columns with word MINIMUM to MIN.
    • Add column: Select this to add a column with a similar name to multiple tables.
    • Drop column: Select this to drop a column with a similar name from multiple tables.
    • Convert data type: Select this if you want to change a specific data type to a different one across multiple tables. For example, if you want to change all Integer data types to a string.
    • Replace column data: Select this to replace column data across multiple target tables.
    Warning note

    In homogeneous replication tasks (such as Oracle to Oracle), modifying a single table column (by changing the column data type or length for example), will break the homogeneity for the entire table.

    Change Table:

    Change Table transformations are only available when the Store Changes replication option is enabled.

    For more information on Change Tables, see Using Change Tables.

    • Rename Change Table: Select this to rename the Replicate Change Table for all tables or for any table that matches the specified schema name and/or table name.
    • Rename Change Table schema: Select this to change the schema under which the Replicate Change Table will be created, for all tables or for any table that matches the specified schema name and/or table name.
  3. Click Next to proceed to the Transformation scope step.

Did this page help you?

If you find any issues with this page or its content – a typo, a missing step, or a technical error – let us know how we can improve!