From: Henrik J. <hp...@gl...> - 2002-09-06 15:32:44
|
The problem might be as simple as this. After an SQL statement has been executed it will only hang around the SGA for a short while (Depending on SGA size etc), after that time it will be dropped. The v$session table still lists the address to the last executed statement even if the statements isn't still in the SGA. This isn't the problem if the session you are looking at is active (Then it is some other reason I can't really figure out right now), but otherwise that's probably it. /Mauritz Underscore AB Don Seiler wrote: >Using the Sessions screen to see what statement a user is running. Most >of the users I click on give me "SQL Address not found in SGA" errors when >I click on the "Current Statement" tab. > >Mainly these are sessions for other windows clients. Other TORA users >show up fine, as do sqlplus users. TOAD users and our home-grown app >users return that error. I haven't done a scientific survey to see if >these are 100% all of the time but so far it's been that way with the >small (10 sessions) I've looked at. > >Any thoughts? > >Don. > > > >------------------------------------------------------- >This sf.net email is sponsored by: OSDN - Tired of that same old >cell phone? Get a new here for FREE! >https://www.inphonic.com/r.asp?r=sourceforge1&refcode1=vs3390 >_______________________________________________ >Tora-develop mailing list >Tor...@li... >https://lists.sourceforge.net/lists/listinfo/tora-develop > > |