Couple of Checks you should do.
#1 Verify Dataset is crested in CMDB , in your case there is a error ERROR (120121): Dataset is not found.; SCB.ADDM10
#2 CMDB User Configured in ADDM has admin rights
#3 Before sync , try test connection from ADDM site.
Please let know result for all 3 items in your environment.
1: Dataset is created in CMDB thats obvious, and We have tested the connection it is successful.
we have tried elevating addm user permission which is used to sync the data, still no luck
The connection test was successful
CMDB Response Time: 48 ms
CMDB Version: 8.1.01
AR Server Version: 8.1.00 Build 00
This is very basic use case so it should work. can you try connecting to BMC.SAMPLE dataset push few CIs.
Dev, Can you tell me something here
Since i am new to CMDB , The first step to sync ADDM to CMDB is to do with BMC.ADDM first and then CMDB dataset
OR i can directly push the CIs in CMDB dataset.
if you have some data in dataset you configured in ADDM you need to do initial sync. but if dataset has zero CI no initial sync is needed
so if your BMC.SAMPLE is having zeo CIs no initial sync needed.
when you say "dataset" which dataset you are referring to , so to tell you a lil background
We had some data in our UAT Dataset, we have deleted all the CI from that using cmdbdiag utility,
Now out ADDM is clean and no CI inserted in the UAT dataset, and ADDM showing 0 Inserted,Updated.
Now we want to push all CI into UAT , so my question can we do it directly to same Dataset where we ahve deleted or need to do first to BMC.ADDM/SAMPLE
ADDM is supposed to sync data into BMC.ADDM (or another appropriate name). NOT to BMC.ASSET.
Only Reconciliation Engine is supposed to write into BMC.ASSET.
This has become confusing with some discussion talking about SCB.ADDM10 and then a UAT dataset and attempts to load into BMC.ASSET directly.
So first up, as Gustavo has mentioned - you do not load into BMC.ASSET directly. That job is done by the reconciliation engine when you are ready for your staged ADDM discovery data to be promoted to the 'golden' dataset.
Second, what dataset name is your UAT dataset mentioned> And what is the purpose of SCB.ADDM10?
Sounds like you have been test loading some ADDM data into a test/UAT dataset, and now you want it cleared out and a full ADDM load into UAT to happen?
This issue is solved, after restarting the AR Server
AR Restart should not be needed to work on any dataset. now sure how that solved your issue, if AR restart solved this and there was no other configuration issues then it's a defect.