Duplicate records in cmdb_ci_db_ora_instance class.SummaryISSUE: ACC Visibility is discovering wrong Oracle Instances:Oracle database instances are getting discovered as 'Oracle Instance@<Host name>'This is causing duplicate CI to be created in the Oracle Instance table. SOLUTION AND ANALYSIS: ACC-V will gather information on running processes, and then using the ip-based discovery process classification records, make matches and create Application CIs. The naming convention is simply "<table label of application CI class>@hostname", which is not in line with how Discovery names them in general, or how specific application patterns name them. This breaks the OOTB identification rules, which rely on unique names for many applications, plus other attributes such as Oracle SID, that ACC does not collect. This naming of the application CI is different to how IP-based Discovery process classification, or Discovery Patterns would name the CI. If the name is not overridden by a application specific pattern, then Discovery defaults to <process classifier record Name>@<hostname of the host CI>" . If a Pattern is involved, the naming convention will be specific to that pattern. e.g. Oracle pattern will be "<Oracle instance SID>@<hostname of the host CI>", and the response for this is often to have unique names for multiple instances of the same software installed and running on the same host. If this is not done, as is the case with ACC currently, then you can end up with duplicate application CIs being created with different names, or the same single CI being updated multiple times for multiple different running processes. This is related to PRB1595057: https://support.servicenow.com/problem.do?sys_id=df71ae62db859550904fa9fb1396199c&sysparm_view=&sysparm_domain=null&sysparm_domain_scope=null&sysparm_nostack=yesThe issue is fixed in ACC-F 3.3.1 , so upgrade the plugin "Agent Client Collector Framework" to the latest version and check if the duplicates are still being created through ACC.