BRCONNECT Default Conditions for Database Operations

The check conditions for database operations are specified in the control table DBCHECKORA. For more information, see Database System Check with BRCONNECT.

Condition	Severity	Description
LAST_ARCHIVE_FAILED	Warning	Checks whether the last backup of the offline redo log files with BRARCHIVE failed. BRCONNECT takes the following function IDs into account: sve, cpy, ssv, svd, cpd, ssd, cps, cds The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units.
LAST_BACKUP_FAILED	Warning	Checks whether the last complete backup of the database with BRBACKUP failed. BRCONNECT takes the following function IDs into account: afd, aff, afp, afr, afs, aft, afv, and, anf, anp, anr, ans, ant, anv, ffd, fff, ffp, ffr, ffs, fft, ffv, fnf, fnd, fnp, fnr, fns, fnt, fnv The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units.
LAST_STATS_FAILED	Warning	Checks whether the last update of the optimizer statistics with BRCONNECT failed. BRCONNECT takes the following function IDs into account: sta, aly These refer to the entire database. The OBJECT field is not specified for this condition. This condition does not have test operands, threshold values, or value units.
LAST_OPERATION_FAILED	Warning	Checks whether the last DBA operation failed, which is identified by a function ID specified in the OBJECT field of the DBCHECKORA table. This condition does not have test operands, threshold values, or value units. You can also define this condition by specifying the function ID in the PARAM field. You can also use this convention in later (including current) SAP releases.
ARCHIVE_TOO_OLD	Warning	Checks whether the last successful backup of the offline redo log files with BRARCHIVE is too old. BRCONNECT takes into account the following function ids: sve, cpy, ssv, svd, cpd, ssd, cps, cds The OBJECT field is not specified for this condition. Possible test operands, threshold values, value units: >, >= <number> D The last successful backup of the offline redo log files is older than <number> day(s).
BACKUP_TOO_OLD	Warning	Checks whether the last successful complete backup of the database with BRBACKUP is too old. BRCONNECT takes into account the following function IDs: afd, aff, afp, afr, afs, aft, afv, and, anf, anp, anr, ans, ant, anv, ffd, fff, ffp, ffr, ffs, fft, ffv, fnf, fnd, fnp, fnr, fns, fnt, fnv The OBJECT field is not specified for this condition. Possible test operands, threshold values, value units: >, >= <Number> D The last successful complete backup of the database is older than <number> day(s).
STATS_TOO_OLD	Warning	Checks whether the last successful update of the Optimizer statistics with BRCONNECT is too old. BRCONNECT takes the following function ID into account: sta, aly The OBJECT field is not specified for this condition. Possible test operands, threshold values, value units: >, >= <number> D The last successful update of the optimizer statistics is older than <number> day(s).
OPERATION_TOO_OLD	Warning	Checks whether the last successful DBA operation, identified by a function ID specified in the OBJECT field of the DBCHECKORA table, is too old. Possible test operands, threshold values, value units: >, >= <number> D The last successful DBA operation is older than <number> day(s). You can also define this condition by specifying the function ID in the PARAM field. You can also use this convention in later (including current) SAP releases.

Note Note

Since the test conditions for database operations are programmed in a specific way in BRCONNECT (known as built-in test conditions), you cannot add new check conditions to the DBCHECKORA table. However, this is generally not necessary because operations can be monitored by the LAST_OPERATION_FAILED and OPERATION_TOO_OLD check conditions, or by specifying function IDs in the PARAM field.

End of the note.