Tags: abcd, back, completion, database, estimated, failoverquot, following, message, microsoft, mysql, nonqualified, oracle, partner, quotalter, rollback, rolled, server, sql, transactions
Nonqualified transactions are being rolled back. Estimated rollback completion: 100%.
Sometimes when I do "alter database ABCD set partner failover" I get the following message: Nonqualified transactions are being rolled back. Estimated rollback completion: 100%.
In 99 percent of the cases after such message the first attempt to use an open connection would also raise an error such as "Exception: A transport-level error has occurred when sending the request to the server. (provider: Shared Memory Provider, error: 0 - No process is on the other end of the pipe.)"
After the first error all subsequent queries would run perfectly.
What am I missing?
Leave a comment...
- 4 Comments
The first message indicates that there were users found in the principal when you issued the failover. These users have to be killed and their transactions rolled back.
The second exception message tends to indicate that the connection getting the error was one of the users found in that database and they were killed.#1; Thu, 13 Sep 2007 20:02:00 GMT
Thanks for the reply!
Could you please elaborate some more why the connection sometimes get killed and the action rolled back. Does not mirroring suppose to move the connection to the active database without killing it?
Avi#2; Thu, 13 Sep 2007 20:03:00 GMT
- No, that is not how it works. It can reconnect to the new mirror, but the existing connection will get killed and its transaction rolled back. #3; Thu, 13 Sep 2007 20:04:00 GMT
- Standard database projection requires that if a connection is killed prior to the transaction being completed that the transaction must be rolled back. By initiating a failover all connections are severed and must therefor be rolled back. #4; Thu, 13 Sep 2007 20:04:00 GMT