Oracle Database / Accounts, Security & Access
Inspect inherited password policy before changing one account
A profile limit may display DEFAULT rather than a concrete value. Resolve inheritance before deciding whether the account policy is wrong.
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 profile, resource_name, limit FROM dba_profiles WHERE resource_type = 'PASSWORD' AND profile IN ('APP_PROFILE','DEFAULT') ORDER BY resource_name, profile;Read the result
Compare the assigned profile's limits with DEFAULT where inheritance applies. The account may not use APP_PROFILE, so verify its assignment separately.
Resolve and verify
Review lockout, lifetime and reuse behavior with the identity owner. Adjust a dedicated profile only when the approved application requirement justifies it.
Operational precautions
Do not alter DEFAULT for one application without assessing every account inheriting that setting.