topic Re: Limitations and considerations (Oracle) in Qlik Replicate

Limitations and considerations (Oracle)

epanosian — Thu, 06 Jan 2022 14:28:32 GMT

Hello,

With reference to 'Limitations and considerations' >> Object names exceeding 30 characters are not supported. Consequently, tables with names exceeding 30 characters or tables containing column names exceeding 30 characters will not be replicated'. We get 'table .... cannot be captured because it contains column with too long name (more than 30 bytes)'

Any suggestions to bypass this? how others solve the issue.

Reducing the size is not an option.

thank you,

Estifan

Re: Limitations and considerations (Oracle)

Heinvandenheuvel — Thu, 06 Jan 2022 14:49:20 GMT

This old (13 months?) Topic 'suddenly' popped up - possibly moved to a different forum or having received labels?

This may be version dependent, both Oracle and Replicate. Which Replicate version is being used?

Oracle used to only support 30 byte names. As of Oracle Database 12.2, the maximum length of names increased to 128 bytes (provided compatible is set to 12.2 or higher).

Apparently that's being used. - and not yet supported in the version of Replicate you are using.

If you are using a recent (Nov 2021) Replicate version then a formal functionality request to support this is appropriate.

>> Reducing the size is not an option.

It always is, but it may be more work than one is willing to invest.

Perhaps a VIEW van be used as workaround? Either rename the base table and its columns and add a view to present the old names to the source DB users, or add a view on the base table with shortened column names and Replicate that view, not the base table ?

Hein.

Re: Limitations and considerations (Oracle)

john_wang — Thu, 06 Jan 2022 15:17:43 GMT

Hello @epanosian copy @Heinvandenheuvel ,

Maybe the internal parameter skipValidationLongNames helps. You may add it to the source endpoint and set its value to true (default is false).

Regards,

John.

Re: Limitations and considerations (Oracle)

epanosian — Thu, 06 Jan 2022 15:20:19 GMT

Our installed version is May 2021 (2021.5.0.1133).

Reducing the sizes: technically, yes, possible, but from 'amount of work (database, application,...)' it is not an easy task.

View: needs administration work, any changes in the base table, view needs update..

Probably the best is to upgrade to Nov. 2021 version (assuming as you mentioned it will solve the issue) .

thank you..

Re: Limitations and considerations (Oracle)

Heinvandenheuvel — Thu, 06 Jan 2022 16:07:56 GMT

>> Nov. 2021 version (assuming as you mentioned it will solve the issue)

I did not indicate it would be fixed, only that it should be tried there.

I just did a limited test and it does not appear to work in that version either. Full-load works fine. CDC does not.

Message:

[METADATA_MANAGE ]W: Table 'ATT_USER.TEST' cannot be captured because it contains column with too long name (more than 30 bytes)

twice, and

[SOURCE_UNLOAD ]W: Table 'ATT_USER.TEST' cannot be captured because it contains column ABCDEFGHIJKLMNOPQRSTUVWXYZ_SKIPVALIDATIONLONGNAMES with too long name 50 bytes (more than 30 bytes)

Adding internal parameter "skipValidationLongNames " changes the behavior, the SOURCE_UNLOAD warning and one of the METADATA_MANAGE messages is gone, but it still does not appear to make CDC work for that table, no updates, no inserts beyond the initial load.

fwiw,

Hein

Re: Limitations and considerations (Oracle)

epanosian — Mon, 10 Jan 2022 18:47:04 GMT

skipValidationLongNames solved the issue.. warning is gone, CDC works too..