3 Replies Latest reply on Sep 3, 2017 5:44 AM by Carey Walker

    Recon Jobs include unchanged CI option

    Pawan K

      Team-
      I am running the recon jobs and not clear about how the checkbox include all unchanged CI's behave. Below is the scenario:-
      I was running the recon jobs in new environment for the first time so followed below steps:-
      1. Push from ADDM to BMC.ADDM dataset in remedy
      2. Run Identification Job
      3. Run a merge job to merge data from asset dataset to a staging dataset(with option Include all unchanged CI's selected) to consider all the CI's for the first time
      4. Run a merge job to merge data from ADDM dataset to the same as above staging dataset(with option Include all unchanged CI's selected) to consider all the CI's for the first time
      5. Run final merge job to merge all the data from staging dataset above to Asset dataset(with option Include all unchanged CI's selected) to consider all the CI's for the first time

       

      Now after 1 week we tried to run the recon jobs again with the same steps.:-


      1.Push from ADDM to BMC.ADDM dataset in remedy which already have data that was pushed and identified earlier
      2. Run Identification Job on the addm data.
      3. Run a merge job to merge data from asset dataset to a staging dataset(with option Include all unchanged CI's unselected). Hence it processed very less number of CI's probably those which were changed. This seems to working fine.
      4. Now, Run a merge job to merge data from ADDM dataset to the same as above staging dataset(with option Include all unchanged CI's unselected). But this job still processes all the CI's in ADDM dataset. Why so? From where does it checks if the data was changed or not. When I checked the modified date for the data in ADDM dataset in remedy, I found all the records were have updated modified date. Even though there was no change in soem records still the dates were updated.

      If the ADDM updates all the record in BMC.ADDM dataset in remedy instead of the delta then everytime when i run the merge job all CI's will be considered in merge activity which will increase the time of merge.

      Please suggest how to fix this or this is the default behavior ?

        • 1. Re: Recon Jobs include unchanged CI option
          Carey Walker

          I think the issue is that when you run the ID job on the ADDM dataset in week 2, it is updating every record (new ones and ones already identified in week 1) since there are several 'housekeeping' attributes that it will maintain values for. Example FailedAutomaticIdentification is a flag set to indicate whether this item was successfully identified or not. It's possible that it re-evaluates this each time, for every record.It's also possible that the push from ADDM may have updated the last modified date for all records in the dataset, even if already there from week 1 - not sure if it works incrementally or not.

           

          I guess you need to check when that last modified date was set - by the ADDM push, or by the identification job on the ADDM dataset. I have a feeling it's the ID job. Can you please check and let us know?

           

          The 'Include all unchanged CIs' option, when not selected (i.e. make the run incremental) uses the last run date of the recon job to compare with the last modified date of each record in the dataset, by the way. So if the record has not been updated since the last time the recon. job ran, it will be skipped.

          • 2. Re: Recon Jobs include unchanged CI option
            Pawan K

            Hi Carey,

             

            Thanks for your reply. I had checked and all the records in ADDM were modified by the after the ADDM push to CMDB.

            Just want to understand the records identified during week 1 ID job run, why will they be updated by ID job run on week 2.

            • 3. Re: Recon Jobs include unchanged CI option
              Carey Walker

              Ok, I think this is just how the ID activity operates. All the records have been updated by the ADDM push (as you have checked) so I think it's re-evaluating the identification rules all over again and updating those house keeping attributes I mentioned as a result. I can't easily test this right now but will try and find an environment where I can. i.e. if a record has already been identified (it has an recon. id other than 0) AND its last modified date is updated, when the ID activity runs, does it process everything all over again. It seems from you example it does.