HVR log-based capture from Oracle fails with error F_JT4600 when a table contains a column name longer than 30 characters, unless ENABLE_GOLDENGATE_REPLICATION=TRUE is set on the source database. We would like HVR to support these tables without depending on this parameter.

Current behaviour: When we added a new table to an HVR channel, Activate failed with:

F_JT4600: The column 'wfs_group_location_manager_user_id' of the table 'osswfm.wfs_group_location_manager_user' is longer than 30 symbols. It is necessary to have the parameter 'enable_goldengate_replication' set to 'TRUE' on the capture location in order to capture data correctly from such a table.

Fivetran Support confirmed (ticket #418695) that this comes from Oracle supplemental logging behaviour. Right now there are only three workarounds:

1. Set ENABLE_GOLDENGATE_REPLICATION=TRUE on the source database (this requires the appropriate Oracle licensing)
2. Rename the column to 30 characters or fewer
3. Exclude the table from the channel

Why the workarounds are not practical:

• Licensing: We use HVR, not Oracle GoldenGate. We would have to justify extra Oracle licensing just to enable a GoldenGate parameter for a non-GoldenGate product.
• Renaming columns: This is usually not possible on production application schemas owned by third-party vendors or application teams.
• Excluding tables: The data never reaches the destination, so the replication is incomplete.

Since Oracle 12.2, identifiers can be up to 128 bytes long, so column names over 30 characters will keep getting more common in modern application schemas.

Comparison with other CDC tools: In another Oracle environment, a different CDC tool (Quest SharePlex) replicates tables with column names over 30 characters while ENABLE_GOLDENGATE_REPLICATION is set to FALSE. This suggests that capturing these tables without the parameter may be technically feasible.

Requested enhancement:

• Allow HVR to capture tables with column names longer than 30 characters without requiring ENABLE_GOLDENGATE_REPLICATION=TRUE, for example through an alternative capture or metadata-resolution method for affected tables.
• If a full solution is not possible, add a pre-check that lists all affected tables and columns before Activate, rather than failing during activation.
• Document the limitation and the licensing implications clearly on the Oracle source requirements page.

Reference: Fivetran Support ticket #418695