04-22-04, 06:33 #1Registered User
- Join Date
- Apr 2004
Unanswered: Urgent - 220.127.116.11.0 listener dies periodically on Solaris
I've installed Oracle 9i R2 (18.104.22.168.0) running on Solaris. Started the 9iR2 listener on default 1521 port which listens for 9i DB and 8i DB instances on same box.
Listener stops automatically without writing something exeptional to listener.log/listener.trc periodically. I've to monitor it manually & start it once again when it goes for a walk.
I've gathered from old posts that mts_* parameters in init.ora cause it to stop. I've created pfile from spfile (9i DB) which don't have single mts_* parameter. But my 8i DB init.ora has just one entry "
mts_dispatchers = "(PROTOCOL=TCP)(PRE=oracle.aurora.server.SGiopServ er)"".
Why is it happening so? What is the root cause of it?
Does 9i listener really have problem with mts_* in parameter file?
Whats the relationship between mts_* parameters & DEDICATED/SHARED server in tnsnames.ora?
What is/are the solution(s)/work around(s) get rid of it?
Thanks in advance.
04-22-04, 11:10 #2Registered User
Provided Answers: 1
- Join Date
- Aug 2003
- Where the Surf Meets the Turf @Del Mar, CA
Try to set the init.ora parameter INSTANCE_NAME. If this parameter is not set each instance registers in an endless loop. The listener may hang or die.
Also the standard answer from Oracle would be to upgrade to V22.214.171.124
and see if the problem still exists. ;-)You can lead some folks to knowledge, but you can not make them think.
The average person thinks he's above average!
For most folks, they don't know, what they don't know.
Good judgement comes from experience. Experience comes from bad judgement.