Use
You analyze the whole set of all parameters.
Prerequisites
You have
opened a parameter session.You have the DBM operator authorization
ParamCheckWrite.Syntax
param_checkall [<mode>]
Option
<mode>With the parameter <
mode> you control the behavior of the parameter manager in parameters with the check status request.Possible values of
<mode>:
No entry |
The system default values are used for all parameters (necessary for background processing). |
GENERAL |
Only the parameters from the group General - General Database Parameters are requested during the check status request. |
EXTENDED |
Only the parameters from the groups General - General Database Parameters and Extended - Special Database Parameters are checked. |
SUPPORT |
This option is only relevant for support. All parameters (from the groups General, Extended and Support) are checked. |
Reply
If an error occurs the parameter check is canceled with an error message.
ERR
14,ERR_XPCHECK_CN00 : param check failure/request
<parameter_name> <check_status>
<user_value>
<computed_value>
<parameter_name> |
Name of parameter |
<check_status> |
The following check statuses may occur: Mandatory – An obligatory parameter has been assigned a blank value.Constraint – a constraint could not be fulfilled.Request – the user input deviates both from the value transferred to the system and confirmed by it earlier, as well as from the system default value. |
<user_value> |
Value that the user entered with param_put. |
<computed_value> |
Default value calculated by the system |
For open
requests the parameter changes cannot be confirmed (parameter change confirmation).Continuation of Procedure
Correct the parameter in question using
param_putconfirm (correcting parameters) or param_put (parameter value change)and carry out a new check with the command param_checkall [<mode>].The new parameter value is registered by the system, and is transferred to the parameter file as the effective value when the database instance is restarted.