Access mode and persistence of parameter modifications
The access mode of a parameter defines whether the parameter can be changed dynamically via an ADMIN COMMAND, and when the change takes effect.
The possible access modes are:
▪RO (read-only): the value cannot be changed; the current value is always identical to the startup value.
▪RW: the value can be changed via an ADMIN COMMAND and the change takes effect immediately.
▪RW/Startup: the value can be changed via an ADMIN COMMAND and the change takes effect the next time that the server starts.
▪RW/Create: the value can be changed via an ADMIN COMMAND and the change applies when a new database is created.
All the changes made to parameters having the access mode RW* are stored in the solid.ini file at the next checkpoint. Values set with the temporary option are not impacted.
Saving parameters
It is also possible to request an immediate storing of changed values with the command:
ADMIN COMMAND 'save parameters [ini_file_name]';
If ini_file_name is not specified, the current solid.ini file is rewritten.
If ini_file_name is specified, a full configuration file is written to a new location. Specifying ini_file_name is a convenient way to save configuration file checkpoints for later use.
The access mode of the IndexFile.BlockSize parameter is RO. The parameter is set when the database is created and cannot be modified afterward.
If you want to use a different constant value, you have to create a new database. Before creating the new database, set the new parameter constant value by editing the solid.ini file.
The following example sets a new block size for the index file by adding the following lines to the solid.ini file:
[IndexFile] Blocksize = 4096
After editing and saving the solid.ini file, move or delete the old database and log files, and start solidDB®.
The log block size can be changed between startups of the server.