Search Results get_error_msg

Overview

FND_ADG_EXCEPTION is a utility package shipped with Oracle E-Business Suite releases 12.1.1 and 12.2.2 as part of the Active Data Guard (ADG) support infrastructure. Its purpose is to centralize the definition and raising of errors encountered by the ADG registration, link validation, and remote procedure call (RPC) configuration routines that operate against a physical standby database. The package header declares an extensive set of named constants, each assigned a numeric error code, covering conditions such as an invalid database release (10), a null register link (11), an owner that is not PUBLIC (12), a register link that cannot be found (13), a standby value out of range (14), link host mismatches (15), standby primary link matches (16), RPC system enabled or disabled states (17–18), RPC ADG enabled or disabled states (19–20), inconsistent ADG state (21), directive mismatches (22), invalid connect types (23), null standby values (24), RPC system not prepared (25), and a family of link-check failures (26–34) including TNS, loopback, bad DBID, bad database role, clone detection, bad standby, bad service, and bad system link. Further constants address bad directory objects (35), an undefined registration configuration manager (36), existing configuration data (37), and an over-length connection string (38 and above). The package is compiled with AUTHID CURRENT_USER, and the header comment notes that all errors are currently wrapped in ORA-20001, a wrapper that can be altered by changing this single package. This design isolates error-message formatting from the many ADG callers.

Key Procedures and Functions

• RAISE_ERROR — Raises an application error corresponding to one of the package's error constants. Callers pass the constant that identifies the specific ADG failure condition, and the routine emits the error using the standard convention (currently ORA-20001) so that the message reaches the calling session in a consistent form.
• GET_ERROR_MSG — Returns the message text associated with a given ADG error code or condition. This function is the canonical way for ADG-related code, diagnostics, and support tooling to translate the numeric constants defined in the package header into human-readable text without duplicating message lookups. This is the object most commonly sought by users searching for "get_error_msg," since it provides the readable counterpart to the raised ORA-20001 errors.

Tables Accessed

The documented table reference for this package is APPS.PLITBLM, an Oracle Applications synonym that maps to the underlying PL/SQL message table owned by the FND schema. Both RAISE_ERROR and GET_ERROR_MSG rely on this table to store and retrieve the message text keyed by application and message name. No other application tables are recorded as dependencies, which is consistent with the package's narrow role as an error-handling helper rather than a business-logic unit.

Usage Notes

FND_ADG_EXCEPTION is an internal support package and is not exposed through a user-facing form or a standalone concurrent program. It is invoked indirectly by the ADG utility packages, link-check packages, and RPC configuration routines that perform standby database validation in an EBS environment. ETRM records that it is referenced by four other packages, confirming that its constants and message retrieval function form a shared vocabulary among the ADG components. Customizations rarely call it directly; when they do, the usual pattern is to invoke RAISE_ERROR with an appropriate constant or to call GET_ERROR_MSG to surface an ADG-related message in a custom log or diagnostic report. Because message text is resolved through PLITBLM, any administrative change to message definitions in that table is reflected automatically at runtime. The AUTHID CURRENT_USER setting means the package executes with the privileges of the invoking schema, so callers must have the necessary grants on the underlying message table for error reporting to succeed.