The workload manager can initiate a migration when a request can successfully be sent to a client. Specifically, migration can occur:
To connections that have completed their login:
After an instance receives a new batch from the client, but before the batch is parsed and executed
After an instance completes the processing of a client batch but before it sends a final completion to the client.
When an instance is not executing any batch on behalf of the client.
According to the workload manager’s algorithm. The Work load Manager may migrate certain clients for load balancing or because the current instance is being brought down for maintenance.
When a connection’s context accommodates migration. The workload manager targets connections for migration, but these connections migrate only when their context allows this. In particular, no migration can occur inside a transaction.
Connection migration is not supported for connections
executing Java. See “Using Java in a clustered environment”.
