on 2014 May 06 10:19 PM
Update: The original question was stated "What might cause a mirror to disconnect during a long ALTER TABLE?"
The mirror became disconnected from the primary for some unknown reason, then it appears it couldn't become the primary itself, then it restarted itself, then it became the mirror again. In the meantime the primary kept chugging away, although Sybase Central became unresponsive.
I. 05/05 02:47:49. Starting checkpoint of "xxx" (xxx.db) at Mon May 05 2014 02:47 I. 05/05 02:47:50. Finished checkpoint of "xxx" (xxx.db) at Mon May 05 2014 02:47 I. 05/05 02:54:24. Database "xxx" mirroring: disconnected from partner "ppp" I. 05/05 02:54:24. Database "xxx" mirroring: becoming primary server ... I. 05/05 02:59:20. Database "xxx" mirroring: neither partner nor arbiter confirmed this server could become primary I. 05/05 02:59:20. Database "xxx" mirroring: restarting to determine mirror role I. 05/05 02:59:23. Database "xxx" mirroring: disconnected from arbiter "aaa" I. 05/05 02:59:23. Database "xxx" (xxx.db) stopped at Mon May 05 2014 02:59 I. 05/05 02:59:23. Starting database "xxx" (c:\\xxx\\xxx.db) at Mon May 05 2014 02:59 ... I. 05/05 02:59:23. Database recovery in progress I. 05/05 02:59:23. Last checkpoint at Mon May 05 2014 02:47 I. 05/05 02:59:23. Checkpoint log... I. 05/05 02:59:28. ... recovery 13% complete ... I. 05/05 02:59:58. ... recovery 92% complete I. 05/05 03:00:02. Opening dbspace ccc ... ... I. 05/05 03:00:02. Opening dbspace ddd ... ... I. 05/05 03:00:07. ... recovery 12% complete ... I. 05/05 03:00:38. ... recovery 87% complete I. 05/05 03:01:47. Transaction log: xxx.log... I. 05/05 03:07:16. Database "xxx" mirroring: local status for this server: role=mirror, state=synchronizing, sequence=52, yielding=N I. 05/05 03:07:16. Database "xxx" mirroring: determining mirror role ... I. 05/05 03:07:16. Database "xxx" mirroring: connected to partner "ppp" I. 05/05 03:07:16. Database "xxx" mirroring: partner status for this server: role=mirror, state=synchronizing, sequence=52, yielding=N I. 05/05 03:07:17. Database "xxx" mirroring: connected to arbiter "aaa" I. 05/05 03:07:17. Database "xxx" mirroring: arbiter status for this server: role=mirror, state=synchronizing, sequence=52, yielding=N I. 05/05 03:07:17. Database "xxx" mirroring: synchronizing ... I. 05/05 03:07:17. Database "xxx" (xxx.db) started as mirror at Mon May 05 2014 03:07 ... I. 05/05 03:07:30. Starting checkpoint of "xxx" (xxx.db) at Mon May 05 2014 03:07 I. 05/05 03:09:09. Finished checkpoint of "xxx" (xxx.db) at Mon May 05 2014 03:09
Could this be caused by the tcpip timeout=2 in the mirror configuration file?
# dbsvc.exe parameters... -o zzz\\dbsvc_create_service_log.txt -y -as -i -s Automatic -t Network -w ppp "C:\\Program Files\\SQL Anywhere 12\\Bin64\\dbsrv12.exe" # dbsrv12.exe parameters... -n sss -o ... .txt -su nfr -x tcpip(port=55500;dobroadcast=no) -xf ... .txt -gl All -ti 0 ... xxx.db -sn ccc -sm ddd -xp partner=(eng=ppp;links=tcpip(host=192.168.0.20;port=55500;timeout=2));mode=sync;autofailover=YES;auth=...;arbiter=(eng=aaa;links=tcpip(host=192.168.0.30;port=55501;timeout=2))
Request clarification before answering.
User | Count |
---|---|
52 | |
10 | |
9 | |
8 | |
5 | |
5 | |
5 | |
5 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.