Hierarchy
⤷
⤷
Basic Data
| Data Element | CHKOBJ |
| Short Description | Object for Check Condition |
Data Type
| Category of Dictionary Type | D | Domain |
| Type of Object Referenced | No Information | |
| Domain / Name of Reference Type | TEXT50 | |
| Data Type | CHAR | Character String |
| Length | 50 | |
| Decimal Places | 0 | |
| Output Length | 50 | |
| 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 | Object |
| Medium | 15 | Object |
| Long | 20 | Check object |
| Heading | 20 | Check object |
Documentation
Definition
Object definition allows the definition of additional object-specific check conditions. This requires a general specification (empty object) as the master definition.
The possible check objects depend on the corresponding check condition:
1.) Certain DBA parameters can be defined in more detail at the tablespace level. This includes: CRITICAL_SEGMENT, FILE_SYSTEM_FULL,
TABLESPACE_FULL and TOO_MANY_EXTENTS.
Example: Tablespace PSAPPROTD for check condition TABLESPACE_FULL
For some DBA check conditions, a threshold value is specified that can be changed. These include: ARCHIVER_STUCK, CRITICAL_SEGMENT, FILE_SYSTEM_FULL, TABLESPACE_FULL, and TOO_MANY-EXTENTS.
2.) Check conditions LAST_OPERATION_FAILED and OPERATION_TOO_OLD can use object-specific attributes. The object specifies the function ID of the operation that is to be checked.
For some DBO check conditions, a threshold value is specified that can be changed. These include: ARCHIVE_TOO_OLD, BACKUP_TOO_OLD, STATS_TOO_OLD and OPERATION_TOO_OLD
Example: "10 days" for object "chk" of check condition OPERATION_TOO_OLD.
3) Check conditions of type PROF and ORA do not require object specification
History
| Last changed by/on | SAP | 20130604 |
| SAP Release Created in |