DB2Look Bug?

DB2Look Bug?

 

  

Hi Folks, I am running UDB V8 fixpack 10 on AIX 5.3. I have an interesting
problem and wonder if anyone has ran into a similar situation.

When I run "db2look -d department -l -e -o db2look.sql" to retrieve
tablespace DDL it takes too long as it also retrieves dependent object
information. By hitting ctrl+c I expect the process to simply terminate.
Well apparently the process is terminated but the DB2 agent remains active
and it holds locks in the catalog indefinitely until the agent is identified
and killed. Unfortunately it caused a back log on one of our QAS systems and
I'd like to avoid the situation in the future.

Appreciate any feedback you may have.

Ivan


DB2 & UDB email list listserv db2-l LazyDBA home page