The bugs have been worked out, and it has been field tested with great success. We can now say with confidence, this works well.
The hot fix routines are located here if needed:
p_ETL_SYNC_FINAL_1.1.5.sql
p_ETL_SYNC_IDXCUR_1.1.2.sql
p_ETL_SYNC_ZBALSAFE_1.1.2.sql
All three of these hot fix routines need to be applied for this to work.
Remember: to activate zero balance safety, you need to adjust the BPM Connect global settings as such:
use bpmconnect
go
update dbo.const_sys set [value] = '1' where keyid = 'SyncZeroBalanceSafety'
This Hotfix is wrapped into the DBObjects_v1.3.5, so it only applies to older versions. To determine what DBObjects version you are running, see here.
Subscribe to:
Post Comments (Atom)
Scott,
ReplyDeleteFor those who do not know what is "zero balance safety", Can you please explain, and provide an example as how it works in BPMC
Thanks
Hi Scott,
ReplyDeleteDoes this mean that during a sync it will build the other reversing entries to produce the result of a "Replace" as the Reload does? So it's slower because of the additional lines used to zero out all other areas that did not come from the source?
Also, being a global constant, I'm guessing with this on, it is on for all processes in the BPM Connect instance. Please confirm.
Yes, your assessment is correct, it will build the reversing entries, and act as a replace and reload would.
ReplyDeleteSince it will be set in the global constant table, this will affect all feeds in an instance.