Skip to main content
Docs
Feature Requests Onboarding Trust Center Status Page

Community

Connector Improvement: Connector Improvement: Request to handle more then 30 chars in schema and object names for HVA oracle connector

Answered
Reuben Gerald User

Hello Team, We recently faced an issue where the HVA oracle connector in fivetran  failed when the DBA created a schema/user more then 30 bytes. The only way to recover was to ask the DBA to drop that schema. Later we came to know that this is not supported by Fivetran. Since oracle databases after 12c allow to extend object names to 128 bytes, could you please implement the change so that fivetran can handle the same.

Also, for the timebeing to make a change so that fivetran HVA oracle connector doesnt have to fail when it encounters such schemas, rather i would prefer it skips and processes for others as a normal process.

Please sign in to leave a comment.

Comments

2 comments

Date Votes
  • Official comment
    Nathan Fuzi User

    Hi Reuben Gerald,

    Thank you for using our feature request portal to submit your query. We appreciate your interest in our HVA Oracle connector. Unfortunately, Oracle has restricted supplemental logging of objects with long identifier names (schema names, table names, and column names) such that changes to these objects cannot be read from the redo logs as they can for names that are 30 characters or less. 

    You can read about this in Oracle's documentation at https://docs.oracle.com/en/database/oracle/oracle-database/21/sutil/oracle-logminer-utility.html#GUID-ED46E42D-B412-4820-9753-EBE15F49BA21. This is stated as a limitation of LogMiner, but we can confirm that the supplemental logging is itself affected. We are aware of the initialization parameter ENABLE_GOLDENGATE_REPLICATION (Oracle documentation at https://docs.oracle.com/en/database/oracle/oracle-database/21/refrn/ENABLE_GOLDENGATE_REPLICATION.html), which Oracle explains extends supplemental logging for newer data types and operations. However, setting this parameter on your source database may trigger feature usage and licensing requirements for Oracle GoldenGate. 

    To your point, we should more gracefully fail on syncing those objects or not allow them to be selected for inclusion in your replication set with an explanation that they are unsupported. We will work to improve this experience over the next few months.

  • Ramon Martin User

    We can't wait to have this feature ready. If Oracle supports it why Fivetran connector does not.