Re: ORA-12223

From: Just Visting <guest_at_example.com>
Date: Sat, 17 Jul 1999 17:10:43 GMT
Message-ID: <3790b822.14672537@news>

Thanks for trying but PROCESS=100 & there were only 12 - 18 sessions in the database at the time. This system & Oracle have been running fat, dumb & happy for many months without any recent configuration change. I swear that in the past this system has had many more sessions than when the errors occurred.

12223, 00000, "TNS:internal limit restriction exceeded" // *Cause: Too many TNS connections open simultaneously. // *Action: Wait for connections to close and re-try.

WHAT/WHICH internal limit restriction was exceeded?

---

On Sat, 17 Jul 1999 09:55:24 -0700, "Yass Khogaly" <ykhogaly_at_us.oracle.com> wrote:

>Solution Description:
>=====================
>
>Check the processes parameter in the init<sid>.ora file. Processes should
>be
>set to the number of background processes plus one for each connection to
>the
>database.
>
>If the init<sid>.ora processes parameter seems fine, it might be necessary
>to
>increase the Unix kernel parameters for the maximum number of processes or
>users.
>
>The problem is sometimes fixed by setting TWO_TASK=p:
>
>Check the manual for the Unix operating system that you are using for the
>correct parameters. Care should be taken when modifying these parameters.
>Save a copy of the original file version before making changes.
>
>
>Solution Explanation:
>=====================
>
>An ORA-12223 can be a result of too many files or sockets opened
>simultaneously (or some other resource that has been depleted).
>
>Regards
>
>"The Views expressed here are my own and not necessarily those of Oracle
>Corporation"
>
>Just Visting <guest_at_example.com> wrote in message
>news:378fb23d.558483_at_news...
>> Today a number of folks got a rash of the ORA-12223
>> error messages. I don't like the suggested action of
>> wait until later & try again. This system is not using
>> MTS. It is a Solaris V2.6 running Oracle V7.3.4.0.1
>> I am/was unaware of any type of limit involing TNS.
>>
>> What can be done to minimize the chances in the future
>> of getting this error message?
>
>
Received on Sat Jul 17 1999 - 12:10:43 CDT