AnsweredAssumed Answered

Change Cora Rules

Question asked by Jason.Huber on Feb 21, 2015
Latest reply on Feb 23, 2015 by Jason.Huber

I'm pushing a server CI via jdbc GRLoader with these fileds.

 

[name]

      ,[serial_number]

      ,[asset_num]

      ,[dns_name]

      ,[class]

      ,[federated_asset_id]

      ,[alarm_id]

      ,[delete_flag]

      ,[mdr_name]

      ,[mdr_class]

      ,[server_type]

      ,[role]

      ,[phys_mem]

      ,[mem_capacity]

      ,[number_proc_inst]

      ,[proc_type]

      ,[app_id]

      ,[smag_1]

 

When the server moves to a new frame only the "federated_asset_id" & "serial_number" change.

Which creates a NEW CI instead of updating the existing.

 

 

If I change only ONE of those 2 fields at a time it updates properly.

I can get the CI updated through 2 updates changing one field at a time, but thats not going to work since both change when a server moves to a new frame.

 

The "asset_num" never changes and is what I'm using as a KEY in my data. CORA rules are ignoring that constant.

 

 

How can I update these 2 attributes at the same time without creating a new CI?

Outcomes