Hierarchy
SAP_FIN (Software Component) SAP_FIN⤷
CA-GTF-DRT (Application Component) Data Retention Tool⤷
FTW1 (Package) Data Retention Tool
Basic Data
| Data Element | TXW_IDXSZM |
| Short Description | Maximum memory allocation for data segment indexes (MB) |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | NUM6 | |
| Data Type | NUMC | Character string with only digits |
| Length | 6 | |
| Decimal Places | 0 | |
| Output Length | 6 | |
| 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 | 0 | |
| Medium | 0 | |
| Long | 40 | Maximum memory allocation for index (MB) |
| Heading | 0 |
Documentation
Definition
This value sets an upper limit for how much memory can be allocated on the application server for building data segment indexes. The value is in Megabytes (MB).
Technical background
When data for a segment is being exported, data for building a segment index is retained. Once the segment is exported completely, this index data is sorted and also exported.
Initially, this index data is stored in the memory. However, the segment index can become very large in size and may exhaust available memory. Even if enough memory is available for storing the index, sorting the temporary index data requires a much larger amount of temporary disk space than the size of the index itself.
To avoid this, there is a limit on how much memory is allocated for holding index data. If this limit is exceeded, index data is temporarily stored in a database table. Once the index has been exported to the data extract file, this table is cleared. This limits memory consumption and offloads the sorting process to the database so that sort space on the application server is not required.
You can use the File size worksheet to estimate the size of the temporary index memory and temporary disk sort space that is required.
The name of the database table that stores temporary index data is TXW_INDEX. Please make sure that there is sufficient table space available for this table.
This temporary storage table can only be used by one extraction run at a time in a system, irrespective of the client. If one extraction run uses the table, any other parallel run automatically uses memory only, and ignores the table.
Performance considerations
Using the TXW_INDEX table for storing index data temporarily introduces additional overheads and decreases performance. Normally, extraction of a particular data segment takes about 30% longer than normal.
If enough memory and sort space are available on the application server, the level of the memory limit should be set so that the entire data extraction and index building can take place in memory. You can use the File size worksheet to estimate the size of the required temporary index memory and temporary disk sort space.
If the data volume is so large that not enough memory is available, it is better to set the memory limit to a smaller value of about 50 MB.
History
| Last changed by/on | SAP | 19981110 |
| SAP Release Created in |
