## param_checkall

### Use

You check the database parameters on the basis of the properties, calculation formulas and conditions stored in the default parameter file. How this proceeds depends on whether or not you opened a parameter session before executing the DBM command.

If you have opened a parameter session (see: param_startsession) and an error is found during the check, then the check is stopped and the results are output together with an error message. Correct the database parameter (see: param_put) and then start the check again. Repeat this procedure until the database parameter check does not find any more errors. All changes to database parameters are first buffered by the system. They are only entered in the parameter file when you explicitly confirm the changes you have made (see: param_commitsession).

If you start the check without first opening a parameter session, and the check finds an error, then the system adapts the changed parameter values to the valid rules and enters these in the parameter file. Changes do not take effect until the database instance is restarted.

See also:

Database Administration Tutorial, Changing the Values of Multiple Database Parameters

Concepts of the Database System, Database Parameters

### Prerequisites

You have the server authorization ParamCheckWrite.

### Syntax

param_checkall

### Successful Reply

OK

### Reply in the Event of Errors (with Parameter Session)

ERR

-24986,ERR_XPCHECK: param check failure/request

<parameter_name> <check_status>

<user_value>

<computed_value>

Values for the Reply Fields

Field | Description
<parameter_name> | Name of database parameter
<check_status> | Check results; the following values are possible: mandatory | constraint mandatory: An obligatory database parameter has been assigned an empty value. constraint: A condition defined in the default parameter file was not fulfilled.
<user_value> | Value defined by the user for the database parameter
<computed_value> | Default value calculated by the system