OracleInstance & database
Listener status and services (lsnrctl)
What the listener is doing and which services it knows about, from the database server. Then test the path from a client machine. Pairs with Listener registration and services.
Not yet verified. How scripts are tested
1# On the database server, as the listener owner (oracle, or grid on Grid Infrastructure)2lsnrctl status3lsnrctl services4 5# With Grid Infrastructure6srvctl status listener7srvctl status scan_listener8 9# From a client machine: name resolution, then the network path10tnsping <alias>11nc -vz <db_host> 1521Run these at the operating system prompt.
Open in denrepoRelated tool: Connection string builder
Helps with
- ORA-12505: TNS:listener does not currently know of SID given in connect descriptor
- ORA-12514: TNS:listener does not currently know of service requested in connect descriptor
- ORA-12541: TNS:no listener
More Oracle scripts: Instance & database
- Instance status on every nodeHost, instance, version, status, whether logins are allowed, startup time and archiver state for every instance. A quick RAC-wide check after a…
- Working with the spfileShows which spfile the instance is using, where parameter files live and the order Oracle searches for them, and what SCOPE = MEMORY, SPFILE and BOTH…
- Database and instance overviewOne row per instance: host, version, uptime, role, open mode, archive log mode and whether it's a CDB. The first thing to run when you land on an…
- Non-default initialization parametersEvery parameter that has been changed from its default. Handy for comparing two databases or documenting a build.
- Processes and sessions against their limitsCurrent and peak usage of processes, sessions and transactions since startup. A PEAK % near 100 means the next connection storm will hit ORA-00020.
- Installed components and their statusEverything in DBA_REGISTRY. Anything not VALID after a patch or upgrade needs attention before you hand the database back.