| Message: 62578 |
 |
BY: Praveen Devarao (praveend)
DATE: 2008-11-28 12:35
SUBJECT: RE: Problems with connection to iseries DB Hi Francesco,
Yes a strange situation. The reason for SQL30082N error can be found here http://publib.boulder.ibm.com/infocenter/db2luw/v9r5/topic/com.ibm.db2.luw.messages.sql.doc/doc/msql30082n.html . We will need to look in to the CLI trace to know about what is happening. Could you provide us with a CLI trace. Please follow the procedure below to obtain a CLI trace.
Procedure to obtain a CLI trace: -
* Make an environment variable named DB2CLIINIPATH and set it to some directory where your local db2cli.ini will reside.
eg. in bash, issue
export DB2CLIINIPATH=<dir name where the traces will be generated>
On Windows, issue
set DB2CLIINIPATH=<dir name where the traces will be generated>
* issue the following commands ( in windows run these commands in the DB2 command prompt, issue db2cmd for the same)
db2 update cli cfg for section COMMON using trace 1
db2 update cli cfg for section COMMON using tracepathname <dir name where the traces will be generated>
* Local db2cli.ini file should be generated in mentioned directory.
* Run the application. Traces will be generated inside the specified directory.
* To disable the CLI trace issue the following command
db2 update cli cfg for section COMMON using trace 0
Please get us the traces during both the conditions.
Note: - Remember to turn off the trace once done.
Thanks
Praveen
| |
Start New Thread
Problems with connection to iseries DB