Discovery creates only cmdb_ci_db_ora_instance CIs, not cmdb_ci_database CIs
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-03-2018 05:07 AM
Hello!!
Discovery creates only oracle instances (cmdb_ci_db_ora_instance) CIs, not the dababase server itself (cmdb_ci_database). I come from BMC discovery wotld where both were created with a relationship (a database server may serve several db instances)
-Is it inherited from legacy
-Or is there an option to activate to discover them too.
-Any lack/benefit if trying to discover them?
Honestly, I'm more open to let it as it runs currently and hide the modules, but my mnager is curious.
Best regards
Cedric

- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-03-2018 05:57 AM
Hi cedriccreton,
I think Oracle databases are registered as Oracle Database Catalogs (cmdb_ci_db_ora_catalog).
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-03-2018 06:29 AM
Hello Cedric,
Out of the box the pattern doesn't discover all the schemes that are running on an instance. If you are using Service Mapping a schema will be created if passed into the entry point but it doesn't actually do any querying for it. Erik is correct that they would go in the oracle db catalog table and it would be representing the schema that would be used.
I once did a probe/sensor to pull this back and to fill the db catalog table for oracle and it required running a SQL statement to pull it out but that was all custom. I hope this helps.
- Mark as New
- Bookmark
- Subscribe
- Mute
- Subscribe to RSS Feed
- Permalink
- Report Inappropriate Content
‎09-18-2019 06:23 AM
Has anything changed with Mardrid on New York