Merry Christmas & Happy 2027! Less downtime. More good times. Celebrating 13 years of sorlavit.com
Skip to content
Sorlavit KimIT Support, Network & Infrastructure Services Let’s talk

ปุ่มแปลไทยจะเปิดบทความผ่าน Google Translate เพื่อแปลอัตโนมัติ โดยคงโค้ดและคำสั่งไว้ตามต้นฉบับ

Oracle Database / Multitenant, Patching & Deployment

ORA-65096: distinguish common users from PDB-local users

A user-creation script intended for a PDB may be executed in the CDB root and fail common-user naming rules.

Compiled for Sorlavit Kim · Published · Updated · 1 min read

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 SYS_CONTEXT('USERENV','CON_NAME') AS con_name FROM dual;

Read the result

The target container helps determine whether the script is trying to create a common or local identity. Naming rules do not replace the identity-design decision.

Resolve and verify

Run the approved local-user deployment in the intended PDB, or design a properly authorized common user if that is actually required.

Operational precautions

Do not set hidden script parameters or bypass common-user rules to make a deployment run in the wrong container.

Source & further reading

Oracle Error Help — ORA-65096

Independently written summary reviewed on 2026-11-01. The example illustrates a possible application; it is not a client case study.

Share this article

Back to all articles