SAP GET_DB_ORA_LATCH Function Module for Latch Monitoring









GET_DB_ORA_LATCH is a standard get db ora 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 latch FM, simply by entering the name GET_DB_ORA_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_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_LATCH'"Latch Monitoring
  EXPORTING
*  I_INST_ID =  "Oracle monitor: Instance ID
   I_SNAPSHOT_FROM =  "Oracle monitor: snapshot ID
   I_SNAPSHOT_TO =  "Oracle monitor: snapshot ID

 IMPORTING
   IS_RAC =  "Is RAC, Y/N?

TABLES
*  LATCH =  "Latch Monitoring
*  LATCH_SUM =  "Latch Monitoring
*  LATCH_CHILDREN =  "Latch Monitoring
*  CACHE_BUF_CHAINS =  "Latch Monitoring
*  LTC_PROTEC_STMT1 =  "Latch Monitoring
*  LTC_PROTEC_STMT2 =  "Latch Monitoring

EXCEPTIONS
   WRONG_DATABASE = 1    WRONG_ORACLE_RELEASE = 2    DB_RELEASE_UNKNOWN = 3
.



IMPORTING Parameters details for GET_DB_ORA_LATCH

I_INST_ID - Oracle monitor: Instance ID

Data type: ORA_INST_ID
Optional: Yes
Call by Reference: Yes

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

EXPORTING Parameters details for GET_DB_ORA_LATCH

IS_RAC - Is RAC, Y/N?

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

TABLES Parameters details for GET_DB_ORA_LATCH

LATCH - Latch Monitoring

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

LATCH_SUM - Latch Monitoring

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

LATCH_CHILDREN - Latch Monitoring

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

CACHE_BUF_CHAINS - Latch Monitoring

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

LTC_PROTEC_STMT1 - Latch Monitoring

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

LTC_PROTEC_STMT2 - Latch Monitoring

Data type: LTC_PROTEC_STMT2
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_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.

DATA:
lt_latch  TYPE STANDARD TABLE OF LATCH, "   
lv_is_rac  TYPE CHAR1, "   
lv_i_inst_id  TYPE ORA_INST_ID, "   
lv_wrong_database  TYPE ORA_INST_ID, "   
lt_latch_sum  TYPE STANDARD TABLE OF LATCH, "   
lv_i_snapshot_from  TYPE ORA_SNAPSHOT_ID, "   
lv_wrong_oracle_release  TYPE ORA_SNAPSHOT_ID, "   
lv_i_snapshot_to  TYPE ORA_SNAPSHOT_ID, "   
lt_latch_children  TYPE STANDARD TABLE OF LATCH_CHILDREN, "   
lv_db_release_unknown  TYPE LATCH_CHILDREN, "   
lt_cache_buf_chains  TYPE STANDARD TABLE OF CACHE_BUF_CHAINS, "   
lt_ltc_protec_stmt1  TYPE STANDARD TABLE OF LTC_PROTEC_STMT1, "   
lt_ltc_protec_stmt2  TYPE STANDARD TABLE OF LTC_PROTEC_STMT2. "   

  CALL FUNCTION 'GET_DB_ORA_LATCH'  "Latch Monitoring
    EXPORTING
         I_INST_ID = lv_i_inst_id
         I_SNAPSHOT_FROM = lv_i_snapshot_from
         I_SNAPSHOT_TO = lv_i_snapshot_to
    IMPORTING
         IS_RAC = lv_is_rac
    TABLES
         LATCH = lt_latch
         LATCH_SUM = lt_latch_sum
         LATCH_CHILDREN = lt_latch_children
         CACHE_BUF_CHAINS = lt_cache_buf_chains
         LTC_PROTEC_STMT1 = lt_ltc_protec_stmt1
         LTC_PROTEC_STMT2 = lt_ltc_protec_stmt2
    EXCEPTIONS
        WRONG_DATABASE = 1
        WRONG_ORACLE_RELEASE = 2
        DB_RELEASE_UNKNOWN = 3
. " GET_DB_ORA_LATCH




ABAP code using 7.40 inline data declarations to call FM GET_DB_ORA_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



Comments on this SAP object

What made you want to lookup this SAP object? Please tell us what you were looking for and anything you would like to be included on this page!