E1: UPG: AS400 Platform - CCSID Errors - OS400QL009 Error - "SQL0332 - Character conversion between CCSID &1 and CCSID &2 not valid"
(Doc ID 638855.1)
Last updated on APRIL 03, 2024
Applies to:
JD Edwards EnterpriseOne Tools - Version SP24 and laterIBM i on POWER Systems
Symptoms
Scenario 1 - Hexadecimal Characters Appearing after Upgrade
Customer upgrading from EnterpriseOne Xe to 8.10 application release level. About 25% of Table Conversions failed. Re-ran them locally and they completed successfully. Receiving errors in the AS/400 job log as follows:
Customer gets this error whenever they try to run a UBE on the server. Also, when they view an Address Book record in P01012, under Mailing Tab the State, Postal Code and Country Code show hex values, not data. If data is viewed however via UTB, all data looks good. This also happens in most of customer's applications like Vendor Master. Seems like they are mostly related to any field that has a UDC attached. Customer actually came from a coexistent environment with World software A73 and Xe, they ended coexistence and then upgraded to a higher E1 application release level.
Scenario 2 - UDCs not been displayed after Upgrade - SQL0332 / OS400QL009 / JDB9900401 Errors
Customer upgraded to EnterpriseOne 9.0 application release level. They have installed E9 on an IBM iSeries machine and successfully run through an upgrade plan, followed by a full client/server package build. They then handed the system over to the users for surface testing, but when users go to add a Journal Entry for example, the UDCs are not displaying. They found CCSID errors when doing a select on the F0004 table. Customer checked the datasources and found that the "Control Tables - PROD" was set to Unicode. They changed this to non-unicode (as they have not yet performed the Unicode conversion on the Enterprise server) and restarted the JDE services but still getting the same error. When looking on the IBM iSeries machine , they see the following errors in the AS400 joblog :
"SQL 0332 - Character conversion between CCSID 13488 and CCSID 65535 not valid."
Customer has changed the JDE user profile to CCSID 37 but still getting the same error. And they can see the data in the F0004 table through the backend. They would like to know which CCSID to use to fix this issue.
The following errors are found in the jde.log for the Call Object Kernel:
ICU0000017 - ICU CodePage for 37 is ibm-37.
2628/3 SYS:Dispatch Mon Jul 4 12:54:06.738072 jdekdisp.c2197
INITIALIZING CALL OBJECT KERNEL
2628/3 SYS:Dispatch Mon Jul 4 12:54:07.490376 jdekdisp.c2284
KNT0000888 - Call Object Kernel Thread Pool in multi-threaded mode.
2628/3 SYS:Dispatch Mon Jul 4 12:54:07.490664 jdekdisp.c2291
KNT0000999 - Call Object Kernel Thread Pool Setting: size 20, increment 5
2628/3 SYS:Dispatch Mon Jul 4 12:54:07.492120 perfmon.c212
E1PerfMon turned off in the INI file.
2628/6 WRK:JDE_80000000_P0911 Mon Jul 4 12:55:23.712296 dbdrv_log.c196
OS400QL009 - OpenSQLCursor:Open SQL cursor: Crsr37. QSQLMSG *LIBL - SQL0332 - Character conversion between CCSID &1 and CCSID &2 not valid
2628/6 WRK:JDE_80000000_P0911 Mon Jul 4 12:55:23.712624 jdb_drvm.c1143
JDB9900401 - Failed to execute db request
2628/8 WRK:JDE_80000000_P0005S Mon Jul 4 12:55:36.491152 dbdrv_log.c196
OS400QL009 - OpenSQLCursor:Open SQL cursor: Crsr38. QSQLMSG *LIBL - SQL0332 - Character conversion between CCSID &1 and CCSID &2 not valid
2628/8 WRK:JDE_80000000_P0005S Mon Jul 4 12:55:36.491496 jdb_drvm.c1143
JDB9900401 - Failed to execute db request
Cause
To view full details, sign in with your My Oracle Support account. |
|
Don't have a My Oracle Support account? Click to get started! |
In this Document
| Symptoms |
| Scenario 1 - Hexadecimal Characters Appearing after Upgrade |
| Scenario 2 - UDCs not been displayed after Upgrade - SQL0332 / OS400QL009 / JDB9900401 Errors |
| Cause |
| Solution |
| Solution for Scenario 1 |
| Solution for Scenario 2 |
| References |