Chris Thanks for sharing the info But when u are waiting on a latch free on shared pool dont u think there should be an sql_address to it. When a session is active, in the sense that he has a transaction then i thought he should have an sql_addresss, but based on the below information u can see that there is no sql_address nor hash value. this is what is bugging me sid username sql_address event ------------------------------------ 7507 ODSAPP 00 latch: library cache SID SQL_ADDRESS SQL_HASH_VALUE EVENT TADDR ----- ---------------- -------------- ----------------------------------- ---------------- 5408 00 0 latch: shared pool C00000057511FC78 --- Christian Antognini <Christian.Antognini@xxxxxxxxxxxx> wrote: > Arun > > >I am querying the v$session to get the sql_address > of > >some sessions who are generating high redo.but > before > >even going there i am seeing this weird output from > >v$session where there is no value in sql_address > and > >henceforth i cannot know what sql these sessions > are > >running. > > According to the fine manual SQL_ADDRESS is "Used > with SQL_HASH_VALUE to identify the SQL statement > that is currently being executed". Since those > sessions are not executing a SQL statement, but > waiting on the client, this is the expected > behavior. > > HTH > Chris > > New Features Oracle Database 10g Release 2 seminars > @ www.trivadis.com > Italiano: Lugano (24-Nov) > Français: Genève (17-Nov) > Deutsch: Hamburg (13-Oct), München (20-Oct), Basel > (25-Oct), Frankfurt (27-Oct), > Zürich (29-Nov), Bern (8-Nov), Düsseldorf > (23-Nov), Stuttgart (13-Dec) > __________________________________________________________ Yahoo! India Matrimony: Find your partner now. Go to http://yahoo.shaadi.com -- //www.freelists.org/webpage/oracle-l