Highlighted
Absent Member.. Absent Member..
Absent Member..
150 views

UCMDB SUPPORT TIP: Discovering SQL Server Databases/Instances

In the event when there are some CIs that get ignored on the discovery due to “Reason: Connected CI needed for identification was ignored” however, when checked on the reconciliation.data in.ignored log, you can see that the connected CI that was ignored is not actually ignored but it’s getting merged to an existing one.

 

For example:

Data Ignored From Bulk:

 {node@$TempObjecte6c23ac67cecb69911ce52a65e0511eb}@[(string-host_key:167.209.224.105 DefaultDomain), (string-data_source:MSSQL Server Connection by SQL), (boolean-root_enableageing:true), (boolean-host_iscomplete:false), (string_list-lic_type:[udf])]

               

Then it shows that it was merged, the following CIs were merged:

 cfc7aff9bb0c726b1f0c0930d6024385 = e2d33c920315af2208fac3fa67809058; $TempObjecte6c23ac67cecb69911ce52a65e0511eb

 41f6b2c8f2c9b333a0eb2331a56180cd = e28cf4f8dd8717bba9e4445ddb7393fc; $TempObjecte6c23ac67cecb69911ce52a65e0511eb

 94a1659f4eb8841eb8c83774e885077e = e28cf4f8dd8717bba9e4445ddb7393fc; $TempObjecteaa59552cad1cf01f1ada55c2e65157e

 

Since the $TempObjecte6c23ac67cecb69911ce52a65e0511eb shows was ignored then the connected CI’s are ignored

 

SOLUTION:

In order to resolve such discrepancy, first you will need to confirm if the SQL Server that the database has a relationship with is in a cluster. If so then you should discover the clusters (Microsoft Cluster by NTCMD or UDA) then run the Merge Clustered Software discovery job.

 

SQL Servers that are clustered will be duplicated on the various physical hosts which causes unintended behavior.  So in this case the SQL Server on a particular host might be merged with a duplicate SQL Server on a different host.  This might cause the endpoint in the relationship to be missing.

 

If the SQL Server is not in a cluster or you run the Merge Clustered Software job and the issue still occurs, it is suggested to open a Support ticket to further investigate the issue encountered.

"HP Support
If you find this or any post resolves your issue, please be sure to mark it as an accepted solution."

Click the KUDOS star on the left to say 'Thanks'
Labels (1)
Tags (1)
0 Likes
The opinions expressed above are the personal opinions of the authors, not of Micro Focus. By using this site, you accept the Terms of Use and Rules of Participation. Certain versions of content ("Material") accessible here may contain branding from Hewlett-Packard Company (now HP Inc.) and Hewlett Packard Enterprise Company. As of September 1, 2017, the Material is now offered by Micro Focus, a separately owned and operated company. Any reference to the HP and Hewlett Packard Enterprise/HPE marks is historical in nature, and the HP and Hewlett Packard Enterprise/HPE marks are the property of their respective owners.