Hi Group,

Getting the below error in AIX server 5.2 and my DB2 ESE is V8.1 and
Fixpack 11.

I'm able to successfully connect to the database and able to run a
SELECT query with out any issues..If I run a UPDATE query on a table
which is a part of ETL datastage job..getting the below error:

Error:[IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE =
08003. SQLTransact: Error committing transaction.

Can any one guess what would be the issue and how to resolve this???


Thanks in advance,
vj_dba

vijay.db@gmail.com wrote:

> Hi Group,
>
> Getting the below error in AIX server 5.2 and my DB2 ESE is V8.1 and
> Fixpack 11.
>
> I'm able to successfully connect to the database and able to run a
> SELECT query with out any issues..If I run a UPDATE query on a table
> which is a part of ETL datastage job..getting the below error:
>
> Error:[IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE =
> 08003. SQLTransact: Error committing transaction.
>
> Can any one guess what would be the issue and how to resolve this???

I would say that you shouldn't close your connection. If you don't do that
(or think you don't), verify this:
- are you using the correct environment, database, and statement handles?
- is no other thread using the connection handle and closes it?
- collect a CLI trace and search for the above error. Then scan back to
find some information about the statement/connection handle.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany

On Feb 9, 1:47 am, Knut Stolze <sto...@de.ibm.com> wrote:
> vijay...@gmail.com wrote:
> > Hi Group,
>
> > Getting the below error in AIX server 5.2 and my DB2 ESE is V8.1 and
> > Fixpack 11.
>
> > I'm able to successfully connect to the database and able to run a
> > SELECT query with out any issues..If I run a UPDATE query on a table
> > which is a part of ETL datastage job..getting the below error:
>
> > Error:[IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE =
> > 08003. SQLTransact: Error committing transaction.
>
> > Can any one guess what would be the issue and how to resolve this???
>
> I would say that you shouldn't close your connection. If you don't do that
> (or think you don't), verify this:
> - are you using the correct environment, database, and statement handles?
> - is no other thread using the connection handle and closes it?
> - collect a CLI trace and search for the above error. Then scan back to
> find some information about the statement/connection handle.
>
> --
> Knut Stolze
> DB2 z/OS Utilities Development
> IBM Germany

Hi Knut many thanks for the help...can you pls put your views on
enabling CLI trace...

I tested the below in a Windows server..I created a trace folder in C:/
temp and gave full control privilege to it. Then I manually edited the
db2cli.ini file in the instance sqllib directory with the following
entry:

SCHEMALIST='ADMIN','CURRENT SQLID'
DBALIAS=test

[sample]
DBALIAS=TEST


[COMMON]

Trace=1
TracePathName=C:\temp\trace
TraceComm=1
TraceFlush=1
TraceTimeStamp=1
TraceScript=1

then I performed a Import SQL statement of putting more rows to the
table...though the trace is ON..not able to see any entries in the
trace file location...

kindly advice how and where to use the CLI trace facility..

Thanks in advance,
vj_dba

vijay.db@gmail.com wrote:

> On Feb 9, 1:47 am, Knut Stolze <sto...@de.ibm.com> wrote:
>> vijay...@gmail.com wrote:
>> > Hi Group,
>>
>> > Getting the below error in AIX server 5.2 and my DB2 ESE is V8.1 and
>> > Fixpack 11.
>>
>> > I'm able to successfully connect to the database and able to run a
>> > SELECT query with out any issues..If I run a UPDATE query on a table
>> > which is a part of ETL datastage job..getting the below error:
>>
>> > Error:[IBM][CLI Driver] CLI0106E Connection is closed. SQLSTATE =
>> > 08003. SQLTransact: Error committing transaction.
>>
>> > Can any one guess what would be the issue and how to resolve this???
>>
>> I would say that you shouldn't close your connection. If you don't do
>> that (or think you don't), verify this:
>> - are you using the correct environment, database, and statement handles?
>> - is no other thread using the connection handle and closes it?
>> - collect a CLI trace and search for the above error. Then scan back to
>> find some information about the statement/connection handle.
>>
>> --
>> Knut Stolze
>> DB2 z/OS Utilities Development
>> IBM Germany
>
> Hi Knut many thanks for the help...can you pls put your views on
> enabling CLI trace...

I would recommend that you use the UPDATE CLI CFG command.

--
Knut Stolze
DB2 z/OS Utilities Development
IBM Germany