Negative OBJ# in Solaris Trace files?
- From: Norman Dunbar <oracle@xxxxxxxxxxxxxxx>
- To: oracle-l@xxxxxxxxxxxxx
- Date: Tue, 03 Jan 2012 17:28:28 +0000
I've been shown a trace file created on "64 bit Sun, Oracle 18.104.22.168". In it are WAIT (Sorry Cary, SYSCALLS) where the OBJ~ numbers are negative but not -1. For example: WAIT #18446741324892415968: nam='SQL*Net message from client' ela= 845 driver id=1413697536 #bytes=1 p3=0 obj#=-40016363 tim=32135481352379 WAIT #18446741324892415968: nam='SQL*Net message to client' ela= 2 driver id=1413697536 #bytes=1 p3=0 obj#=115287 tim=32135503128935 These were separated by a FETCH call. As far as I'm aware and can find out, the OBJ# should be -1 when Oracle was not acting on a particular object - and all "message to/from client" WAITs that I've seen are indeed -1. Anyone know what's happening? Google doesn't seem to know either, but if you point me at any known docs, I'll be grateful. Thanks. Cheers, Norm. -- Norman Dunbar Dunbar IT Consultants Ltd Registered address: Thorpe House 61 Richardshaw Lane Pudsey West Yorkshire United Kingdom LS28 7EL Company Number: 05132767 -- http://www.freelists.org/webpage/oracle-l
Other related posts:
- » Negative OBJ# in Solaris Trace files? - Norman Dunbar