Skip to main content
Announcements
Have questions about Qlik Connect? Join us live on April 10th, at 11 AM ET: SIGN UP NOW

Qlik Replicate and Oracle Endpoint: Cannot get a 'max_string_size' parameter. Using STANDARD 'max_string_size'

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
OritA
Support
Support

Qlik Replicate and Oracle Endpoint: Cannot get a 'max_string_size' parameter. Using STANDARD 'max_string_size'

Last Update:

Oct 7, 2022 4:37:38 AM

Updated By:

Sonja_Bauernfeind

Created date:

Oct 7, 2022 4:14:06 AM

When working with Qlik Replicate using an Oracle endpoint, you may see the following message in the Qlik Replicate log:

Cannot get a 'max_string_size' parameter. Using STANDARD 'max_string_size'

 

Environment:

Qlik Replicate 
Oracle Endpoint

 

Prior to Oracle 12c, regardless of the character semantics used, the maximum size of a VARCHAR2, NVARCHAR2 and RAW columns in a database were as follows:

  • VARCHAR2: 4000 bytes
  • NVARCHAR2: 4000 bytes
  • RAW: 2000 bytes


With the introduction of Extended Data Types, Oracle 12c optionally increases these maximum sizes:

  • VARCHAR2: 32767 bytes
  • NVARCHAR2: 32767 bytes
  • RAW: 32767 byte

Note: These figures are in bytes, not characters. The total number of characters that can be stored will depend on the character sets being used.


The message Cannot get a 'max_string_size' parameter. Using STANDARD 'max_string_size' usually appears when Oracle 'max_string_size' is not set to EXTENDED or when it is not set to any value. In this case, it is using STANDARD, and Qlik Replicate will display the above message in the log.

You may confirm that by running the following SELECT against the Oracle DB:

SELECT name, value
FROM v$parameter
WHERE name = 'max_string_size'

 

Related Content:

How to analyze a Qlik Replicate log 

Tags (1)
Labels (1)
Version history
Last update:
‎2022-10-07 04:37 AM
Updated by: