EBS / RDBMS -- 19C Upgrade -- Post Upgrade fails due to missing jar (orai18n.jar) in classpath

Upgrading an EBS RAC Database to 19C (RU 12 & OJVM 12) requires the MOS note "Using Oracle 19c RAC Multitenant (Single PDB) with Oracle E-Business Suite Release 12.1 (Doc ID 2530680.1)" to be followed, and there you will do lots of stuff including the post upgrade tasks... 

Today's issue is encountered while executing the txkPostPDBCreationTasks.pl. ( a post upgrade task actually)

I won't go into the details about the actions that we take for this complex upgrade work (it is complex, because it is EBS! :), but! I will give you the solution that we designed and implemented for getting rid of the following errors in txkPostPDBCreationTasks.pl run;

StackTrace:

java.sql.SQLException: Non supported character set (add orai18n.jar in your classpath): WE8ISO8859P9

at oracle.sql.CharacterSetUnknown.failCharsetUnknown(CharacterSetFactoryThin.java:233)

at oracle.sql.CharacterSetUnknown.convert(CharacterSetFactoryThin.java:194)

at oracle.jdbc.driver.PhysicalConnection.throughDbCharset(PhysicalConnection.java:10425)

at oracle.jdbc.driver.PhysicalConnection.enquoteIdentifier(PhysicalConnection.java:10502)

at oracle.jdbc.driver.OracleStatement.enquoteIdentifier(OracleStatement.java:6452)

at oracle.jdbc.driver.OracleStatement.getColumnIndex(OracleStatement.java:3853)

at oracle.jdbc.driver.InsensitiveScrollableResultSet.findColumn(InsensitiveScrollableResultSet.java:270)

at oracle.apps.ad.autoconfig.RestoreProfile.createRestoreFile(RestoreProfile.java:294)

at oracle.apps.ad.autoconfig.RestoreProfile.generateRestoreScript(RestoreProfile.java:128)

at oracle.apps.ad.autoconfig.AppltopDrivers.main(AppltopDrivers.java:1426)

It is needless to say that, we've already put orai18n.jar in the correct directories, as it is stated in the upgrade documents but here we are, still failing unexpectedly in the post upgrade tasks..

The exact phase that we failed was the autoconfig and the failing script (autoconfig executes a bunch of script to do its work, as you know..) was adgentns.pl (+adconfig.pl).

It  was obvious that the issue was related with the classpath.. classpath that is passed to java.. 

adgentns.pl was failing but adclone.pl was also requiring a change.

So I checked the code ( the perl scripts adgentns.pl and adconfig.pl) and added the ora18in.jar in to the classpaths defined there in those perl scripts.. Those perls script execute java and I modified their classpaths (added ora18in.jar) used for executing those java .. (this action requires some knowledge in perl, bytheway) With this action, the issue was fixed! So we could continue the remaining tasks and finished the upgrade! 

No other solution is available at the moment.. 

This should also be directed to development, right? Ofcourse we did it at by opening a SR. However; we fixed the issue on ourselves and could continue upgrading.

I will revisit this blog post and update it with a patch number.. (probably.. because I think the development will write a fix for it.)