iamareplicant
Programmer
OCBC tracing experts,
I have been given a request to use ODBC tracing to try to capture a large number of ODBC connections made to Oracle during our morning batch routines.
When I did a test on one Access database and one of its pass-thru queries, what was captured was not quite what I need. I need the table name(s) used in the call (it showed the sql statment to ORacle but just the select part, not the FROM part) and hopefully the actual app name (that is, I know that Ms access.exe was the platform that used the ODBC connection, but what I need to see in the ODBC log is something like MyDB.mdb to show - tis wa, I can match app to tables in Oracle used).
Is there a way (within standard ODBC tracing or 3 party tool or??) to capture more robust ODBC connection info than what comes with Windows? Help!
Thanks,
JBG
I have been given a request to use ODBC tracing to try to capture a large number of ODBC connections made to Oracle during our morning batch routines.
When I did a test on one Access database and one of its pass-thru queries, what was captured was not quite what I need. I need the table name(s) used in the call (it showed the sql statment to ORacle but just the select part, not the FROM part) and hopefully the actual app name (that is, I know that Ms access.exe was the platform that used the ODBC connection, but what I need to see in the ODBC log is something like MyDB.mdb to show - tis wa, I can match app to tables in Oracle used).
Is there a way (within standard ODBC tracing or 3 party tool or??) to capture more robust ODBC connection info than what comes with Windows? Help!
Thanks,
JBG