Manage Logical Server Membership

You can only access multiplex servers by using logical servers. Login policies control user access to the logical servers.

You can assign one or more logical servers to a login policy. All users using the login policy can only access those multiplex servers that are effective members of the assigned logical servers. You can make one of these assignments to a login policy:

• ALL – allows access to all logical servers, so that you need not specify server names when you add or drop them.
• AUTO – prevents login redirection. Returns an error if the node belongs to multiple logical servers. If the node belongs to a single logical server, uses the logical server context of the current node.
• COORDINATOR – allows access to the current coordinator node, so that, should the coordinator role passes from one server to another, you need not specify the new server name.
• Name of logical server – One or more existing user-defined logical servers.
• OPEN – allows access to all multiplex nodes that are not members of any user-defined logical servers.
• SERVER – allows access to all multiplex nodes, subject to the semantics of the SERVER logical server.
• NONE – denies access to any multiplex server.

• Logical Server Assignment Inheritance
  A login policy without a logical server assignment inherits assignments from the root login policy.
• Lock-down Prevention
  To prevent a lock-down situation due to login policy logical server access configuration, DBA connections will not fail even if the login policy prevents access to the node.
• Changing Logical Server Assignments
  Alter logical server assignments using Interactive SQL.
• Removing Logical Server Assignments
  Remove all existing logical server assignments from a user-defined login policy.
• Node Membership Overlap
  When multiple logical servers are assigned to a single login policy, no overlap in node membership is allowed among those logical servers, including the logical membership of the coordinator.