Troubleshooting
Problem
SQL0332N error received when executing CLI application using a DB2 Client or Driver from DB2 Version 9.7 fix pack 6 (9.7.0.6), or DB2 Version 9.7 fix pack 5 (9.7.0.5).
Two scenarios may generate this symptom:
1. When connection string passed to SQLDirverConnect() contains an invalid attribute that results only in a warning message CLI004W. The connection to the database would be successful with warning (SUCCESS_WITH_INFO), but several of the DB2 CLI APIs against this database may throw the -332 error further down the application logic. The problem has been seen with SQLGetCursorName() API
2. When attempting to access a DRDA nickname in a Federation Server environment with trusted context connection enabled. Though most of statements that access the nickname would be successful, several of them may fail with the -332 error.
For example:
-DELETE FROM
Symptom
Following is an example of the symptom that may be received:
SQL0332N Character conversion from the source code page "0" to the target code page "1202" is not supported."
Log InLog in to view more of this document
Was this topic helpful?
Document Information
Modified date:
30 April 2025
UID
swg21600269