> ## Documentation Index
> Fetch the complete documentation index at: https://docs.serval.com/llms.txt
> Use this file to discover all available pages before exploring further.

# Oracle Enterprise Manager

> Connect Oracle Enterprise Manager target inventory to Serval.

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 direct relationships as external assets.

## Beta requirements

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](https://docs.oracle.com/en/enterprise-manager/cloud-control/enterprise-manager-cloud-control/24.1/emrest/APIOverview.html).

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, details/properties, and relationship health checks before enabling the inventory workflow. 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** to sync database, RAC, and PDB target snapshots. Each external asset is keyed by its OEM target GUID. The source data includes target details, properties, direct relationships, and RAC members. 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](/sections/self-hosting/private-network-access).

The workflow fails when a required topology request fails. It does not treat unavailable relationships as empty inventory. Validate RAC membership and repeat-sync identities during the pilot, and agree on missing-target handling before enabling a schedule.