Viewing DB System Checks in CCMS (Informix) (SAP Library

Viewing DB System Checks in CCMS (Informix)

Use

You can use this procedure to view the results of database system checks (shortened to "DB system checks") for your Informix database, or to delete results from previous checks. This procedure is started from the Computing Center Management System (CCMS) in the R/3 System.

We recommend that you always check the results of check runs as soon as possible, otherwise you might fail to react in good time to a warning or error.

Prerequisites

You are ready to use CCMS. Refer to Getting Started in CCMS with Informix DBA.

You must run a check before you can view the results. Refer to Running DB System Checks in CCMS (Informix).

Procedure

...

1. Choose CCMS ® DB administration ® Check ® Monitor.

The system displays a list showing the results of previous check runs. For each check run, the highest detected severity is displayed, using a color-coded scheme (that is, red for errors, yellow for warnings, green for OK):

Severity	Color	What to Do
Abort	Red	You must immediately correct the severe error, otherwise data might be lost
Error	Red	You should correct the error as soon as possible, otherwise a severe error might occur leading to data loss
Warning	Yellow	You should correct the setting, but do not need to do so immediately
Not checked	Yellow	As the system could not perform the check, you should find out why not (this is usually given in the recommendation)
Nothing to complain	Green	As the check is OK, you need not do anything.

2. To display the results for a check run, select the row.

The system displays entries for the following:

¡ A Summary for the check run

¡ Checks grouped by severity

3. Look at the highest detected severity in the summary.

If this is nothing to complain, you need take no action, as your system has passed all checks. Otherwise, continue with this procedure.

4. Drill down to display the results of each individual parameter checked.

5. If the check is color-coded red or yellow, perform the necessary action, as identified in the table above.

For each such check, the system displays the expected value and the current value, together with a recommendation, as shown in the following example:

Example

When looking at the detailed results for a check run, you might see something like the following for a single check:

EXTENTS for table vrsx (class DBGENERAL) non-performance check

expected... <= 200 (SAP original)

found ........ 228

recommendation. section D-021 in note ‘64001’ ?

please reorganize table immediately

This means that the value in the variable EXTENTS found for the table vrsx exceeds the recommended maximum value of 200. See Note 64001, or choose ? to display background information about this single check.

You can also see the following information:

· The class of the check is DBGENERAL, that is, general database checks.

· The check is a non-performance check.

· The expected value of the check is SAP original. This means that the expected value had not been amended before the check was run.

6. To find more information about the recommendation for a check, choose the question mark next to it.

A help window is displayed showing detailed information about the single check to help you correct the problem.

7. To delete the results from a previous check run, select the row and choose Delete Protocols. You can delete the results of several check runs at the same time. If you choose Delete Protocols without having selected a row, you can delete all the results.

8. If there are more difficult problems, choose Generate Debug Protocol to look at a detailed event log.

Result

If you follow the recommendations given for checks color-coded red or yellow, you can make sure that your system remains as well tuned as possible. This leads to reduced downtime and better system performance.