Greetings,

So far as I have gone through the docs, DGTT has to be dropped explicitly for a remote thread re-use ( pooled).

We will be using few Stored Procedures for reporting ETL from production. Develpment team has asked me to study & test DGTT usage across pooled threads ( connections , agents ).

Can some one correct me if I am wrong. A refrence will be helpful.

Regards

DBFinder
DB2V9.5.5 on Win2003

Not sure what you mean, but a Declared GTT does not have to be dropped, since it is only for that one sesson. But not sure I know exactly what you mean by pooled threads.

In DB2 9.7 there are CGTT (Created) which are created outside of the SP and each session gets its own copy, but the definition stays around in the catalog.

Oh,

Let me explain.

I was refering to pooled connections, applications are remote, the threads go into the pool after it is done, so I used remote thread re-use.

When a DGTT is declared with on commit perserve rows the DGTT will not be dropped when a thread is returned to pool.

Am I right here ?

If so, then we need to drop the DGTT explicitly before a thread is returned to the pool. Is it ??

That's all I mean by above quote.


Regards

You are correct. Otherwise it will stick around for the life of the thread.
Dave