Login Policy Migration Example

Consider these sample login policies for a 15.x database with multiplex nodes {n1, n2, n3, n4} (assume that {n1} is the coordinator).

Pre-Upgrade Login Policies

Root Login Policy
Login Policy Name General Overrides Multiplex Server Multiplex Overrides
root locked OFF n4 max_connections 15
max_connections 20
Login Policy 1
Login Policy Name General Overrides Multiplex Server Multiplex Overrides
mpx_grp1 locked ON n1 locked OFF
n2 locked OFF
max_connections 5
Login Policy 2
Login Policy Name General Overrides Multiplex Server Multiplex Overrides
mpx_grp2 locked OFF n1 locked ON
max_connections 10
Login Policy 3
Login Policy Name General Overrides Multiplex Server Multiplex Overrides
mpx_grp3 locked ON

Login Policy 4
Login Policy Name General Overrides Multiplex Server Multiplex Overrides
mpx_grp4 n2 locked ON
n3 locked ON
Login Policy 5
Login Policy Name General Overrides Multiplex Server Multiplex Overrides
mpx_grp5 max_connections 20

Post-Upgrade Server Assignments

Post-Upgrade Server Assignments
Login Policy Name Logical Server Member Servers Overrides

root

LS_root

n1, n2, n3, n4, FOR LOGICAL COORDINATOR

locked OFF
max_connections 10

mpx_grp1

LS_mpx_grp1

n1, n2, FOR LOGICAL COORDINATOR

mpx_grp2

LS_mpx_grp2

n2, n3, n4

mpx_grp3

NONE

mpx_grp4

LS_mpx_grp4

n1, n4, FOR LOGICAL COORDINATOR

mpx_grp5

Note:
  • The Overrides column shows locked and max_connections options set to default values in the root login policy. Settings and overrides in other login policies were removed during the upgrade.
  • Because the mpx_grp3 login policy did not allow access to any node prior to the upgrade, the conversion assigns a system defined logical server NONE.
  • Because the mpx_grp5 login policy did not have any explicit setting for locked option prior to the conversion, it simply inherits the logical server assignment from the root login policy. This ensures that mpx_grp5 has access to the same set of nodes as the root login policy.