You confirm all changes to the database parameters and transfer these to the parameter file of the database instance. Before storing them the check status of all parameters is verified.
If you specify the NOCLOSE option, the parameter session remains open after the database parameters have been stored. If you do not specify this option, the parameter session is closed after the database parameters have been stored.
The changed values in the parameter file are only effective after a restart of the database instance.
You have changed parameter values in a parameter session.
You have the server authorization ParamCheckWrite.
param_commitsession [NOCLOSE]
The system displays an OK message.
Execution of the command is refused:
ERR
14,ERR_XPCHECK_CN00 : param check failure/request
<identifier>
<check_status>
<user_value>
<computed_value>
<check_status> |
The following check status may occur: Mandatory: An obligatory database parameter has been assigned an empty value. Constraint: A condition defined in the description file could not be fulfilled (Configuring Database Instances). 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 operator entered with param_put (Changing the value of a database parameter). |
<computed_value> |
Default value calculated by the system |
Check status request is displayed only if the user entry varies from the value of the database parameter in the parameter file.
If the check status is a request, you can correct the error as follows:
Specify the valid value with param_putconfirm (Correcting Database Parameters). Otherwise the system default <computed_value> is used this for parameter for all further calculations of other parameters.
In the following cases, the parameter change is refused:
- The parameter has the value NOBODY for the CHANGEproperty
- The parameter has the value NOfor the property MODIFY and the parameter file was already checked by the kernel (parameter __PARAM_CHANGED___ exists)
- You are
dealing with a volume parameter (VOLUME property = Yes) and there are changed kernel parameters in
the parameter file (VOLUME
property =
No) that have not yet been
checked by the kernel
(Exception: You are creating a new database instance)
- The parameter is a kernel parameter and volume parameters have already been changed, but not yet checked by the kernel.