"Oracle strongly recommends that you do NOT set the NLS_LENGTH_SEMANTICS parameter to CHAR in the instance or server parameter file. This may cause many existing installation scripts to unexpectedly create columns with character length semantics, resulting in run-time errors, including buffer overflows."
Can you advise firstly on the appropriate way to define CHAR length semantics.
Secondly is installation with default BYTE semantics supported by Pega?
***Edited by Moderator: Pooja Gadige to change category from Product to Upgrade***
Pega recommends setting the default length semantic as CHAR supports international character sets.
As mentioned it the upgrade document, you can also choose to set it at session level before applying any DDL or ask your DBA to set it up at session level to ensures that all sessions use CHAR semantic.
Or, You can always use CHAR keyword to VARCHAR2(n CHAR) and CHAR(n CHAR) declarations to make them independent from the SP File semantic setting.
If the NLS_LENGTH_SEMANTICS is set to BYTE, then a column declared as VARCHAR2(10) or CHAR(10) would be interpreted as 10 bytes, if it is set to CHAR then the columns would be interpreted as 10 characters. You may run into issues where you have special characters that exceed the specified column length in bytes. Please refer the links below to understand more.