Database Administration (MOSC)

MOSC Banner

Usage of NLS_LENGTH_SEMANTICS=CHAR for PDB - recommended?

edited Jan 8, 2021 12:50PM in Database Administration (MOSC) 1 commentAnswered

Hi Community,

We have a database migration project from PostreSQL to Oracle 19c (not kidding). As it turns out PostreSQL's UTF8 seems not like to be equal to Oracle's AL32UTF8 settings. So we found out, that when we change the NLS_LENGTH_SEMANTICS parameter in the PDB from BYTE to CHAR the mirgration works. The CDB and other PDBs are still on BYTE parameter.

After reading the documentation regarding NLS_LENGTH_SEMANTICS (https://docs.oracle.com/en/database/oracle/oracle-database/19/nlspg/setting-up-globalization-support-environment.html#GUID-C0306672-8501-4D73-BDAC-5FC19ED6C4EB) where it is noted that you need to be careful changing this parameter, I am wondering if we still have to consider this.

Howdy, Stranger!

Log In

To view full details, sign in to My Oracle Support Community.

Register

Don't have a My Oracle Support Community account? Click here to get started.

Category Leaderboard

Top contributors this month

Instructions for posting

×

1. Select a discussion category from the picklist.


2. Enter a title that clearly identifies the subject of your question.


3. In the body, insert detailed information, including Oracle product and version.


Please abide by the Oracle Community guidelines and refrain from posting any customer or personally identifiable information (PI/CI).


Cloud / Fusion customers - Our Cloud community has moved! Please go to Cloud Customer Connect .


New to My Oracle Support Community? Visit our Welcome Center

MOSC Help Center