Results for “xs_diag_int”
50+ results
AI-generated from documented ETRM metadata — verify critical details on the linked pages.
Overview
XS_DIAG_INT is a SYS-owned PL/SQL package that forms part of Oracle's internal diagnostic framework supporting the eXtensible Security (XS) subsystem used by Oracle E-Business Suite. In Oracle EBS 12.1.1 and 12.2.2, this diagnostic layer underpins the security model that governs access to administrative schemas, audit records, and other sensitive dictionary objects. XS_DIAG_INT functions as the internal implementation ("INT") companion to the public XS_DIAG package, encapsulating the low-level logic that the external diagnostic interface exposes to callers. Its status is documented as VALID, confirming the package body compiles correctly in the reference environment and that its procedures are callable without recompilation.
The business function of XS_DIAG_INT is therefore not to support a functional EBS module directly, but to sustain the integrity and observability of the security infrastructure that all EBS applications depend upon. Because it belongs to the XS diagnostic family, it is principally invoked during troubleshooting, health checks, and self-service diagnostics executed on behalf of Oracle Support, allowing defects in the security configuration to be identified and reported reliably.
Key Procedures and Functions
The ETRM metadata for this object documents no public procedures or functions; the documented procedure/function count is zero. This is consistent with the "_INT" suffix convention, which denotes an internal implementation package whose callable units are deliberately excluded from the published interface catalog. The package is classified under API classification OTHER, indicating that it is not a supported public application programming interface and should not be called directly by customer extensions.
The documented dependency on SYS.STANDARD confirms that the package body relies only on the base PL/SQL runtime constructs, and the dependency on XS_ADMIN_UTIL indicates that it delegates utility operations — such as logging, privilege verification, or administrative helper routines — to the shared XS administration utility package. Any diagnostic logic present in XS_DIAG_INT is thus assembled from those primitives rather than from bespoke code.
Tables Accessed
No tables are documented as being accessed through APPS synonyms, which is expected for a security diagnostic package operating in the SYS schema. Any data manipulation performed by XS_DIAG_INT is directed at dictionary and XS internal objects that are not exposed through the APPS synonym layer. Consequently, the package should be regarded as a consumer of security metadata rather than a reader or writer of application data tables.
Usage Notes
XS_DIAG_INT is referenced by exactly one other package, SYS.XS_DIAG, and additionally by itself, consistent with a hierarchical relationship in which the public diagnostic package calls down into the internal implementation. The documented dependency direction shows XS_DIAG_INT referencing SYS.STANDARD and XS_ADMIN_UTIL, and being referenced by SYS.XS_DIAG.
- Invocation normally occurs indirectly, when an administrator or Oracle Support engineer runs XS diagnostic actions through the XS_DIAG interface.
- It may be exercised during EBS patching, cloning, or post-upgrade validation, where the security configuration must be verified before the environment is released for use.
- Direct calls from custom EBS code, forms personalizations, or concurrent programs are not supported, because the package is undocumented and internal to SYS.
- Because the package is owned by SYS and marked OTHER, customers should treat it as read-only infrastructure and confine any investigation to tracing its execution rather than modifying it.
In summary, XS_DIAG_INT is a supporting element of the Oracle EBS security diagnostics stack, valuable for understanding how the XS subsystem reports its own state, but neither documented nor intended for direct application use.
-
PACKAGE: SYS.XS_DIAG_INT 12.1.1
-
PACKAGE: SYS.XS_DIAG_INT 12.2.2
-
PACKAGE: SYS.XS_DIAG_INT 12.1.1
-
PACKAGE BODY: SYS.XS_DIAG 12.1.1
-
PACKAGE: SYS.XS_DIAG_INT 12.2.2
-
PACKAGE: SYS.XS_DIAG 12.1.1
-
PACKAGE: SYS.XS_DIAG 12.2.2
-
PACKAGE BODY: SYS.XS_DIAG 12.2.2
-
TABLE: SYS.XS$PROXY_ROLE 12.1.1
-
TABLE: SYS.XS$ROLESET 12.1.1
-
TABLE: SYS.XS$INSTSET_INH 12.2.2
-
TABLE: SYS.XS$ACE_PRIV 12.1.1
-
TABLE: SYS.XS$ATTR_SEC 12.2.2
-
TABLE: SYS.XS$POLICY_PARAM 12.2.2
-
PACKAGE: SYS.DBMS_RANDOM 12.1.1
-
TABLE: SYS.XS$ACL_PARAM 12.2.2
-
TABLE: SYS.XS$INSTSET_LIST 12.2.2
-
TABLE: SYS.XS$SECCLS 12.2.2
-
TABLE: SYS.XS$NSTMPL 12.1.1
-
TABLE: SYS.XS$INSTSET_ACL 12.1.1
-
PACKAGE: SYS.DBMS_RANDOM 12.2.2
-
TABLE: SYS.XS$ACE 12.2.2
-
TABLE: SYS.XS$SECCLS_H 12.1.1
-
TABLE: SYS.XS$SECCLS_H 12.2.2
-
TABLE: SYS.XS$ROLESET_ROLES 12.1.1
-
TABLE: SYS.XS$ACL 12.2.2
-
TABLE: SYS.XS$POLICY_PARAM 12.1.1
-
TABLE: SYS.XS$ROLESET 12.2.2
-
TABLE: SYS.XS$ATTR_SEC 12.1.1
-
TABLE: SYS.XS$AGGR_PRIV 12.2.2
-
TABLE: SYS.XS$INSTSET_ACL 12.2.2
-
TABLE: SYS.XS$ACL_PARAM 12.1.1
-
TABLE: SYS.XS$INSTSET_LIST 12.1.1
-
TABLE: SYS.XS$INSTSET_RULE 12.1.1
-
TABLE: SYS.XS$INSTSET_INH 12.1.1
-
TABLE: SYS.XS$DSEC 12.2.2