SAP ABAP Data Element LONG_TX (Number of Long Transactions (aborted))
Hierarchy
☛
SAP_BASIS (Software Component) SAP Basis Component
⤷ BC-DB-INF (Application Component) Informix
⤷ STUI (Package) Informix Database Monitor
⤷ BC-DB-INF (Application Component) Informix
⤷ STUI (Package) Informix Database Monitor
Basic Data
Data Element | LONG_TX |
Short Description | Number of Long Transactions (aborted) |
Data Type
Category of Dictionary Type | D | Domain |
Type of Object Referenced | No Information | |
Domain / Name of Reference Type | SINT4_NOS | |
Data Type | INT4 | 4-byte integer, integer number with sign |
Length | 10 | |
Decimal Places | 0 | |
Output Length | 10 | |
Value Table |
Further Characteristics
Search Help: Name | ||
Search Help: Parameters | ||
Parameter ID | ||
Default Component name | ||
Change document | ||
No Input History | ||
Basic direction is set to LTR | ||
No BIDI Filtering |
Field Label
Length | Field Label | |
Short | 10 | LONG_TX |
Medium | 17 | Long Transactions |
Long | 0 | |
Heading | 0 |
Documentation
Definition
In normal operation this figure should be zero. This figure corresponds to the 'Aborting Long Transaction: tx ...' entries in the database message log. The transaction spans the log space specified by transaction high-water mark (LTXHWM), and the offending long transaction is rolling back.
There are several causes possible:
- A program performs massive data changes (INSERT, UPDATE, DELETE) with too less COMMITs.
=> Revise program. - There is too much concurrent database activty or too less logical log space.
=> Increase logical log space. - ONCONFIG-Parameters LTXHWM and LTXEHWM were reduced without adapting logical log space.
=> Increase logical log space.
History
Last changed by/on | SAP | 20041216 |
SAP Release Created in | 700 |