Configuring Database System Check (Oracle) (SAP Library

Configuring Database System Check (Oracle)

Use

This section describes how you can configure the Oracle database system check in the Computing Center Management System (CCMS) to:

· Add new conditions of type ORA or PROF

· Exclude individual conditions from the check

· Specify threshold values for the conditions

· Create object-specific conditions to exclude them from the check

· Create object-specific conditions to set individual threshold values

· Specify corresponding corrective actions

· Maintain the condition description

Prerequisites

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

· Changed or new condition take effect the next time Check databaseis executed by the DBA Planning Calendar or you execute a database system check with BRCONNECT.

· If a condition is met during a database system check, an alert is raised in the Oracle database monitor. For more information, see Displaying Alert Messages from Database System Check.

Procedure

...

1. Choose Administration ® CCMS ® DB Administration ® DB System Check ® Configuration. Alternatively, call transaction DB17.

In Number of Database Check Conditions, you can see an overview of the current status of the check conditions:

¡ Database Administration: Number of database administration check conditions

¡ Database Operations: Number of database operation check conditions

¡ Database Messages: Number of Oracle alert check conditions

¡ Database Profile: Number of Oracle parameter check conditions

¡ Active: Number of active check conditions

¡ Inactive: Number of inactive check conditions

¡ Total: Total number of check conditions

In the table you can see the following columns:

Column	Description
Type	Type of alert the condition is assigned to: · DBA These database administration conditions check database space (fill level and fragmentation), physical consistency (availability of data) and DBA-specific problems, in the database system. · DBO These database operation conditions check DBA 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 These are Oracle alert conditions. If there is an error, these are read from the Oracle alert file, alert_<DBSID>.log, and an alert is reported. You can define any number of new conditions (that is, Oracle error code or Oracle message strings). · PROF These profile conditions compare the values of the Oracle database conditions with the values in the DBCHECKORA configuration table. You can define any number of new conditions (that is, Oracle profile conditions).
Condition	The technical name of the condition. · Type DBA, see BRCONNECT Default Conditions for Database Administration. · Type DBO, see BRCONNECT Default Conditions for Database Operations . · Type ORA, see “Oracle Messages” in Database Health Alerts. · Type PROF, see “Profile Parameters” in Database Health Alerts.
Object	Object-specific instance of a condition 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 condition, a corresponding master condition must exist. This master condition is the standard for all specific instances of the condition. This master condition does not contain any object specifications. Only function IDs can be specified for conditions of type DBO. All function IDs used by DBA tools can be found in the table DBAFID.
Actv.	Indicates whether the condition is active (green) or inactive (red)
Level	Severity of the alert message: E Error W Warning A Exception due to a deviation from the SAP standard (for example, a condition for a PROF alert message is not within the value range we recommend)
Operands, 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 Gigabyte · H Hours · K Kilo · M Megabyte or minutes · P Percent · R Rate · S Seconds With Operand = >, Value = 80 and Unit = P, an alert is triggered when the value of the condition checked exceeds 80%.
Period, Unit	These fields are not used by BRCONNECT.
Date	Date the last time the condition was changed
User	User who made the last changes to the condition
CorrType	Tool to use for the corrective measures: · D DBA action · E Text editor · H Hotline · P DBA program · R SAP report · T SAP transaction
CorrMeasure	Corrective measures to fix an alert for the condition
Description	Description of condition

2. To display details about a selected condition, choose Details.

The system displays details of the selected condition, as shown in the table below for creating a new condition.

3. To create a new condition of type ORA or PROF:

...

a. Select an existing condition of the required type ORA or PROF.

b. Choose Create with template.

c. Enter data in the fields displayed:

Screen Area	Field	Description
Condition definition	Condition type	See Type in table above. Choose Database message, to add a new condition of type ORA or Database Profile to add a new condition of type PROF.
	Condition name	See Condition in table above.
	Check object	See Object in table above.
	Active flag	See Actv. in table above. Enter Yes to activate the parameter.
	Condition level	See Level in table above.
	Check condition	See Operands, Val., Unit in table above.
	Description	See Description in table above.
Repetition period	Duration and Time Unit	Not used.
Corrective measure	Correction type	See CorrType in table above.
Corrective measure	Corrective action	See CorrMeasure in table above.
Changed by	User and Date	The user and date of the last change (you cannot enter data in these fields)

d. Choose Save to save your changes

4. To change a selected existing condition:

...

a. Select an existing condition.

b. Choose Change.

c. Enter data in the fields displayed as described in the table above for creating a new condition.

Note

When you change an existing condition, you cannot enter data in all fields.

5. To make a selected condition object-specific, choose Copy for object and enter the name of the object in Check Object, then do the following:

¡ To exclude an object from the check, select No for Active Flag.

¡ To set an individualized threshold, enter data as described in the table above for creating a new condition, making sure to enter data in the check condition fields.

Note

You cannot make all conditions object-specific.

6. To activate or deactivate a condition, select the relevant condition and select the Actv. field for that condition.

The condition switches to active or not active.