Hierarchy
SAP_BASIS (Software Component) SAP Basis Component⤷
BC-I18 (Application Component) Internationalization (I18N)⤷
SCP (Package) SAP Code Pages
Basic Data
| Data Element | DBSACHKMOD |
| Short Description | Use Checkpoint Mode ? |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | DBSOFLAG | |
| Data Type | CHAR | Character String |
| Length | 1 | |
| Decimal Places | 0 | |
| Output Length | 1 | |
| 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 | Chk-Mode |
| Medium | 15 | Checkpoint Mode |
| Long | 20 | Checkpoint Mode |
| Heading | 15 | Checkpoint Mode |
Documentation
Definition
The checkpoint mode can be used to process tables in predefined portions. This may be necessary if a job was cancelled because the workload of the database was too high. In such cases you will get error messages (see transaction ST22) like:
"ORA-01652: unable to extend temp segment by 256 in tablespace PSAPTEMP" (Oracle)
"ORA-01555: snapshot too old" (Oracle)
"SQL0289N Unable to allocate new pages in table space PSAPTEMP" (DB6)
"SQL0964C The transaction log for the database is full" (DB6)
"SQL0968C The file system is full. SQLSTATE=57011" (DB6)
"INF-458: Long transaction aborted." (Informix)
This option can be changed anytime as long as no worker job is running.
Use
SAP recommends to set the value to "active" for processing large tables if you encounter one of the errors mentioned above. Using the checkpoint mode increases the runtime of the scans.
Mode
Determines what happens if a job is cancelled while a table is being processed. With the mode set to "inactive" a worker job must reprocess the entire table again. With the mode set to "active", a log is written after a certain number of rows (see frequency) and a new job continues the work at that point where the first job ended.
Frequency
Specifies the number of rows that are processed in one step. Setting the number too low results in a downgrade in performance. The default is currently 2 million, but this can be changed.
Oracle only (Release Oracle 9i):
In addition to the Checkpoint Mode SAP recommends to use the feature "Automatic UNDO Management" as described in SAP Note 600141 in order to avoid the following error: "ORA-01555: snapshot too old".
Dependencies
Example
History
| Last changed by/on | SAP | 20051219 |
| SAP Release Created in |
