Automatic resizing of the expansion factor

When SQL_LOGICAL_CHAR is set to a valid digit, and the current session creates a database, HCL OneDB™ compares the SQL_LOGICAL_CHAR value with the maximum number of bytes that any logical character requires in the code set of the database locale.

If the SQL_LOGICAL_CHAR setting is greater than that maximum number of bytes, the database uses the maximum value for the locale as the new expansion factor, overriding what the configuration file specifies. The SQL_LOGICAL_CHAR setting in the configuration file remains unchanged, and continues to act as the default expansion factor for the creation of other databases.