Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
Qlik and ServiceNow Partner to Bring Trusted Enterprise Context into AI-Powered Workflows. Learn More!
cancel
Showing results for 
Search instead for 
Did you mean: 
tjahncke
Contributor
Contributor

30 byte limit on column name

Since Oracle 12.2 128 byte column name is now supported.  When will Qlik replicate support beyond 30 bytes for a column name.  

Labels (1)
3 Replies
Dana_Baldwin
Support
Support

Hi @tjahncke 

Please refer to this community knowledge article on this topic: Replicate - Oracle source: Long Object Names excee... - Qlik Community - 1961484

Thanks,

Dana

aidanor89
Contributor
Contributor

Hey Dana

 

Is there a version of Qlik Replicate that supports this change on Oracle.

I understand it is called out as a limitation on Oracle but is there potentially a change to Qlik in the works to support that change?

 

The only options seem to be the 2 below so if you don't have goldengate license it will be impossible to work around unless you can influence the Oracle dev side. 

(1) Add internal parameter skipValidationLongNames (see above) in endpoint

(2) It also requires a parameter called "enable_goldengate_replication" is enabled in Oracle. This can only be done by end user and their DBA:

 

alter system set ENABLE_GOLDENGATE_REPLICATION=true;

 

Kind regards

Aidan 

Dana_Baldwin
Support
Support

Hi @aidanor89 

No, the issue is on Oracle's side - they only write the longer object names to the redo log when Golden Gate is enabled on the database, which requires a license from them. If it's not in the redo log, Qlik Replicate can't read it.

Thanks,

Dana