I am looking at a connection to a 32-bit 11.0.1.2405 database that is "stuck", and shows the following connection properties... HeapsLocked 4294967266 HeapsRelocatable 4294967276 Since the largest unsigned integer is 4294967295, those numbers look suspiciously like "hitting a limit". More... Here is a snapshot of a few related properties. Does this prove the connection-level values are bogus? Or is it still possible the connection-level values are valid, indicating some serious problem in the engine? engine... 2010-09-25 03:45:00.092,87,'HeapsLocked','Number of relocatable heaps currently locked in cache','21' 2010-09-25 03:45:00.092,89,'HeapsRelocatable','Number of relocatable heaps','204' 2010-09-25 03:45:00.092,100,'LockedHeapPages','Heap pages locked in cache','2175' connection... 2010-09-25 03:45:00.014,81,87,'HeapsLocked','Number of relocatable heaps currently locked in cache','4294967255' 2010-09-25 03:45:00.014,81,89,'HeapsRelocatable','Number of relocatable heaps','4294967275' |
Looks like I'm going to lose my bet with Nick Elson, where I claimed I could get an answer here first :)
In addition to the BOUNTY, I am offering FREE BEER.
I bet the bounty & beer will go to Waterloo, ON...
As I learned from Bruce Hay, the HeapsLocked should be <= LockedHeapPages. And so they are at least related to the address space/4096 you have available. Having this in mind your numbers look to me more like a free twice, so probably some dereferencing has brought them into the negative range.
@Martin: FWIW LockedHeapPages is not available as a connection-level property. But... that's a moot point, since the engine-level HeapsLocked and HeapsRelocatable values are much smaller than the connection-level values, indicating the later are probably bogus (as Mohammed indicates).