Configuring Database System Check (Oracle) 

Use

Use this function to configure the database system check in order to:

Procedure

To configure the database system check, choose Tools ® CCMS ® DB Administration ® DB System Check ® Configuration. Alternatively: Call Transaction DB17 .

The configuration data for the database system check is stored in the table DBCHECKORA.

The group box Number of SAPDBA check parameters provides an overview of the current status of the parameters (such as the current number of active parameters. You configure the individual parameters in the table below the box. The table includes the following columns:

Column

Description

Typ

Type of alert the parameter is assigned to There are four alert types:

DBA

Includes 19 parameters at delivery. These check memory space (fill level and fragmentation), physical consistency (availability of data) and DBA-specific problems, in the database system

DBO

Includes eight parameters at delivery. These check database operations that:

  • Terminated or had errors between the time of the last check and the current time A terminated operation or one with errors is reported only once.
  • Have not been processed successfully since a specific (time) period

ORA

Includes 13 parameters at delivery. If there is an error, these are read from the Oracle alert file, <SID>alert.log , and an alert is reported Any number of new parameters (Oracle error messages or Oracle strings) may be defined.

PROF

Includes 25 parameters at delivery. These compare the values of the Oracle database parameters with the values in the configuration table DBCHECKORA. Any number of new parameters (Oracle profile parameters) may be defined.

Parameter

Parameters and Alerts for Database System Check

Object

Object-specific instance of a parameter of type DBA or DBO. The instance can be used to exclude the object from the check or to individualize the object settings.

In order to specify object-specific instances of the parameter, a characteristic master parameter must exist. This master parameter is the standard for all specific instances of the parameter. This master parameter does not contain any object specifications. When it is set to inactive, all specific instances of the parameter are set to inactive (this does not apply to parameters of type DBO)

Only Operation objects may be specified for parameters of type DBO. These operation objects are entered as objects in the XDB tables DBAREOL, DBAOPTL or DBASPAL.

Actv.

Indicates whether the parameter is active (green) or inactive (red)

Sev.

Severity of the alert message:

A Exception due to a deviation from the SAP standard (for example, a parameter for a PROF alert message is not within the value range we recommend)

E Error

W Warning

Operand,

Val.

Unit

Definition of the threshold value using operand, value and unit.

Possible operands are: equal to, not equal to, less than, less than or equal to, greater than, greater than or equal to and greater than and less than.

The possible units are:

D Days

G Giga

K Kilo

M Mega

P Percent

R Rate, only for type ORA (Number of alerts for each check session)

S Seconds

With Operand = >, Value = 80 and Unit = P, an alert is triggered when the value of the parameter checked exceeds 80%.

With Operand = >, Value = 1 and Unit = R, an alert is triggered if the Oracle alert corresponding to the ORA parameter, or the ORA parameter corresponding to the Oracle string, is logged in the Oracle alert file <SID>alert.log more than once during the check session.

Period

The minimum time period before the parameter will be checked again

For parameters of types DBO, PROF and ORA: If a parameter has several object-specific instances for which individual periods are specified, the system will always use the largest period for the time interval.

You want to check the parameter ARCHIVE_STUCK only once a week. However, the database system check is planned in the DBA Planning Calendar to run daily.

For the parameter ARCHIVE_STUCK , enter 7 in the Period field and Days in the Unit field. The parameter is only checked once a week.

Unit

Unit for period (time interval)

Possible units are Seconds, Hours, or Days

Date

Date the last time the parameter was changed

User

User who made the last changes to the parameter

CorrType

Tool to use for the corrective measure(s):

E Text editor

H Hotline

P SAPDBA program

R R/3 report

T R/3 transaction

CorrMeasure

Measures to be taken to fix alert

Description

Description of parameter / alert

SAPDBA uses placeholders (#1, #2) to correctly describe the parameters and alerts:

Type DBA: Do not change these alerts, only add to them

Type DBO: The placeholder #1 is replaced by a detailed alert generated by SAPDBA

Type ORA: The error alert ORA-... logged in the Oracle alert log is displayed (and not the existing documentation in the Description field

Type PROF: The placeholder #1 is replaced by an alert generated by SAPDBA If the placeholder #1 is not used or the Description field is empty, the system displays the Oracle documentation for the database parameter

To display details about a selected parameter, choose Parameter details . To update the configuration table display, choose Refresh .

Activities

Adding new parameters of type ORA or PROF

To add a new parameter of type ORA or PROF to the database system check, do the following:

  1. Choose Create new check (with reference)
  2. In the Typ field, choose the type of alert ( ORA or PROF). Enter Database error message, to add a new parameter of type ORA or DB Profile parameter to add a new parameter of type PROF
  3. In the Parameter field enter the name of the parameter
  4. In the Actv. Field, enter Yes to activate the parameter
  5. In the Condition field, specify the threshold value (operand, value and unit)
  6. In the Description field, enter a brief description of the parameter
  7. In the Repeat period field, enter the time period and the unit
  8. In the Corrective measure field, enter the type of corrective measure and a description of the corrective measure
  9. Save the new parameter

The changes made take affect the next time the action Check database is executed by the DBA Planning Calendar (DB13) or the SAPDBA command -CHECK is executed.

Activating / Deactivating check parameters

Use the column Actv. to activate (green) or deactivate (red) parameters.

Specifying threshold values for the parameters

Threshold values can be specified for the following parameters:

Parameter

Error Type

ARCHIVE_STUCK

DBA

CRITICAL_SEGS

DBA

FS_FULL

DBA

MANY_EXTENTS

DBA

TSP_FULL

DBA

All parameters

DBO

Checkpoint not complete (or similar alerts)

ORA

All parameters

PROF

  1. Select the parameter and choose Change
  2. Specify the operand, value, and unit
  3. Save the parameter

Create object-specific parameters to exclude them from the check

Object-specific instances can be created for the following parameters to exclude them from the check:

Parameter

Object

Type

CRITICAL_SEGS

<Table> or <Tablespace>

DBA

FS_FULL

<SAPDATA> or <file system>

DBA

MANY_EXTENTS

<Table> or <Tablespace>

DBA

MISSING_INDEXES

<Table>

DBA

NO_OPT_STATS

<Table>

DBA

TABLES_NOT_IN_TABLE_TABLSPACE

<Table>

DBA

TSP_FULL

Tablespace

DBA

All parameters

  

DBO

  1. Select the parameter and choose Create object check
  2. In the Object field enter the name of the object You can also specify the wildcard * (for example, *character string, *character string* or character string*)
  3. In the Actv. field, enter No to deactivate the parameter
  4. Save the new object-specific parameter

Creating an object-specific parameter to set an individualized threshold value

Individualized threshold values can be specified for the following object-specific parameters:

Parameter

Object

Type

CRITICAL_SEGS

<Tablespace>

DBA

FS_FULL

<SAPDATA> directory or <file system>

DBA

TSP_FULL

<Tablespace>

DBA

All parameters

  

DBO

  1. Select the parameter and choose Create object check
  2. In the Object field enter the name of the object
  3. In the Actv. Field, enter Yes to activate the parameter
  4. In the Condition field, specify the threshold value (operand, value and unit)
  5. In the Description field, enter a brief description of the parameter
  6. In the Repeat period field, enter the time period and the unit
  7. In the Corrective measure field, enter the type of corrective measure and a description of the corrective measure
  8. Save the new object-specific parameter

Setting parameter check periods

You can set the check period for every parameter:

  1. Select the parameter and choose Change
  2. In the Repeat period field, enter the time period and the unit
  3. Save the changed parameter

Specifying corrective measures

You can specify a corrective measure for every parameter:

  1. Select the parameter and choose Change
  2. In the Corrective measure field, enter the type of corrective measure and a description of the corrective measure
  3. Save the changed parameter

Maintaining parameter documentation

Documentation can be maintained for all parameters:

  1. Select the parameter and choose Change
  2. In the Description field, enter a brief description of the parameter
  3. Save the changed parameter