Re: Starting Oracle Net Listener...forever!? Oracle XE
Date: Thu, 5 Aug 2010 11:06:32 +0200
Message-ID: <4c5a7f28$0$17085$65785112_at_news.neostrada.pl>
My connect string is:
jdbc:oracle:thin:_at_localhost:1521:XE (its java aplication runing on server).
tsnspinf for localhost tell :
Used HOSTNAME adapter to resolve the alias
Attempting to contact
(DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=TCP)(HOST=127.0.0.1)(PORT=1521)))
OK (0 msec)
tnsping for address 192.168.1.251 (server adddress) :
Used HOSTNAME adapter to resolve the alias
Attempting to contact
(DESCRIPTION=(CONNECT_DATA=(SERVICE_NAME=))(ADDRESS=(PROTOCOL=TCP)(HOST=192.168.1.251)(PORT=1521)))
OK (0 msec)
but tns for service name XE failed:
Used TNSNAMES adapter to resolve the alias
Attempting to contact (DESCRIPTION = (ADDRESS = (PROTOCOL = TCP)(HOST =
hpserwer)(PORT = 1521)) (CONNECT_DATA = (SERVER = DEDICATED)
(SERVICE_NAME = XE)))
and hangs forever.
Uzytkownik "joel garry" <joel-garry_at_home.com> napisal w wiadomosci
news:c9e03240-df40-4892-885f-87d2d5ea15de_at_y32g2000prc.googlegroups.com...
On Aug 4, 6:33 am, "CS" <c..._at_gryftechnologia.com> wrote:
> Hi
>
> I reinstalled my database Oracle XE and now when I run it
> /etc/init.d/oracle-xe start,
> It hangs for a few minutes on : "Starting Oracle Net Listener... " and
> when
> trying to connectto database i get ORA-12505: TNS: listener could not
> resolve SID given in connection description.
>
> Any ideas ?
$ oerr ora 12505
12505, 00000, "TNS:listener does not currently know of SID given in
connect descriptor"
// *Cause: The listener received a request to establish a connection
to a
// database or other service. The connect descriptor received by the
listener
// specified a SID for an instance (usually a database instance) that
either
// has not yet dynamically registered with the listener or has not
been
// statically configured for the listener. This may be a temporary
condition
// such as after the listener has started, but before the database
instance
// has registered with the listener. // *Action: // - Wait a moment and try to connect a second time. // - Check which instances are currently known by the listener byexecuting:
// lsnrctl services <listener name> // - Check that the SID parameter in the connect descriptor specifies // an instance known by the listener. // - Check for an event in the listener.log file.
Watch the case of the service name, and the ports you use, too.
What connect string are you using? My guess is you wound up with a different SID than you had before.
Do the appropriate ps on your system to see all processes, grepping for lsnr, in case you managed to wind up with multiple listeners somehow. Also grep for dbw, in case you wound up with multiple instances somehow. Or none at all.
What does tnsping tell you?
jg
-- _at_home.com is bogus. “This is John, I’m a little too depressed to take your call today. Please leave your message at the gunshot.” http://www.nytimes.com/2010/07/28/arts/design/28callahan.htmlReceived on Thu Aug 05 2010 - 04:06:32 CDT