|
Does SET MIRROR OPTION synchronization_mode actually affect 12.0.1.3298 HA operations after the servers have started? Does SET MIRROR OPTION synchronization_mode have any effect on an old-school HA setup that uses -xp instead of CREATE MIRROR SERVER? Is DB_PROPERTY ( 'MirrorMode' ) supposed to show the effect of SET MIRROR OPTION synchronization_mode or not? The following version 12.0.1.3298 behavior has been noticed in BOTH old-school and declarative HA setups; note that the option_value and MirrorMode values are different: SET MIRROR OPTION synchronization_mode = 'asynchronous';
SELECT * FROM SYSMIRROROPTION;
SELECT DB_PROPERTY ( 'MirrorMode' );
option_name,option_value
'synchronization_mode',asynchronous
DB_PROPERTY('MirrorMode')
'synchronous'
|
|
The current behaviour (in 12.0.1.3994 and I believe in the current 16.0.0.1761) is for:
Note that you should either be using the SQL Anywhere 11 -xp options OR using the SQL Anywhere 12 SET MIRROR OPTIONS and CREATE/ALTER MIRROR SERVER ... syntaxes. Mixing the old and new syntaxes is not recommended and at your own risk. (Note that the SQL Anywhere 11 -xp options are deprecated in 12 and 16 and no longer documented. Support for these old -xp options will be removed in a future version since they can create confusion.) From a quick look at CR#666011 , I believe that before that fix, Given the many mirroring issues that have been fixed since 12.0.1.3298, I recommend upgrading to a recent build.
Is that behaviour the same for the other two modes, too, i.e. is a change of the synchronization mode via SET MIRROR OPTION generally effective immediately?
(20 Feb '14, 03:26)
Volker Barth
Replies hidden
Yes, from a quick look at the code I believe that is the behaviour.
(20 Feb '14, 09:01)
Ian McHardy
|
Does upgrading to a newer EBF resolve the issue? On 12.0.1.3967 changing the synchronization_mode using SET MIRROR OPTION seems to update the MirrorMode property immediately. This appears to have been addressed by CR#666011 in builds 3327 and higher.