RE: found dead multi-threaded server
I encountered some problems also when we moved over from dedicated to MTS all of my problems it seem were being caused by the idle_time parameter in the profile when it was set to anything like 60mins or 120 mins, I would frequently get dead MTS-servers after disabling that no more problems I'm on 8.1.7.2 now on HP-UX 11.0 64 bit -Original Message- Sent: Tuesday, December 18, 2001 5:05 PM To: Multiple recipients of list ORACLE-L I've gotten these errors (most notably 16365) on numerous occasions and I'm running 8.1.7.0 I've also gotten this error on 8.1.6 with and without the patchset. The main cause of this error is a half-duplex protocol error and, according to Oracle, tends to be application related.See notes 155513.1, 300867.999 on metalink for more information. Since the upgrade has not fixed this for us, my guess is that it is an application problem (perl in our case). We only occasionally get them, but if you get them all the time, you may want to check your app. HTH, -Brian On Mon, 17 Dec 2001, prashast gujrati wrote: Hi Gurus, We have recently upgraded our DBs from old 7.3.2 version to 8.1.6.0 and have moved from dedicated to MTS. since then we are getting ORA-600s in alert.log of all the DBs with various first arguments some of which I'll list here : 15429, 15439, 16365, 16375, 17034, 17182, 17280, 17281, 17285, kohlnm120, kohcpi298 etc. These are the most frequent ones. Though the DBs are up and running these errors are being consistently logged in alert. None of the instances have crashed ever since we have upgraded. I've opened up a TAR on metalink and have been told that 8.1.6.3 patchset is to be applied. Now what I want to know is if others have also encountered these errors and if applying this patchset has solved the problems. If not then what are the other things to be done (I mean does moving to 8.1.7.3 will necessarily solve the problem ? We are reluctant as this will mean another period of downtime for the users...) Also what is the source of these errors ? Will moving into dedicated arch solve our problems ? (I somehow tend to trust this list more than Metalink !!) TIA, -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Brian Haas INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing). -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: david hill INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
Re: found dead multi-threaded server
I've gotten these errors (most notably 16365) on numerous occasions and I'm running 8.1.7.0 I've also gotten this error on 8.1.6 with and without the patchset. The main cause of this error is a half-duplex protocol error and, according to Oracle, tends to be application related.See notes 155513.1, 300867.999 on metalink for more information. Since the upgrade has not fixed this for us, my guess is that it is an application problem (perl in our case). We only occasionally get them, but if you get them all the time, you may want to check your app. HTH, -Brian On Mon, 17 Dec 2001, prashast gujrati wrote: Hi Gurus, We have recently upgraded our DBs from old 7.3.2 version to 8.1.6.0 and have moved from dedicated to MTS. since then we are getting ORA-600s in alert.log of all the DBs with various first arguments some of which I'll list here : 15429, 15439, 16365, 16375, 17034, 17182, 17280, 17281, 17285, kohlnm120, kohcpi298 etc. These are the most frequent ones. Though the DBs are up and running these errors are being consistently logged in alert. None of the instances have crashed ever since we have upgraded. I've opened up a TAR on metalink and have been told that 8.1.6.3 patchset is to be applied. Now what I want to know is if others have also encountered these errors and if applying this patchset has solved the problems. If not then what are the other things to be done (I mean does moving to 8.1.7.3 will necessarily solve the problem ? We are reluctant as this will mean another period of downtime for the users...) Also what is the source of these errors ? Will moving into dedicated arch solve our problems ? (I somehow tend to trust this list more than Metalink !!) TIA, -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: Brian Haas INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
found dead multi-threaded server
Hi Gurus, We have recently upgraded our DBs from old 7.3.2 version to 8.1.6.0 and have moved from dedicated to MTS. since then we are getting ORA-600s in alert.log of all the DBs with various first arguments some of which I'll list here : 15429, 15439, 16365, 16375, 17034, 17182, 17280, 17281, 17285, kohlnm120, kohcpi298 etc. These are the most frequent ones. Though the DBs are up and running these errors are being consistently logged in alert. None of the instances have crashed ever since we have upgraded. I've opened up a TAR on metalink and have been told that 8.1.6.3 patchset is to be applied. Now what I want to know is if others have also encountered these errors and if applying this patchset has solved the problems. If not then what are the other things to be done (I mean does moving to 8.1.7.3 will necessarily solve the problem ? We are reluctant as this will mean another period of downtime for the users...) Also what is the source of these errors ? Will moving into dedicated arch solve our problems ? (I somehow tend to trust this list more than Metalink !!) TIA, -- Please see the official ORACLE-L FAQ: http://www.orafaq.com -- Author: prashast gujrati INET: [EMAIL PROTECTED] Fat City Network Services-- (858) 538-5051 FAX: (858) 538-5051 San Diego, California-- Public Internet access / Mailing Lists To REMOVE yourself from this mailing list, send an E-Mail message to: [EMAIL PROTECTED] (note EXACT spelling of 'ListGuru') and in the message BODY, include a line containing: UNSUB ORACLE-L (or the name of mailing list you want to be removed from). You may also send the HELP command for other information (like subscribing).
