Search Results get_admin_list

Overview

SYS.DBMS_EPGC is the Embedded PL/SQL Gateway (EPG) configuration package shipped with the Oracle Database and exposed within the Oracle E-Business Suite 12.1.1 and 12.2.2 technology stack. The EPG is the database-resident HTTP listener that allows PL/SQL stored procedures to be invoked directly over HTTP without a separate mid-tier such as Oracle HTTP Server or Apache mod_plsql. DBMS_EPGC provides the administrative API used to create, configure, secure, and remove the gateway instances, Database Access Descriptors (DADs), and administrative users that govern this embedded listener.

The package is declared AUTHID CURRENT_USER, meaning its routines execute with the privileges of the calling schema rather than the definer, and it is owned by SYS. In an EBS context, DBMS_EPGC is rarely part of the functional application flow; it is an infrastructure and administration utility used by DBAs and system administrators who need to expose or secure PL/SQL endpoints at the database tier. It defines a private VARCHAR2_TABLE type for returning lists of attributes and DAD names, and a set of named exceptions — including config_error, user_already_exists, invalid_port, invalid_username, not_an_admin, and privilege_error — each mapped to a specific Oracle error number via PRAGMA EXCEPTION_INIT to give callers precise, catchable error semantics.

Key Procedures and Functions

The documented interface exposes twenty-three routines grouped by administrative purpose.

• Instance management: CREATE_INSTANCE establishes a gateway instance bound to a specified port; DROP_INSTANCE removes a single instance; DROP_ALL_INSTANCES removes every defined instance.
• Administrator management: GRANT_ADMIN and REVOKE_ADMIN add or remove administrative privileges for a user on a gateway instance; GET_ADMIN_LIST returns the current administrators.
• Global attribute management: SET_GLOBAL_ATTRIBUTE, GET_GLOBAL_ATTRIBUTE, DELETE_GLOBAL_ATTRIBUTE, and GET_ALL_GLOBAL_ATTRIBUTES manage gateway-wide configuration settings such as listener behavior and security defaults.
• DAD management: CREATE_DAD and DROP_DAD define and remove Database Access Descriptors; SET_DAD_ATTRIBUTE, GET_DAD_ATTRIBUTE, DELETE_DAD_ATTRIBUTE, and GET_ALL_DAD_ATTRIBUTES manipulate per-DAD settings; GET_DAD_LIST enumerates the defined descriptors.
• Configuration transport: IMPORT and EXPORT move gateway configuration definitions between databases, supporting cloning and migration.

Tables Accessed

The ETRM metadata records no direct table references for DBMS_EPGC through APPS synonyms. The package operates against the internal EPG repository objects that the database maintains on behalf of the embedded gateway. Because it is a SYS-owned infrastructure package rather than an EBS application API, it does not read or write the standard EBS transactional tables. All persistence is confined to the gateway configuration store.

Usage Notes

DBMS_EPGC is invoked administratively, typically from SQL*Plus or a DBA script, and not from EBS forms or concurrent programs. It is called when an environment requires the embedded PL/SQL gateway to be enabled, when a DAD must be created or re-pointed, when administrative users must be granted or revoked, or when gateway configuration must be exported and imported during cloning. The package is referenced by two other database packages, indicating layered internal dependencies. The exception definitions are significant for callers: configuration failures raise config_error (-20000), duplicate administrators raise user_already_exists (-20001), invalid ports raise invalid_port (-20002), malformed usernames raise invalid_username (-20003), missing privileges raise not_an_admin (-20004), and insufficient administrative rights on a gateway instance raise privilege_error (-20005). Because the package runs AUTHID CURRENT_USER, callers must themselves hold the necessary privileges on the gateway objects. The search string "146.88.24.105:8080" is unrelated to package definition and corresponds to an HTTP listener endpoint address rather than any DBMS_EPGC construct.