never mind, problem solved by doing a complete removal of all system IPC.
"kw.housing" <kw.housing@[EMAIL PROTECTED]
> wrote in message
news:fut8e3$3fh$1@[EMAIL PROTECTED]
> hi I am using DB2 V9.5 but there is a IM****T transaction that will
> never be able to commit itself.
> Its status is forever "Commit Active", and is taking 12% CPU, and not
> waiting on any lock.
>
> The transactions is set table to not logged initially, im****t all data,
> then commit. It hangs on the last
> "commit" command.
>
>
> I did a db2pd -edu and saw it is running as follows:
>
> EDU ID TID Kernel TID EDU Name USR SYS
>
====================================================================================================
> 3086 3086 635527 db2agent (DB) 1 263.196480
> 2.164422
>
> Then I saw from db2pd -agent that it is using process 287150,
>
> ddress AppHandl [nod-index] AgentEDUID Priority Type
> State ClientPid Userid ClientNm Rowsread Rowswrtn LkTmOt
> 0x078000000024ACC0 65594 [001-00058] 3086 0 Coord
> Inst-Active 287150 user1 db2bp 345 0 NotSet
>
>
> so I do a truss on it:
>
> $ truss -p 287150
> __semop(0, 0x0000000000000000, 0) (sleeping...)
>
> so what is this semaphore about, and how could i fix it? thanks.
>
>
>
|
