Avatar

Correct answer by
Community Advisor

Hi,

 

The nms:broadLogEventHisto/@id col is populated by mcSynch_local workflow, which sets it to:

$int64(vars/@CELL_OFFSET)*$long(vars/@cellId) + @ID

  • vars/@CELL_OFFSET = '72057594037927936' (string since js doesn't go up that high, 2**52)
  • vars/@cellId = xtk:option NmsExecutionInstanceId
  • @ID= nms:broadLogRtEvent/@id

 

If you only have 1 exec instance, set its execution id to 0 in Deployment wizard, it'll get rid of the offset, no further work needed.

 

If you have >1 exec instances, you'll need the offset- it's what keeps the logs from colliding when they're collated on the control instance.

To fix (seems like how it should work ootb?):

  1. Rename the existing @ID col to @idExec or something else
  2. Change the mcSynch_local workflow to write to renamed id col
  3. Make an ordinary autopk col called @ID with its own pkSequence so as not to consume XtkNewId

 

Thanks,

-Jon

View solution in original post