Links
• Home
• Oracle DBA Forum
Frequent Oracle Errors
•TNS:could not resolve the connect identifier specified
•Backtrace message unwound by exceptions
•invalid identifier
•PL/SQL compilation error
•internal error
•missing expression
•table or view does not exist
•end-of-file on communication channel
•TNS:listener unknown in connect descriptor
•insufficient privileges
•PL/SQL: numeric or value error string
•TNS:protocol adapter error
•ORACLE not available
•target host or object does not exist
•invalid number
•unable to allocate string bytes of shared memory
•resource busy and acquire with NOWAIT specified
•error occurred at recursive SQL level string
•ORACLE initialization or shutdown in progress
•archiver error. Connect internal only, until freed
•snapshot too old
•unable to extend temp segment by string in tablespace
•Credential retrieval failed
•missing or invalid option
•invalid username/password; logon denied
•unable to create INITIAL extent for segment
•out of process memory when trying to allocate string bytes
•shared memory realm does not exist
•cannot insert NULL
•TNS:unable to connect to destination
•remote database not found'>ora-02019
•exception encountered: core dump
•inconsistent datatypes
•no data found
•TNS:operation timed out
•PL/SQL: could not find program
•existing state of packages has been discarded
•maximum number of processes exceeded
•error signaled in parallel query server
•ORACLE instance terminated. Disconnection forced
•TNS:packet writer failure
•see ORA-12699
•missing right parenthesis
•name is already used by an existing object
•cannot identify/lock data file
•invalid file operation
•quoted string not properly terminated
-none-

-none-

2004-06-09       - By -not available-
Reply:     <<     101     102     103     104     105     106     107     108     109     110     >>  

I THINK:
The low 4 digits is the slave number of the blocker.
(as in Pnnn, not the SID) or FFFF for the query
coordinator.

Somewhere in there, there is a clue about the
wait time - and I think it depends on the top
bit: there is a 'non-contentious ' wait time of
200 centiseconds, (0xC8) and any other time
is a contentious time. (A 'non-contentious '
wait time example: if the QC is reading
an order input from the slaves, the first will be
supplying, and the others will be idling with a
2-second wakeup, awaiting there turn)

So if you can see the slave that 's being wait for,
and a 0xC8 in the high word, then the slave
is twiddling it 's thumbs waiting to be told that
it is time to supply date.


Regards

Jonathan Lewis

http://www.jlcomp.demon.co.uk

http://www.jlcomp.demon.co.uk/faq/ind_faq.html
The Co-operative Oracle Users ' FAQ

http://www.jlcomp.demon.co.uk/seminar.html
Optimising Oracle Seminar - schedule updated May 1st


-- -- Original Message -- --
From: "David Sharples " <dsharples@(protected) >
To: <oracle-l@(protected) >
Sent: Wednesday, June 09, 2004 1:46 PM
Subject: PX Deq wait


Hi, had a little problem today.

Had a process which had been running for over 24 hours (should take
about 15 secs) it was waiting on PX Deq Credit: send blkd.

It was a job which did some inserts, statspack was telling me no i/o was
being done on the objects at all. Is it possible that the parallel
slaves had died so my process never knew it had finished, no trace files
were generated and nothing in the alert log, killing the process and
restarting it fixed it

Is there somewhere else I can look next time to see what has really
happened?

Thanks


-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ------
To unsubscribe send email to: oracle-l-request@(protected)
put 'unsubscribe ' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- ---- --