Hi all, I think I've got a solution, thanks to Carsten for the hint: STATSPACK tables have a MODULE field. Setting the module is the software's duty in usual cases, like SQL Developer and so on does. But anyone can set it on a session basis: exec DBMS_APPLICATION_INFO.SET_MODULE('This is user: '|| USER, 'doing useless stuff'); (first argument is the module, the second one is the action) Since I am at a centralized database (in use for our development), it was easy to combine it with a global logon trigger and enjoy much more useful statspack repots from that day on. Thanks a lot for all replies and thoughts. -- Mit freundlichem Gruß Martin Klier |------------> | Von: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Martin Klier <usn@xxxxxxxxx> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | An: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Oracle-L Group <oracle-l@xxxxxxxxxxxxx> | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Datum: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |19.06.2009 10:39 | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Betreff: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |Re: SQL History in Statspack: Parsing schema? | >--------------------------------------------------------------------------------------------------------------------------------------------------| |------------> | Gesendet | | von: | |------------> >--------------------------------------------------------------------------------------------------------------------------------------------------| |oracle-l-bounce@xxxxxxxxxxxxx | >--------------------------------------------------------------------------------------------------------------------------------------------------| CORRIGENDA: of course it's stats$sql_summary and stats$sqltext, not sql_status Sorry. Martin Klier schrieb: > Dear list, > > I am using statspack in a 10gR2 database to collect and display SQL > history. It's selected from stats$sql_status and stats$sql_summary. > > Now my question: How can I find out, which schema did parse there SQLs? > I can't find a column with a speaking information, did I miss anything > obvious? > > Thanks a lot in advance! -- Usn's IT Blog for Linux, Oracle, Asterisk http://www.usn-it.de -- //www.freelists.org/webpage/oracle-l -- //www.freelists.org/webpage/oracle-l