Oracle Database / Multitenant, Patching & Deployment
Map Oracle services to PDBs before correcting a descriptor
A valid service can point at a different PDB than the application expects. Inspect its configured container association.
Environment and inputs: Oracle Database 19c baseline · SQL*Plus-compatible SQL unless RMAN, DGMGRL, ADRCI or a host shell is specified. Check release, patch level, edition and container first.
Start with this diagnostic
Use the stated SQL, RMAN, DGMGRL or host shell and replace sample names with approved targets. DBA and V$ views need authorized catalog access in the correct container. Do not grant broad privileges for an example.
SELECT name, network_name, pdb FROM dba_services ORDER BY name;
Read the result
The service metadata describes configured associations in the queried context. Active placement and listener registration need separate verification.
Resolve and verify
Compare the application's service with the intended PDB and managed service policy. Correct the mapping or descriptor through the responsible DBA or cluster owner.
Operational precautions
Do not reuse a default administrative service as a replacement for a managed application service.