Errors running "DB2PackageCreator" program to BIND packages on AS400
(Doc ID 2313487.1)
Last updated on AUGUST 31, 2023
Applies to:
Oracle Database Provider for DRDA - Version 12.1.0.2 and laterLinux x86-64
IBM i on POWER Systems
Symptoms
Get errors running "DB2PackageCreator" program on AS400 (IBM iSeries) which has the ability to BIND packages in the DP4DRDA instance.
The BIND command is:
JAVA CLASS('com.ibm.db2.jdbc.app.DB2PackageCreator')
PARM('PROCDEV' 'DRDAUSR' 'XXXX')
PROP((jdbc.drivers 'com.ibm.as400.access.AS400JDBCDriver'))
Gets BIND errors:
com.ibm.db2.jdbc.app.DB2DBException: COMMIT(*NONE) valid only if relational d
atabase PROCDEV (product identification DSN12020) is DB2 for IBM i. Cause . .
. . . : Commit level of *CHG, *CS or *ALL required when relational databas
e PROCDEV is not another DB2 for IBM i. Recovery . . . : Change the progra
m to use commitment control, then retry the CRTSQLxxx command with a commitme
nt control level of *CHG, *CS, or *ALL specified.
at com.ibm.db2.jdbc.app.DB2SQLException.createDefaultException(DB2SQL
Exception.java:41)
at com.ibm.db2.jdbc.app.DB2SQLException.createException(DB2SQLExcepti
on.java:138)
at com.ibm.db2.jdbc.app.DB2StatementRuntimeImpl.SQLExecDirect(Native
Method)
at com.ibm.db2.jdbc.app.DB2StatementRuntimeImpl.execDirect(DB2Stateme
ntRuntimeImpl.java:195)
at com.ibm.db2.jdbc.app.DB2Statement.commonExecDirect(DB2Statement.ja
va:1347)
at com.ibm.db2.jdbc.app.DB2Statement.executeQuery(DB2Statement.java:1
044)
at com.ibm.db2.jdbc.app.DB2PackageCreator.ensurePackageExists(DB2Pack
ageCreator.java:142)
at com.ibm.db2.jdbc.app.DB2PackageCreator.main(DB2PackageCreator.java
:83)
ERROR: Connection for none not created.
The SQL Package may not exist on system.
Java program completed
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 |
| Cause |
| Solution |
| References |