RE: Weird listener behavior (9.2.0.4)

From: Goulet, Dick <DGoulet_at_vicr.com>
Date: Mon, 26 Apr 2004 11:36:23 -0400
Message-ID: <4001DEAF7DF9BD498B58B45051FBEA6506D991@25exch1.vicorpower.vicr.com>

Stephane,

        It appears that we have found the problem, which even OTS missed. Like = I stated in the original message, I had built a new database instance = over the weekend. Now, how many of you copy from one instance to = another when creating new, especially things like init.ora files? Well, = I did & I missed a parameter called "instance_name". Therefore I ended = up with two instances having the same "name". The default is the SID, = which is older version behavior & consequently I never had it in an = init.ora file. Well in 9i it's there & I missed it. Thankfully it's a = changeable parameter, just needs an instance restart. Problem fixed.

Dick Goulet
Senior Oracle DBA
Oracle Certified 8i DBA

-----Original Message-----
From: Stephane Faroult [mailto:sfaroult_at_oriole.com] Sent: Monday, April 26, 2004 8:51 AM
To: oracle-l_at_freelists.org
Subject: Re: Weird listener behavior (9.2.0.4)

"Goulet, Dick" wrote:

>=20

> To All,

>=20
> I've some really weird behavior coming form the Listener on =
one of our =3D
> production boxes. To be fair we did add another instance to this box =
=3D
> over the weekend. But once the listener is started and I try to =
connect =3D
> to "franklin4", which is an old instance, I get connected instead to =
=3D
> "franklin7" which is the one that just got added. Now this is also =
one =3D
> of 5 instances on the server, but I still can't figure out why for the =
=3D
> first 5 minutes that the listener is up it connects one to the right =
=3D
> instance and then starts messing up. I'm appending our listener.ora =
=3D
> file just in case someone can find a flaw in my ways.

Dick,

   I don't think that it's a matter of number of instances, I have known a development box with over 40 ...
I don't see anything shocking in your listener.ora file. I infer, possibly wrongly, from your having prespawned processes that you are using dedicated servers. Since it starts properly, it means that the listener connects a new session to the proper pre-spawned process. It should be interesting to check whether you have the same behaviour when you have MORE sessions than prespawned processes - or trying without any prespawned process.
Intuitively, I'd rather think of a problem on the client side - some corruption bringing the client to talk to the wrong port. Have you tried tracing ?

--=20
Regards,

Stephane Faroult
Oriole

---

Please see the official ORACLE-L FAQ: http://www.orafaq.com

---

To unsubscribe send email to: oracle-l-request_at_freelists.org put 'unsubscribe' in the subject line.

--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------
----------------------------------------------------------------
Please see the official ORACLE-L FAQ: http://www.orafaq.com
----------------------------------------------------------------
To unsubscribe send email to:  oracle-l-request_at_freelists.org
put 'unsubscribe' in the subject line.
--
Archives are at http://www.freelists.org/archives/oracle-l/
FAQ is at http://www.freelists.org/help/fom-serve/cache/1.html
-----------------------------------------------------------------

Received on Mon Apr 26 2004 - 10:34:35 CDT