Oracle Database / Connections & Oracle Net
ORA-01017: verify the account and service before resetting credentials
Invalid logon can reflect a wrong secret, wrong target database or unexpected authentication configuration. First establish which service and account the application is using.
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','DB_NAME') AS db_name, SYS_CONTEXT('USERENV','CON_NAME') AS container_name FROM dual;Read the result
Run from a known authorized connection to confirm the intended target. This does not validate the failing account's password.
Resolve and verify
Compare the application's username, secret source and PDB service with the approved deployment. Correct the relevant secret reference and perform a single controlled login test.
Operational precautions
Avoid repeated retries that may lock the account. Never print, paste or store a production password in troubleshooting output.