Search Results get_instance
Overview
SYS.DBMS_HA_ALERTS is an Oracle-supplied PL/SQL package that forms part of the Kernel High Availability notification infrastructure underlying Oracle E-Business Suite releases 12.1.1 and 12.2.2. Its stated purpose, taken directly from the package header comments, is to provide the PL/SQL public interface for retrieving attributes from HA alerts. In practice the package acts as a decomposition layer: an opaque HA alert object is handed to the package, and individual accessor functions return the discrete attributes that describe that alert. This allows EBS components, diagnostics utilities, and administrative code to inspect an alert's originating service, database identity, host, severity, and timing without needing to understand the internal representation of the alert payload itself.
The package is owned by SYS and is classified under the OTHER API classification in the documented metadata. It is not an APPS-owned or EBS business-application package; rather, it belongs to the database kernel / high-availability layer that supports EBS deployments, including those configured with Real Application Clusters, Data Guard, and similar high-availability topologies.
Key Procedures and Functions
The documented interface consists of eleven public functions, each accepting an alert of type ALERT_TYPE and returning a single attribute. The naming convention get_XXX is consistent throughout, and the package header explicitly describes these routines as the means of getting alert attributes from HA alerts.
GET_SERVICE— returns the service associated with the alert.GET_INSTANCE— returns the instance associated with the alert.GET_DB_UNIQUE_NAME— returns the unique name of the database referenced by the alert.GET_DB_DOMAIN— returns the database domain referenced by the alert.GET_HOST— returns the host on which the alert originated.GET_INCARNATION— returns the incarnation value for the alert.GET_CARDINALITY— returns the cardinality attribute as aBINARY_INTEGER.GET_SEVERITY— returns the severity of the alert as aBINARY_INTEGER.GET_EVENT_TIME— returns the event timestamp asTIMESTAMP WITH TIME ZONE.GET_REASON— returns the textual reason or explanation for the alert.GET_VERSION— returns the version attribute of the alert.
No parameter lists beyond the alert input are documented; the metadata confirms return types for the accessors where specified but does not expose the internal structure of ALERT_TYPE.
Tables Accessed
The documented metadata for SYS.DBMS_HA_ALERTS lists no tables referenced via APPS synonyms, and the package is referenced by zero other packages. This is consistent with its role as a pure decomposition utility rather than a data-access routine. HA alert information is supplied to the package as an inbound parameter, so the package does not itself query application tables; it operates on the alert object presented by its caller. Any persistence or retrieval of HA alert records is handled by the surrounding kernel notification infrastructure, not by this package.
Usage Notes
This package is typically invoked from high-availability monitoring and diagnostic code rather than from Oracle EBS Forms, concurrent programs, or standard application flows. Because it is owned by SYS and exposes only read-only accessors, it is intended for administrative and troubleshooting use — for example, when EBS administrators or Oracle support engineers need to inspect the contents of an HA alert raised by the kernel notification subsystem during failover, instance recovery, or service-level monitoring events. Custom code that consumes HA alerts can call the individual get_XXX functions to extract the service, instance, host, severity, reason, and event time for logging or reporting purposes. Its classification under OTHER indicates that it is not part of the supported EBS application API surface, and direct dependencies on it should therefore be treated with caution during upgrades from 12.1.1 to 12.2.2.
-
PACKAGE: SYS.DBMS_HA_ALERTS
12.1.1
-
PACKAGE: SYS.DBMS_HA_ALERTS
12.2.2
-
PACKAGE: APPS.QPR_MAINTAIN_AW
12.1.1
-
PACKAGE: APPS.QPR_MAINTAIN_AW
12.2.2
-
PACKAGE: APPS.MSC_MANAGE_PLAN_PARTITIONS
12.1.1
-
PACKAGE: APPS.CSI_UTL_PKG
12.2.2
-
PACKAGE: APPS.MSC_MANAGE_PLAN_PARTITIONS
12.2.2
-
PACKAGE: APPS.CSI_UTL_PKG
12.1.1
-
PACKAGE: SYS.DBMS_CDC_UTILITY
12.1.1
-
PACKAGE: SYS.DBMS_CDC_UTILITY
12.2.2
-
PACKAGE BODY: APPS.QPR_MAINTAIN_AW
12.1.1
-
PACKAGE BODY: APPS.QPR_MAINTAIN_AW
12.2.2
-
SYS.DBMS_HA_ALERTS dependencies on ALERT_TYPE
12.1.1
-
PACKAGE BODY: APPS.MSC_MANAGE_PLAN_PARTITIONS
12.2.2
-
PACKAGE BODY: APPS.MSC_MANAGE_PLAN_PARTITIONS
12.1.1
-
SYS.DBMS_HA_ALERTS dependencies on ALERT_TYPE
12.2.2
-
APPS.AHL_UC_INSTANCE_PVT dependencies on AHL_APPLICABLE_INSTANCES
12.2.2
-
PACKAGE BODY: APPS.CSI_UTL_PKG
12.1.1
-
PACKAGE BODY: APPS.AHL_UC_INSTANCE_PVT
12.2.2
-
APPS.CSI_UTL_PKG dependencies on CSI_ITEM_INSTANCES
12.1.1
-
PACKAGE BODY: APPS.CSI_UTL_PKG
12.2.2
-
APPS.CSI_UTL_PKG dependencies on CSI_ITEM_INSTANCES
12.2.2
-
APPS.AHL_UC_INSTANCE_PVT dependencies on FND_LOG
12.2.2
-
APPS.CSI_UTL_PKG dependencies on FND_MSG_PUB
12.1.1
-
APPS.CSI_UTL_PKG dependencies on FND_MSG_PUB
12.2.2
-
APPS.MSC_MANAGE_PLAN_PARTITIONS dependencies on FND_API
12.2.2
-
APPS.MSC_MANAGE_PLAN_PARTITIONS dependencies on FND_API
12.1.1
-
APPS.CSI_UTL_PKG dependencies on FND_MESSAGE
12.1.1
-
APPS.CSI_UTL_PKG dependencies on FND_MESSAGE
12.2.2
-
APPS.CSI_UTL_PKG dependencies on FND_API
12.1.1
-
APPS.CSI_UTL_PKG dependencies on FND_API
12.2.2