Oracle Database / Operations & Incident Response
Distinguish an enabled constraint from validated historical data
A constraint can enforce new work while existing rows have not been validated. Inspect status and validation state when reconciling data quality.
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 owner, constraint_name, table_name, constraint_type, status, validated FROM dba_constraints WHERE owner = 'APP_OWNER' AND table_name = 'APP_ORDERS';Read the result
ENABLED and VALIDATED describe different aspects of enforcement. NOVALIDATE requires careful interpretation of existing data and the specific constraint type.
Resolve and verify
Compare the state with the approved load or maintenance process. Check and repair legacy violations before planning a controlled validation.
Operational precautions
Do not disable constraints or claim all historical rows are valid based only on ENABLED.