Skip to main content
The Oracle Enterprise Manager integration reads database target inventory from a customer-hosted EM console. It supports the oracle_database, rac_database, and oracle_pdb target types and imports OEM target IDs and source data as external assets.

​
Beta requirements

Inventory only: Use Ingest Oracle EM Inventory Only for EM 13.5. It reads target lists, details and properties without calling the relationship or membership APIs. Confirm the exact release update and access to all three endpoints before use; Oracle introduced the REST API in 13.5 Update 7 and expanded target operations in Update 13. See the 13.5 API change log. Full topology: The full inventory workflow requires Oracle Enterprise Manager 24ai Release 1 Update 12 (24.1.0.12) or newer. Oracle introduced the relationship and membership APIs in that update; EM 13.5 and earlier 24.1 updates do not meet this workflow’s requirements. See Oracle’s API change log. This integration is in Beta. Confirm the exact update and complete a supervised inventory sync before scheduling it. Source-to-CMDB mapping requires validation against your Oracle data.

​
Connect

  1. Create an Enterprise Manager service account with read-only permission to the intended targets and their relationships. Validate access with this account; an administrator browser session does not verify the integration account.
  2. Enter the HTTPS console URL, username, and password in Serval. Use the console host and port, for example https://em.example.com:7802.
  3. If the console is on a private network, configure a worker that can reach it. The worker must trust the console’s TLS certificate.
  4. Run the connection, inventory and details/properties health checks before enabling either workflow. The relationship health check is required only for full topology on 24.1.0.12+. It will fail on an instance without that API; this does not block inventory-only sync. No visible database targets means inventory access has not been verified.
The integration only sends GET requests to the target inventory API. It does not modify Oracle targets or incidents.

​
Inventory sync

Install Oracle Database Inventory and select one ingestion workflow:
  • Ingest Oracle EM Inventory Only: target details and properties for database, RAC and PDB targets. Relationship and membership fields are omitted, and topologyCollection is not-collected. A RAC target is imported without its member list.
  • Ingest Oracle EM Targets: the full snapshot including direct relationships and RAC members; requires 24.1.0.12+.
Use inventory-only sync for attribute mapping. Leave relationship mappings disabled and preserve relationships owned by other sources; missing topology does not mean no relationships exist. Do not replace an existing full-topology ingestion with this starter without reviewing its mappings. The workflow does not create or clear CMDB relationships itself. Run a supervised sync with representative standalone database, RAC and PDB targets. Check all pages and repeat the sync to confirm stable identities before scheduling it. Each external asset is keyed by its OEM target GUID. Both workflows use the same OEM identities; only the full workflow collects topology. Review your EM instance’s target types, cloud or non-cloud scope, source properties, and hierarchy before mapping these assets into CMDB classes.

​
Troubleshooting

  • Login page instead of JSON: confirm the REST URL and that the EM account supports username/password API authentication through your console’s authentication setup.
  • 401 or 403: check the account credentials and target permissions.
  • 404 on relationships or members: confirm Update 12 or newer, the target GUID and visibility. Oracle also uses 404 for resources the account cannot see.
  • Network or certificate error: check DNS, the console HTTPS port and the executing worker’s CA trust. For private consoles, use private network access.
The full workflow fails when a required topology request fails. Both workflows fail on required inventory or property request errors. The full workflow does not treat unavailable relationships as empty inventory. Validate RAC membership for full topology and repeat-sync identities for either mode during the pilot, and agree on missing-target handling before enabling a schedule.