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

Community

feature/enhancement request for native HVR support of Oracle character set JA16EUC (Oracle Charset ID 830).

Naresh Kumar Grandi User

Which connector?:Oracle

 

Additional details:

Summary

HVR 6.3.5/3 currently fails to connect to Oracle source databases using the JA16EUC character set. HVR correctly detects Charset ID 830 during the location test, attempts to reconnect with `NLS_LANG=AMERICAN_AMERICA.JA16EUC`, and then fails because HVR's internal character-set lookup map does not include ID 830:
 
```
F_JD5E07 Oracle charset ID '830' ... is not supported.
F_JT145A The previous error occurred while reconnecting to Oracle with a new setting of $NLS_LANG (AMERICAN_AMERICA.JA16EUC).
```
 

Business Impact

  • The affected source is a production Oracle system (TNS: `ttcy:1521/T70RD01S`).
  • JA16EUC is a standard, valid Japanese Oracle character set already listed among supported encodings for standard Fivetran Oracle connectors.
  • Changing the source database character set is not feasible in a production environment, so this blocks replication of these Oracle sources via HVR.

Validation Performed

  • Oracle Client 19c installed and loaded correctly (`ORACLE_HOME=/fivetran/Oraclient/client19c`).
  • Direct SQLPlus connectivity succeeds using `export NLS_LANG=AMERICAN_AMERICA.JA16EUC`.
  • Network, TNS resolution, and credentials (`SRV_FHVRREPL`) all validated successfully.
  • Failure occurs only during the HVR location connection test — confirming this is an HVR internal charset-mapping gap, not an Oracle/client/environment issue.

Requested Enhancement

  1. Add native support for Oracle Charset ID 830 (JA16EUC) to HVR's internal character-set lookup/encoding map.
  2. Alternatively, provide a supported mechanism to force HVR to use UTF8 / AL32UTF8 translation at the Oracle client layer for such sources.
  3. Please confirm whether any existing HVR version, patch, hotfix, or private build already supports Charset ID 830, and if so, the minimum required version.
 
 

Please sign in to leave a comment.

Comments

0 comments