Search Results unset_native_compiler_option

Overview

SYS.DBMS_JAVA is the core PL/SQL interface through which the Oracle database manages its embedded Java virtual machine, its Aurora/ORB runtime, and — most relevant to Oracle E-Business Suite administrators — the native compilation of Java classes and methods stored in the database. In the EBS 12.1.1 and 12.2.2 architectures, the application tier relies on database-resident Java (for example, the Oracle XML Publisher, Workflow Java classes, and various EBS Java-based utilities). DBMS_JAVA provides the DBA and developer-facing entry points used to compile, uncompile, inspect, and tune those Java objects. The package is owned by SYS and is classified as OTHER within the ETRM repository, with 103 documented procedures and functions. It is heavily referenced throughout the EBS stack — the ETRM metadata records nine other packages that depend on it — which reflects its role as a foundational service rather than an application-specific API. The package body wraps many operations as thin pass-throughs to DBMS_JAVA_DEFINERS and to Java classes such as oracle.aurora.perf.OracleBTL.

Key Procedures and Functions

• START_BTL, STOP_BTL, TERMINATE_BTL, INIT_BTL — Manage the Oracle Benchmark Tool Library (BTL) used to collect performance data during Java execution.
• COMPILE_CLASS, COMPILE_METHOD — Invoke the native compiler on a stored Java class or method. The body resolves the current schema via SYS_CONTEXT('userenv','current_schema') and delegates to DBMS_JAVA_DEFINERS.
• UNCOMPILE_CLASS, UNCOMPILE_METHOD — Reverse compilation, with overloads accepting an explicit schema and a permanent flag.
• SET_NATIVE_COMPILER_OPTION — Specifies compiler options (for example optimization flags) applied when Java classes are natively compiled. This is the object referenced in the user search.
• NATIVE_COMPILER_OPTIONS, DECODE_NATIVE_COMPILER_OPTION, UNSET_NATIVE_COMPILER_OPTION, GET_COMPILER_OPTION, SET_COMPILER_OPTION, RESET_COMPILER_OPTION — Retrieve, decode, set, and clear compiler configuration values.
• DUMP_NATIVE_MACHINE_CODE — Emits the generated native machine code for diagnostic inspection.
• LONGNAME, SHORTNAME, RESOLVER, DERIVEDFROM — Utility functions for name mapping, class resolution, and inheritance checks.

Tables Accessed

The ETRM metadata does not document any base tables accessed directly by DBMS_JAVA through APPS synonyms. The package operates against the Oracle Java data dictionary objects maintained by the RDBMS — principally the JAVA$ class and method metadata and the Aurora/native-compiler internal structures — rather than against EBS application tables. Its effects are therefore observed in the state of stored Java objects, not in EBS transactional or setup data.

Usage Notes

SYS.DBMS_JAVA is typically invoked from SQL*Plus or from custom PL/SQL during EBS patching, cloning, and performance tuning. Typical scenarios include recompiling invalid Java classes after applying an EBS patch, clearing native compiler options before applying a Java-based patch, and using COMPILE_CLASS/COMPILE_METHOD to force recompilation when EBS Java-dependent features (for example, XML Publisher or Workflow mailer) fail. Because the package is owned by SYS, it should not be modified. Grant the necessary Java system privileges (for example, via DBMS_JAVA.GRANT_PERMISSION) before calling into these routines, and avoid running native compiler option changes while concurrent Java-based EBS processes are active.