Upgrading a multiplex database creates an appropriate logical server for each server-specific login policy. Login policies are updated to use a logical server configuration that provides access to the same set of multiplex servers as prior to upgrade.
If a login policy does not allow access to any node (such as when the base setting of LOCKED is ON and there are no multiplex server-level overrides), the login policy is set to a system-defined logical server, NONE, instead of creating a new logical server. NONE indicates that the login policy does not allow access to any multiplex server.
If a login policy has no explicit setting for the LOCKED option, either at the base level or via a multiplex server-level override, no logical server is created for that policy. Such a login policy inherits the logical server assignment of the root login policy.
Membership configuration of a logical server provides access to the same multiplex nodes as the corresponding 15.x login policy. If the login policy allowed access to the current coordinator server, a logical membership of the coordinator is also added to the logical server.
If the login policy name exceeds 125 characters, a logical server is created with the same name as of the login policy, that is, without adding an LS_ prefix.
During the upgrade, some login policy option settings or multiplex server-level overrides are reset or removed. In the root login policy, LOCKED and MAX_CONNECTIONS overrides are reset to default values ( 'OFF' and 10 respectively).
Settings for LOCKED and MAX_CONNECTIONS are removed from user-defined login policies. Multiplex server-level overrides are removed from all login policies.