BRCONNECT Default Conditions for Database Administration
The check conditions for database administration are specified in the control table
DBCHECKORA. For more information, see Database System Check with BRCONNECT.|
Condition |
Severity Level |
Description |
|
NOARCHIVELOG_MODE (formerly NOARCHIVELOG) |
Error |
Checks whether the database is in NOARCHIVELOG mode, which is not allowed for production databases.The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
ARCHIVER_STUCK (formerly ARCHIVE_STUCK) |
Warning |
Checks the highest fill level of the archiving directory (by default, saparch).The OBJECT field is not specified for this condition.Possible test operands, threshold values, value units: The space used is larger than (or the same as) <number> % of the total space in the archiving directory. The space used is larger than (or the same as) <number> K|M|G bytes. The free space is smaller than (or the same as) <number> % of the total space in the archiving directory. The free space is smaller than (or the same as) <number> K|M|G bytes. |
|
FILE_SYSTEM_FULL (formerly FS_FULL) |
Warning |
This condition checks the fill level of file systems on the database host. All file systems are checked by default against the same threshold value. However, you can define different threshold values for individual file systems by specifying the file system in the OBJECT field of the DBCHECKORA table (transaction DB17). Here you can use the following keywords for the database file systems:ORACLE_HOME, SAPDATA_HOME, SAPDATA1, SAPDATA2, ..., SAPARCH, ORIGLOG, MIRRLOG, SAPBACKUP, SAPCHECK, SAPREORG and SAPTRACE.Alternatively, you can specify any other file systems by entering the full path of a directory from this file system into the field (you can use upper/lower case spelling in DB17 only as of the Service Packages mentioned in note 427673, otherwise you have to use native SQL). Possible test operands, threshold values, value units: The space used is larger than (or the same as) <number> % of the total space in the file system. The space used is larger than (or the same as) <number> K|M|G bytes.The free space is less than (or the same as) <number> % of the total space in the file system.The free space is smaller than (or the same as) <number> K|M|G bytes. |
|
TABLESPACE_OFFLINE (formerly TSP_OFFLINE) |
Error |
Checks whether there are tablespaces that are offline. The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
TABLESPACE_IN_BACKUP (formerly TSP_BACKUP_MODE) |
Warning |
This condition checks whether there are tablespaces that have the BACKUP status although BRBACKUP is not active The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
TABLESPACE_FULL (formerly TSP_FULL) |
Warning |
This condition checks the maximum level of tablespaces on the database host. All tablespaces are checked by default against the same threshold value. However, you can define different threshold values for individual tablespaces by specifying the tablespace name in the OBJECT field of the DBCHECKORA table (transaction DB17).Possible test operands, threshold values, value units: The space used is larger than (or the same as) <number> % of the total space in the tablespace. The space used is larger than (or the same as) <test> K|M|G bytes. The free space is less than (or the same as) <number> % of the total space in the tablespace. The free space is smaller than (or the same as) <number> K|M|G bytes. |
|
DATA_FILE_MISSING (formerly FILE_MISSING) |
Warning |
This condition checks whether there are data files that no longer exist in the file system. The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
REDOLOG_FILE_MISSING (formerly REDOLOG_MISSING) |
Error |
This condition checks whether there are online redo log files that no longer exist in the file system. The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
CONTROL_FILE_MISSING (formerly CONTROL_FILE_MISSING) |
Error |
This condition checks whether there are control files that no longer exist in the file system. The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
DATA_FILE_MISMATCH (formerly FILE_MISMATCH) |
Error |
This condition checks whether there are data files that are flagged as MISSING in Oracle control file.The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
INVALID_FILE_TYPE (formerly FILE_TYPE_UNKNOWN) |
Error |
This condition checks whether there are database files that have an illegal operating system type, for example, block raw files on Unix or compressed files on Windows. The OBJECT field is not specified for this condition.This condition does not have test operands, threshold values, or value units. |
|
REDOLOG_FILE_MIRROR (formerly REDOLOG_MIRROR) |
Error |
This condition checks whether there are online redo log files that are not mirrored on the Oracle side. The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
CONTROL_FILE_MIRROR (formerly CONTROL_MIRROR) |
Error |
This condition checks whether there are control files that are not mirrored on the Oracle side. The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
FILE_OFFLINE (formerly DF_OFFLINE) |
Error |
This condition checks whether there are data files or online redo log files that are OFFLINE. The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
CRITICAL_FILE |
Warning |
This condition examines the data files with an activated auto extend feature. A check is made to see whether the file system can be brought to overflow, due to the existing parameter setting ( NEXT and MAXSIZE) during the automatic filename extension.The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
TOO_MANY_EXTENTS (formerly MANY_EXTENTS) |
Warning |
This condition checks whether there are tables or indices, for which the number of allocated extents exceeds the specified threshold value. All tables or indices are checked by default against the same threshold value. However, you can define different threshold values for individual tablespaces by specifying the tablespace name in the OBJECT field of the DBCHECKORA table (transaction DB17).Possible test operands, threshold values, value units: More than <number> % of the maximum number of extents was already allocated.More than <number> extents were already allocatedFewer than <number> % of the maximum number of extents can still be allocated.Fewer than <number> extents can still be allocated. |
|
CRITICAL_SEGMENT (formerly CRITICAL_SEGS) |
Warning |
This condition checks whether there are tables or indexes that can bring the tablespace to overflow when up to 5 next extents are allocated. All tables or indices are checked by default against the same threshold value. However, you can define different threshold values for individual tablespaces by specifying the tablespace name in the OBJECT field of the DBCHECKORA table (transaction DB17).Possible test operands, threshold values, value units: <= <number> The tablespace overflows when you allocate up to 1, 2, 3, 4, or 5 next extents. |
|
IN_WRONG_TABLESPACE (formerly TABLES_NOT_IN_TABLE_TABLESPACE) |
Error |
This condition checks whether there are tables that not in a table tablespace or indices, which are not in an index tablespace. The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
MISSING_INDEX (formerly MISSING_INDEXES) |
Error |
This condition checks whether there are tables that do not have any indices and are not specified in the DBDIFF table exception.The OBJECT field is not specified for this condition.This condition does not have test operands, threshold values, or value units. |
|
MISSING_STATISTICS (formerly NO_OPT_STATS) |
Error |
This condition checks whether there are tables or indices that do not have any statistics, although they should have these. The OBJECT field is not specified for this condition.This condition does not have test operands, threshold values, or value units. |
|
HARMFUL_STATISTICS |
Error |
This condition checks whether there are tables or indices that have statistics, although they should not have these (for example, pool and cluster tables). The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
|
PCT_INCREASE_NOT_ZERO |
Error |
This condition checks whether there are tables or indexes for which the PCTINCREASE storage parameter is not equal to zero. This can lead to storage fragmentation and is not suitable for the SAP System.The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units. |
Since the check conditions for database administration are hard-coded in BRCONNECT (known as built-in check conditions), no new test conditions can be added in the
DBCHECKORA table. You can exclude individual tables and indexes or even complete tablespaces from certain checks (which run at table or index level). To do this, specify the objects in the check_exclude parameter:check_exclude = [<owner>.]<table> | [<owner>.]<index> | <tablespace> | (<object_list>)
You can restrict the following check conditions in this way:
TOO_MANY_EXTENTS, CRITICAL_SEGMENT, IN_WRONG_TABLESPACE, MISSING_INDEX, MISSING_STATISTICS, HARMFUL_STATISTICS