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

Description

NOARCHIVELOG_MODE

(previously 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

(previously ARCHIVE_STUCK)

Warning

Checks the highest fill level of the archiving directory (by default oraarch).

The OBJECT field is not specified for this condition.

Possible test operands, threshold values, value units:

·        >, >= <number>

The space used is larger than (or the same as) <number> % of the total space in the archiving directory.

·        >, >= <number>

The space used is larger than (or the same as) <number> K|M|G bytes.

·        <, <= <number>

The free space is smaller than (or the same as) <number> % of the total space in the archiving directory.

·        <, <= <number>

The free space is smaller than (or the same as) <number> K|M|G bytes.

FILE_SYSTEM_FULL

(previously FS_FULL)

Warning

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:

·        >, >= <number>

The space used is larger than (or the same as) <number> % of the total space in the file system.

·        >, >= <number>

The space used is larger than (or the same as) <number> K|M|G bytes.

·        <, <= <number>

The free space is less than (or the same as) <number> % of the total space in the file system.

·        <, <= <number>

The free space is smaller than (or the same as) <number> K|M|G bytes.

TABLESPACE_OFFLINE

(previously 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

(previously TSP_BACKUP_MODE)

Warning

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

(previously TSP_FULL)

Warning

Checks the maximum level of tablespaces in the database. 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:

·        >, >= <number>

The space used is larger than (or the same as) <number> % of the total space in the tablespace.

·        >, >= <number>

The space used is larger than (or the same as) <test> K|M|G bytes.

·        <, <= <number>

The free space is less than (or the same as)  <number> % of the total space in the tablespace.

·        <, <= <number>

The free space is smaller than (or the same as) <number> K|M|G bytes.

DATA_FILE_MISSING

(previously FILE_MISSING)

Warning

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

(previously REDOLOG_MISSING)

Error

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

(previously CONTROL_FILE_MISSING)

Error

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

(previously FILE_MISMATCH)

Error

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

(previously FILE_TYPE_UNKNOWN)

Error

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

(previously REDOLOG_MIRROR)

Error

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

(previously CONTROL_MIRROR)

Error

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

(previously DF_OFFLINE)

Error

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

Examines the data files with an activated autoextend feature. A check is made to see whether the file system might overflow due to the existing parameter setting (MAXSIZE and INCRSIZE) during the automatic file extension.

The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units.

CRITICAL_TABLESPACE

Warning

Enhances the CRITICAL_FILE check (see above) if there are several autoextend files of a tablespace on the same disk (that is, logical volume) by checking whether there is sufficient free space on the hard disk to extend these files to the maximum size (max_extn).

The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units.

TOO_MANY_EXTENTS

(previously MANY_EXTENTS)

 

Warning

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:

·        >, >= <number>

More than <number> % of the maximum number of extents was already allocated.

·        >, >= <number>

More than <number> extents were already allocated

·        <, <= <number>

Fewer than <number> % of the maximum number of extents can still be allocated.

·        <, <= <number>

Fewer than <number> extents can still be allocated.

CRITICAL_SEGMENT

(previously CRITICAL_SEGS)

Warning

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

(previously TABLES_NOT_IN_TABLE_TABLESPACE)

Error

Checks whether there are tables that not in a table tablespace or indices, which are not in an index tablespace.

For an MCOD system, checks whether table and indexes of an owner are in tablespaces belonging to the owner

The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units.

MISSING_INDEX

(previously MISSING_INDEXES)

Error

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 (previously NO_OPT_STATS)

Error

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

Checks whether there are tables or indices that have statistics, although they should not have these (for example, with ACTIVE flag set to N in DBSTATC).

The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units.

PCTINCREASE_NOT_ZERO

Error

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), you cannot add new conditions to the DBCHECKORA table. You can exclude individual tables and indexes or even complete tablespaces from certain checks that 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, PCTINCREASE_NOT_ZERO