Migrating ORACLE Db wat UTF-8 with AE at V21.0.9 - need help to verify/test DB consistency

[PROSENJIT MAJI]

Hello Experts, Good day!! 

Current AE Version      : 21.0.9+hf.1.build.1706176060310
AE is running on           : Red Hat Enterprise Linux release 8.10

We wanted to avoid V21 to V24 & UTF database migration together so staying at AE V21, we are trying to migrating our ORACLE DB to UTF8. 

We have copied our DEV system DB schema & imported into another NEW UTF8 DB without using Broadcom tools. 
We started the AE without any change in the ucsrv.ini ( except the NEW ORACLE service name ) 

Here are the parameters from the UTF8 DB ( from DB table NLS_DATABASE_PARAMETERS ) :
NLS_NCHAR_CHARACTERSET=UTF8
NLS_CHARACTERSET=AL32UTF8 

Here is the UC_SYSTEM_SETTINGS parameters (after logging in to AE client 0 that is using UTF8 DB) :
XML_ENCODING=ISO-8859-15
SERVER_OPTIONS=NNNMNNNNNN5NNP

Here are the parameter from ucsrv.ini
SP=NLS_LANGUAGE=AMERICAN,
NLS_TERRITORY=AMERICA,CODESET=WE8ISO8859P1
sqlDriverConnect=ODBCVAR=NNJNIORO

Sample jobs are running fine but before moving further, we wanted to check the data consistency after migrating from NON-UTF to UTF8 Database. 

It will be very helpful if anyone have a checklist which already provided by Broadcom. 
OR please feel free to share your observation if anyone has done it already. 

Any comments/suggestion/comments would be a great help !!   

------------------------------
Regards,
Prosenjit
------------------------------

[Josef Scharl]

Hello,

we have tested a similar scenario but used Broadcom's tool "UTF-8 DB Migration Action Pack" for the migration.
After that we just kept the NLS settings in ucsrv.ini same as before:
... SP=NLS_LANGUAGE=AMERICAN,NLS_TERRITORY=AMERICA,CODESET=WE8ISO8859P1,NLS_LENGTH_SEMANTICS=CHAR

And continued running all UC4 components with version 21.0.

Later we updated the UC4 components with version 24.0 and changed sqlDriverConnect to:
… SP=NLS_LANGUAGE=AMERICAN,NLS_TERRITORY=AMERICA,CODESET=AL32UTF8

So far it worked, and we didn't find any issue with the encoding. However getting a "OK" form the vendor would be great.

KR, Josef

[Josef Scharl]

PS: At the DB we have this:
U00003535 DB INFO: 'NLS_NCHAR_CHARACTERSET         = AL16UTF16'
U00003535 DB INFO: 'NLS_CHARACTERSET               = AL32UTF8'