Oracle Database / Connections & Oracle Net
Understand why tnsping succeeds while SQL login fails
A listener probe and a database login exercise different layers. Treat probe success as a starting point rather than proof of full database availability.
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.
tnsping APPDB
sqlplus /nologRead the result
Use the client utility to inspect resolution, then open SQL*Plus without credentials on the command line. Connect interactively to the approved service when prompted through your normal authentication method.
Resolve and verify
Compare the real login error with the resolved descriptor and service registration. Route authentication failures to the identity owner and handler failures to the DBA.
Operational precautions
Do not include a password in a scripted connect string. Driver-specific behavior may require reproducing with the actual application client.