STI_LATCH_MISSES SAP (Oracle monitoring: structure for GV$LATCH_MISSES.) Structure details
Description: Oracle monitoring: structure for GV$LATCH_MISSES.
Related tables to STI_LATCH_MISSES
Access table STI_LATCH_MISSES
Structure field list including key, data, relationships and ABAP select examples
STI_LATCH_MISSES is a standard SAP Structure so does not store data like a database table does. It can be used to define the fields of other actual tables or to process "Oracle monitoring: structure for GV$LATCH_MISSES." Information within sap ABAP programs.
This is done by declaring abap internal tables, work areas or database tables based on this Structure. These can then be used to store and process the required data appropriately.
i.e. DATA: wa_STI_LATCH_MISSES TYPE STI_LATCH_MISSES.
The STI_LATCH_MISSES table consists of various fields, each holding specific information or linking keys about Oracle monitoring: structure for GV$LATCH_MISSES. data available in SAP. These include PARENT_NAME (Oracle monitoring: Latch name of a parent latch), WHERE_LATCH (Oracle monitoring: Latch - only for compatibility), NWFAIL_COUNT (Oracle Monitoring: Number of failed latch acquisition), SLEEP_COUNT (Oracle Monitoring: Number of acquisitions causing sleeps).. See below for full list along with technical details, documentation, text table, check tables, foreign key relationships, conversion routines, relevant tcodes and example ABAP select code etc. .
Delivery Class:Display/Maintenance via tcode SM30: Display/Maintenance Allowed but with Restrictions
SAP enhancement categories: Cannot Be Enhanced
SAP STI_LATCH_MISSES structure fields - Full list of fields found in SAP data dictionary
| Field | Description | Data Element | Data Type | length (Dec) | Check table | Conversion Routine | Domain Name | MemoryID | SHLP |
| INST_ID | Oracle monitor: Instance ID | ORA_INST_ID | DEC | 22 | ORA_INST_ID | ||||
| PARENT_NAME | Oracle monitoring: Latch name of a parent latch | ORA_PARENT_NAME | CHAR | 50 | ORA_PARENT_NAME | ||||
| WHERE_LATCH | Oracle monitoring: Latch - only for compatibility | ORA_WHERE | CHAR | 64 | ORA_WHERE | ||||
| NWFAIL_COUNT | Oracle Monitoring: Number of failed latch acquisition | ORA_NWFAIL_COUNT | DEC | 22 | ORA_NWFAIL_COUNT | ||||
| SLEEP_COUNT | Oracle Monitoring: Number of acquisitions causing sleeps | ORA_SLEEP_COUNT | DEC | 22 | ORA_SLEEP_COUNT | ||||
| WTR_SLP_COUNT | Oracle Monitoring: Counter | ORA_WTR_SLP_COUNT | DEC | 22 | ORA_WTR_SLP_COUNT | ||||
| LONGHOLD_COUNT | Oracle Monitoring: Counter | ORA_LONGHOLD_COUNT | DEC | 22 | ORA_LONGHOLD_COUNT | ||||
| LOCATION | Oracle Monitoring: Location that attempted to acquire latch | ORA_LOCATION | CHAR | 64 | ORA_LOCATION |
| Key field | Non-key field |
How do I retrieve data from SAP structure STI_LATCH_MISSES using ABAP code?
As STI_LATCH_MISSES is a database structure and not a table it does not store any data in the SAP data dictionary. The ABAP SELECT statement is therefore not appropriate and can not be performed on STI_LATCH_MISSES as there is no data to select.How to access SAP table STI_LATCH_MISSES
Within an ECC or HANA version of SAP you can also view further information about STI_LATCH_MISSES and the data within it using relevant transactions such asSE11 (ABAP Dictionary Maintenance)
SM30 (Maintain Table Data)
SE80 (Object Navigator)
SE16 (Data Browser).
Search for further information about these or an SAP related objects