With this command you change the parameters of the database instance. Unlike the function changing the value of a database parameter, the value <value> for the parameter identified as <parameter_name> is written straight to the parameter file. An entry is only made if the parameter is already contained in the parameter file.
In the following cases the parameter change is refused:
· The parameter has the value NOBODYfor the CHANGEproperty
· The parameter has the value NO for the property MODIFY and the parameter file was already checked by the kernel (parameter __PARAM_CHANGED___ exists)
·
You are
dealing with a volume parameter
(property VOLUME
= Yes) and there are
changed
kernel parameters in the parameter file (property VOLUME
=
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.
The entered value for the parameter is not checked for consistency. Therefore unqualified changes to parameters are also possible using the command param_directput. These can then not be rejected by param_abortsession because the changes are written directly to the parameter file.
You have the server authorization ParamFull.
param_directput <parameter_name> <value>
The system displays an OK message.
In the event of errors, see Reply Format.