RE: Is listener working for every database
- From: "TJ Kiernan" <tkiernan@xxxxxxxxxxx>
- To: <Joel.Patterson@xxxxxxxxxxx>, <oracle-l@xxxxxxxxxxxxx>
- Date: Wed, 9 Feb 2011 10:10:12 -0600
How about using a universally known password instead, such as
scott/tiger? If you have the schema created & locked, you'll get
ORA-28000: the account is locked. Any other response = something is
wrong.
Thanks,
T. J.
The information contained in this message is privileged and confidential
information intended only for the use of the individual or entity
identified above. If the receiver of this message is not the intended
recipient, you are hereby notified that any dissemination, distribution,
use or copying of this message is strictly prohibited. If you have
received this message in error, please immediately notify the sender by
replying to his/her e-mail address noted above and delete the original
message, including any attachments. Thank you.
From: oracle-l-bounce@xxxxxxxxxxxxx
[mailto:oracle-l-bounce@xxxxxxxxxxxxx] On Behalf Of
Joel.Patterson@xxxxxxxxxxx
Sent: Wednesday, February 09, 2011 10:03 AM
To: oracle-l@xxxxxxxxxxxxx
Subject: Is listener working for every database
All oracle versions, solaris 9,10. No ASM instance, so one
listener/oracle_home.
Back in the day, we had a couple scripts set up that would cycle through
the databases and log in to an account using Sqlplus. This would tell
us that the database was up and the listener was up and working as well.
If not, then we would be notified.
Today, there is EM to name one method, but I may have a short term
requirement to manually check again, and perhaps this time without using
a password that is plain text in any file including the script. The
script would be executed from cron by oracle user.
Instead of creating an oracle account with only create session privilege
on every database:
I can cycle through the databases and log in as sys / as sysdba, and see
that the database is up without using a password. I can also cycle
through the listeners using lsnrctl and I suppose check the status or
something, OR grep for a ps for the tnslsnr listener name - thus
trying to circumvent the password issue.
But does that tell me the same thing as actually logging into each
database using the listener? Discarding the idea that a database
service name could have been 'left out' of the listener.ora file -
because these are production databases and that is not likely, is there
a better idea?
Just checking for feedback.
Joel Patterson
Database Administrator
904 727-2546
Other related posts:
