Connector Improvement: Perform Sanity check before any work done.
For Sybase as source, we know that we can not activate HVR replication if there already a Native Replication as Primary or there is another channel is using same source as SQL capture , but we can't stop user to setup such database as HVR replication as source using GUI.
We need to enhance this to do a precheck and failed if HVR find any such situation.
What HVR do for activation and enabling database as source, its mark all the tables in database for replication and then try to run activate capture which fail with
: F_JD02A5: DBMS error [The log transfer context for the current database cannot be reserved because the current database has been enabled for a Rep Agent Thread] server=
But its already caused damage to existing replication setup and lead to unhealthy environment.
Good if we do basic checks which lead to potential future failure like Supported version and this scenario then do any constructive or destructives action.
As deactivation of HVR Channel also marked all the replicating table false as those are in HVR list and subset are original replication , so data replication got broken.
-
Tushar,
My apologies this ended up in the wrong group and was then neglected. Do you feel this is still an issue? Or have you by now implemented processes to deal with this?
Of course it would be a nice capability to have, but there are many other capabilities we could look into. We have to prioritize our investments.
Thanks,
Mark. -
HI Mark
This need to be done on high priority. User can accidently setup HVR replication on top of Sybase replication and break the native replication impacting setup. We have multiple occurrence of that inclusive of production and there is no way we can stop from GUI. This is a stability issue of the environment.
-
OK. Thanks for the feedback. I have added this to the backlog and asked engineering to consider this for future planning.
Mark.
Please sign in to leave a comment.
Comments
3 comments