Windows trace file weirdness
Date: Mon, 13 Mar 2017 14:11:22 +0000
Message-ID: <D8FB4A72-7909-4B33-8A73-48B2ACC6E306_at_dunbar-it.co.uk>
I'm looking through a trace file on a Windows server, running 11204.
I'm seeing quite a few CLOSE #CURSOR_ID with DEP=0 for cursors that were opened at a different depths. I can see, for example, that the PARSING IN CURSOR and the following PARSE have depth 1, but the following close has depth zero. There's nothing in between other than EXEC, WAIT & STAT lines for the cursor.
Other cursors have the correct depth on the close and it matches the depth at parse time.
I see nothing on MOS regarding this. Has anyone seen anything similar? Or knows of any bugs?
It's driving me bonkers as in addition to my suffering, my trace mining utility TraceMiner2, (https://github.com/NormanDunbar/TraceMiner2) is also suffering from confusion over this, and needs some working around the problem. Sigh.
Cheers,
Norm.
--
Sent from my Android device with K-9 Mail. Please excuse my brevity.
--
http://www.freelists.org/webpage/oracle-l
Received on Mon Mar 13 2017 - 15:11:22 CET