Re: Control File Sequential Read - top wait

Ok; control files are not the first; you have attacked OMLET use of shared cursors set to FORCE. My answer was and still eat sh** and shut up; because there may be may be someone who knows slightly more than you.

Well let me make another bet: Do you know what you have in common with opiosq, opicca, opiexe, opifch or kernel calls kkspsc, kksumc, kkspfx, kkspin?

the first four are the dicks that banged you shared azz; the last four are the ones that banged your mother cusorit.

Actually sharing such a shared objects
- requires shared lock;

• creation of a kgl object;
• pinning the name's object heap zero in shared mode
  • might require checking if there is some context area that could be used by this dick, by pinning the child objects, one by one, and seeing if are also fuckable or usable.
    • release the pin locks
• pin the parent heap zero in exclusive mode, create new child marked as not bind-qualified; lock the child kglob in breakable shared mode, release the parent pin lock, parse; release the pin lock and object lock on the child
• bind all bind variables
• pin parent heap zero in shared mode; check all matching children by pinning their heap zero to see if any is fuckable or reusable byu this dick.

do the above till your mother cursorit is willing and dripping; lock it in breakable-share mode.

on every dip, pin in S mode; do cleanups; if the dick slips signal an error if mid-fetch;

keep doing this till you and your mama scream.

Woho; what an overhead with this crappy PLSQL (untyped)

Or of course you can set cursor sharing to force and gang bang the hookers!

Disclaimer: This is not related to any product whatsoever; all names are fictional and do not relate to any real life objects Received on Sun Jul 25 2004 - 05:56:43 CDT