SAP GET_DB_ORA_CHILDREN_OF_LATCH Function Module for Latch Monitoring

Search SAP Function Modules

GET_DB_ORA_CHILDREN_OF_LATCH is a standard get db ora children of latch SAP function module available within SAP R/3 or S/4 Hana systems, depending on your version and release level. It is used for Latch Monitoring processing and below is the pattern details for this FM, showing its interface including any import and export parameters, exceptions etc. there is also a full "cut and paste" ABAP pattern code example, along with implementation ABAP coding, documentation and contribution comments specific to this or related objects.

See here to view full function module documentation and code listing for get db ora children of latch FM, simply by entering the name GET_DB_ORA_CHILDREN_OF_LATCH into the relevant SAP transaction such as SE37 or SE38.

Function Group: STD8
Program Name: SAPLSTD8
Main Program: SAPLSTD8
Appliation area:
Release date: N/A
Mode(Normal, Remote etc): Normal Function Module
Update:

Function GET_DB_ORA_CHILDREN_OF_LATCH pattern details

In-order to call this FM within your sap programs, simply using the below ABAP pattern details to trigger the function call...or see the full ABAP code listing at the end of this article. You can simply cut and paste this code into your ABAP progrom as it is, including variable declarations.

CALL FUNCTION 'GET_DB_ORA_CHILDREN_OF_LATCH'"Latch Monitoring
  EXPORTING
   I_SNAPSHOT_FROM =  "Oracle monitor: snapshot ID
   I_SNAPSHOT_TO =  "Oracle monitor: snapshot ID
*  LATCH_NAME =  "Oracle monitoring: Name
*  LATCH_INST_ID =  "Oracle monitor: Instance ID

TABLES
*  LATCH_CHILDREN_2 =  "Latch Monitoring

EXCEPTIONS
   WRONG_DATABASE = 1    WRONG_ORACLE_RELEASE = 2    DB_RELEASE_UNKNOWN = 3 

.

IMPORTING Parameters details for GET_DB_ORA_CHILDREN_OF_LATCH

I_SNAPSHOT_FROM - Oracle monitor: snapshot ID

Data type: ORA_SNAPSHOT_ID
Optional: No
Call by Reference: Yes

I_SNAPSHOT_TO - Oracle monitor: snapshot ID

Data type: ORA_SNAPSHOT_ID
Optional: No
Call by Reference: Yes

LATCH_NAME - Oracle monitoring: Name

Data type: ORA_NAME
Optional: Yes
Call by Reference: No ( called with pass by value option)

LATCH_INST_ID - Oracle monitor: Instance ID

Data type: ORA_INST_ID
Optional: Yes
Call by Reference: No ( called with pass by value option)

TABLES Parameters details for GET_DB_ORA_CHILDREN_OF_LATCH

LATCH_CHILDREN_2 - Latch Monitoring

Data type: LATCH
Optional: Yes
Call by Reference: No ( called with pass by value option)

EXCEPTIONS details

WRONG_DATABASE - Non-Oracle Database

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

WRONG_ORACLE_RELEASE - Oracle Release < 9

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

DB_RELEASE_UNKNOWN - Oracle release unknown

Data type:
Optional: No
Call by Reference: No ( called with pass by value option)

Copy and paste ABAP code example for GET_DB_ORA_CHILDREN_OF_LATCH Function Module

The ABAP code below is a full code listing to execute function module POPUP_TO_CONFIRM including all data declarations. The code uses the original data declarations rather than the latest in-line data DECLARATION SYNTAX but I have included an ABAP code snippet at the end to show how declarations would look using the newer method of declaring data variables on the fly. This will allow you to compare and fully understand the new inline method. Please note some of the newer syntax such as the @DATA is not available until a later 4.70 service pack (SP8), which i why i have stuck to the origianl for this example.

ABAP code using 7.40 inline data declarations to call FM GET_DB_ORA_CHILDREN_OF_LATCH

The below ABAP code uses the newer in-line data declarations. This allows you to see the coding differences/benefits of the later inline syntax. Please note some of the newer syntax below, such as the @DATA is not available until 4.70 EHP 8.

Search for further information about these or an SAP related objects