TNS LISTENER Problem - Need Help [message #144334] |
Wed, 26 October 2005 01:35 |
kvjai
Messages: 6 Registered: October 2005 Location: Chennai
|
Junior Member |
|
|
Hi guys,
Error Mesg: ora-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor
Few Days Back due to power failure Server got shutdown Abnormally. After that Listener Error Mesg was coming.
Activities Done...
1. Listener was deleted and Reconfigured.
2. Checked the status of Listener using LSNRCTL Command(Start / Stop / Status )
3. Added the DB entries to listener.ora.
4. Listener Service for DB was started and working fine.
Still was not able to connect to DB,
1. Tried to Connect to DB thru EM, but failed. Used logins like System,<User - DBA Privilege>,scott,<Normal User>. But did not connect to Database
2. When used sysdba login in EM got connected to DB and after that everything is working fine.
Meanwhile restarted the server several times.
Still confused and want to know the reason...
What was the problem ?
How it suddenly started working ?
Why got connected to db when SYS Login used ? while other logins failed ?
Please help
Regards
Vijai K
|
|
|
Re: TNS LISTENER Problem - Need Help [message #146657 is a reply to message #144334] |
Fri, 11 November 2005 17:23 |
sunil_v_mishra
Messages: 506 Registered: March 2005
|
Senior Member |
|
|
hi,
We you make changes with listener it always take time to connect
but as per you error message
Error Mesg: ora-12514: TNS:listener could not resolve SERVICE_NAME given in connect descriptor
you have to set your sid
oracle_home\bin>set ORACLE_SID=SID
error message show that in tnsnames.ora service is not resolved
or listener is not started.
Regards
Always Friend Sunilkumar
|
|
|
Re: TNS LISTENER Problem - Need Help [message #146823 is a reply to message #144334] |
Mon, 14 November 2005 01:35 |
ramsat
Messages: 49 Registered: November 2005
|
Member |
|
|
it happens some time like that.
next time when u struck with the problem use ip address and not the system name when configuring TNS names .
if the problem persists delete the database node from the database tree of EM.
and again create the database node using OEM. it will work fine
|
|
|