Howto Trace Clientside Applications on OCI Level On Windows
(Doc ID 749498.1)
Last updated on AUGUST 04, 2018
Applies to:Oracle Database - Enterprise Edition - Version 22.214.171.124 and later
Microsoft Windows (32-bit)
***Checked for relevance on 2nd Aug 2016***
To describe how to trace client side OCI calls to the Full Client "oraclient[X].dll" or Instant Client "oraociei[X].dll" or library. Since almost all client applications implemented in OCI uses these two libraries (directly or indirectly), this may help in trouble-shooting and debugging applications on Windows. This note also provides an example on how Microsoft Debugging Tools for Windows can be customized to provide Oracle specific information.
The Oracle Call Interface is an application programming interface used by a large number of client side interfaces, for example:
- Oracle JDBC-OCI Driver (JDBC/OCI)
- Oracle Precompilers (PROC/PROCOB)
- Oracle Data Provider for .Net (ODP.NET)
- Oracle Provider for OLE DB (OLEDB)
- Oracle Objects for OLE (OO4O)
- Oracle ODBC Driver (ODBC)
An application using the Oracle Call Interface can either link with oci.dll that indirectly links to the oraclient[X].dll or oraociei[X].dll libraries, or link directly to these two libraries depending if Full or Instant Client is used. The tracing will work regardless how the application is linked.
This approach to trace OCI calls is based on the Microsoft Debugging Tools for Windows. A debugger script is generated that adds breakpoints on the entry points for the OCI calls and writes the function calls and parameters to a log file. The debugger is invoked by the AdPlus tool.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!
In this Document