tag:blogger.com,1999:blog-21236865.post131745457549292475..comments2009-12-15T21:41:41.183-07:00Forbrichnoreply@blogger.comBlogger4125tag:blogger.com,1999:blog-21236865.post-69968682272944659672009-12-15T21:05:32.935-07:002009-12-15T21:05:32.935-07:00you have a nice site. thanks for sharing this valuable resources. keep it up. anyway, various kinds of ebooks are available here<br /><br />http://feboook.blogspot.comAnonymousnoreply@blogger.comtag:blogger.com,1999:blog-21236865.post-13131757433522179622008-06-03T13:07:00.000-06:002008-06-03T13:07:00.000-06:00dude, you totally just saved my bacon. Awesome! It turns out my tnsnames.ora file look alright, but in fact the listener had been configured to listen dbinstancename1, but the tnsnames.ora was referencing dbinstancename1.orafarm.mydomain.tld<BR/><BR/>removed the orafarm.mydomain.tld and we're good. <BR/><BR/>Great post.Matt!http://mattsprinsky.com/blognoreply@blogger.comtag:blogger.com,1999:blog-21236865.post-56337749090755724162008-03-28T21:21:00.000-06:002008-03-28T21:21:00.000-06:00I agree with your comments - they are good points. My objective was to get the troubleshooting process started, not hit every combination.<BR/><BR/>For example:<BR/><BR/>You mention that 12514 means that a listener is running - but is it the right one? <BR/><BR/>You also mention 'odd setup on the server'. <BR/><BR/>But 'odd setups' can and do often happen in a DHCP environment - several different laptops with Oracle database and listener and after reboots, the laptops trade hostnames and IP addresses. (I see that regularily, especially in training centers.)Forbrichhttp://www.blogger.com/profile/16839603129930136268noreply@blogger.comtag:blogger.com,1999:blog-21236865.post-45263951421676871262008-03-21T02:38:00.000-06:002008-03-21T02:38:00.000-06:0012514, 00000, "TNS:listener does not currently know of service requested in connect descriptor"<BR/>Nitpicking here, but:<BR/>- if the listener does not run, you cannot get a TNS-12514 - the fact you get it means a listener is running.<BR/>- if tnsnames.ora on the client has the wrong port number, you will not reach the listener, and this error cannot occur (OK - maybe another listener on the same machine, but that would be an odd setup on the server)<BR/>- default domain will not resolve anything, it would cause the error to be tns-12154 (same numbers, different sequence): 12154, 00000, "TNS:could not resolve the connect identifier specified"<BR/><BR/>One tip: if your servicename on the listener is different (e.g. it has a domain concatenated) from what is specified on the client, you could resolve this by specifying the global_name parameter in listener.ora (when using a SID list in listener.ora, of course)Frankhttp://www.blogger.com/profile/07830428804236732019noreply@blogger.com