Customizing configuration files

When you initialize the new version of HCL OneDB™, which contains a new onconfig.std file, use the same configuration that the old database server used. After you observe the performance of new version, you can examine the new file for new configuration parameters that you might want to use and can you start to use the new and changed configuration parameters.

Set the ALARMPROGRAM configuration parameter to either nothing or no_log.sh to prevent the generation of errors if the logical log fills during the migration. For more details, see Starting the new version of HCL OneDB. After the migration, change the value of ALARMPROGRAM to log_full.sh.

If the ALARMPROGRAM configuration parameter is set to the script alarmprogram.sh, set the value of BACKUPLOGS in alarmprogram.sh to N.

Important: To facilitate migration (and reversion), use the same values for your new database server for ROOTOFFSET , ROOTSIZE, and ROOTPATH that you used for the old database server. Also, keep the same size for physical logs and logical logs, including the same number of logical logs, and the same sqlhosts file.

If you use custom-code files with the High-Performance Loader, set the HPL_DYNAMIC_LIB_PATH configuration parameter in the plconfig file to the location of the shared library. For example, the location of the shared library might be $INFORMIXDIR/lib/ipldd11a.SOLIBSUFFIX, where SOLIBSUFFIX is the shared-library suffix for your operating system.

For information about how to configure HCL OneDB, see your HCL OneDB Administrator's Guide. For information about how to tune the configuration parameters, see the HCL OneDB Performance Guide.