Re: tracing question

Hey Chris,
why not tracing all data, putting it into the SQL trace facility and then query or aggregate based on your needs: https://docs.oracle.com/database/121/TGSQL/tgsql_trace.htm#TGSQL834

... or you can also use profilers that only consider / filter SQLs with a depth=0. However be careful - if the SQLs (no matter if INSERTs, UPDATEs, DELETEs or SELECTs) are run by PL/SQL procedure or functions - they are also considered as recursive statements.

Best Regards
Stefan Koehler

Freelance Oracle performance consultant and researcher Homepage: http://www.soocs.de
Twitter: _at_OracleSK  

> Chris King <dmarc-noreply_at_freelists.org> hat am 15. Juli 2016 um 14:35 geschrieben:
>
> Following up on Debra's question.. I'm wondering if it's possible to set tracing to list ONLY the user's commands issued, and not include all the
> internal parsing. I'm aware of the method of writing a trigger to record insert/update/delete statements into a table, but I also need to know what
> select statements the user is issuing. When setting tracing on in a session, there's a lot of internal information to get thru, and it isn't clear
> to me which are the user issued commands.
>
>
> >>>
> I’m working thru this issue with vendor software now. The application installation requires a schema, and there are scripts to run to pre-create
> the schema.. so it seems it should not be necessary to grant DBA privileges. I’ve decided to put tracing/auditing on to see what the application
> user is trying to do when it connects, and maybe this way, can grant just the privileges needed instead of DBA.
>
> If anyone has done this before and is willing to share their scripts, etc. please contact me? Or post URL
>
> Thank you.

--
http://www.freelists.org/webpage/oracle-l