The term OCI Debugger does not refer to a single, standalone product. Instead, it points to different debugging tools and features depending on whether you are referring to Oracle Cloud Infrastructure (OCI) or the Open Container Initiative (OCI) container standard.
The primary contexts for “OCI Debugger” and how they work are outlined below: 1. Oracle Cloud Infrastructure (OCI) Functions Debugger
When developing serverless functions on Oracle Cloud, the local Fn Server includes a local debug mode. This eliminates the need to continuously redeploy code to the cloud just to test changes.
How it works: You start the Fn Server in local debug mode, which opens a default debugging port (5678).
Functionality: When you invoke your function, it pauses and waits for you to attach a standard remote debugger (like VS Code, IntelliJ, or JDeveloper). You can then set breakpoints, step through code, and inspect variables.
Supported Languages: Native support is available for Java, Go, and Python functions. 2. Oracle Call Interface (OCI) Database Debuggers
In the context of Oracle Databases, OCI stands for Oracle Call Interface—the low-level C-based API used to connect applications to Oracle databases.
Legacy Tracing Tools: Third-party freeware tools historically named “OCI Debugger” were designed to intercept and trace low-level database SQL queries, estimates, and execution times.
Modern Database Debugging: Today, debugging PL/SQL and database programs over OCI is managed via modern IDEs like the SQL Developer Extension for VS Code or JDeveloper using the Java Debug Wire Protocol (JDWP) over TCP. 3. Open Container Initiative (OCI) Image Debugging
Leave a Reply