Oracle instance CI duplication on discovery

[cyked]

We're seeing issues with multiple CIs representing a single oracle instance.   Normally you see duplicate CI creation when something like the params on the running process classified change.   Using process handlers addresses this.

However, what I see on the ora_pmon oracle instance running process records, there are NO command or paramater information recorded.   Currently I can't compare the current actively discovered/updated oracle instance to the "pervious" one because the difference in creation between the two is > 30 days and the running process record of the "previous" CI has already been nuked after being "absent" for over 30 days.    

Does anyone else have this issue?   I'm not finding what discovery identification is finding different in the existing CI record/running process record to create a new CI.

[PeterWiles]

Is it PRB609894 which is fixed in Patch 7?

http://wiki.servicenow.com/index.php?title=Release:Fuji_Patch_9_Hot_Fix_1#gsc.tab=0

Pete

[cyked]

I think not.   That problem is an issue with multiple rels between listener CIs and the oracle instances.

[Valor1]

Then it's most likely a bug if it's happening out-of-box, and you should submit a HI ticket.

If you do submit a ticket, do you mind replying with what they say?

[cyked · Accepted solution]

Ticket was updated today.   Tech chalked it up to potentially being system upgrades/patches as the issue.   Recommended removing the duplicates and moving on.