Does SET MIRROR OPTION synchronization_mode actually affect 22.214.171.12498 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 126.96.36.19998 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 188.8.131.5294 and I believe in the current 184.108.40.2061) 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 220.127.116.1198, I recommend upgrading to a recent build.