Thats what I thought. But here is more details on the issue..
 
I am running a SQL*PLus session with a massive query that returns about 2.5g of data, i am spooling the data to file - that is something similar to what the essbase application is trying to do.
 
that session spooled the data in around 2 hours - so the access paths are fine. after getting the data though, my sql session has still not completed. from the size of the spool file i can see the data came more then three hours ago. this session is still doing something and these waits are increasnig and sql is not returning the SQL prompt to me...
 
trying to find out why...
 
babu
----- Original Message -----
Sent: Wednesday, April 10, 2002 2:52 PM
Subject: RE: PX Deq: Table Q qref

Looks like you have PQ enabled.
These waits are considered idle.
The PQ slave processes are waiting for work to do.
 
- Kirti 
-----Original Message-----
From: Babu Nagarajan [mailto:[EMAIL PROTECTED]]
Sent: Wednesday, April 10, 2002 12:51 PM
To: Multiple recipients of list ORACLE-L
Subject: PX Deq: Table Q qref

All
 
What does this wait event mean? I have a process that connects to the database through ODBC and this process is waiting on this event and SQL*Net message from client.
 
Often this process waits for an unreasonable amout of time (40000 seconds or more) on SQL*Net MEssage from client and PX Deq: Table Q qref before it successfully completes...
 
TIA
 
Babu

Reply via email to