2010-08-08

ORA-04030 (QERHJ hash-joi,kllcqas:kllsltba)

This is not an Oracle memory resource issue since
connecting via SQL*Net is using less PGA for the session than
a local connection which is successful.


Client Connection Fails with ORA-04030 (QERHJ hash-joi,kllcqas:kllsltba) [ID 470604.1]

Modified 24-JUL-2010     Type PROBLEM     Status PUBLISHED

In this Document
  Symptoms
  Changes
  Cause
  Solution




Applies to:

Oracle Server - Enterprise Edition - Version: 10.2.0.1 to 10.2.0.4 - Release: 10.2 to 10.2
IBM AIX on POWER Systems (64-bit)
AIX5L Based Systems (64-bit)

***Checked for relevance on 25-Jul-2010***

Symptoms

   An Oracle statement can fail with the error ORA-04030 (QERHJ hash-joi,kllcqas:kllsltba) when it is executed from a SQL Net client .
   However, the same request is running fine when we launch it from the Unix environment ( local connection).

Changes

 The error in this case is an AIX platform specific issue and it occurs because of an OS resource limitation. 

Cause

   The system may be reaching its Maximum number of PROCESSES allowed per user, or maxuproc.
   Depending on what maxuproc is set to (default is 40), if a user has already forked a number of processes equal to maxuproc, the system will not allow that user to fork any more processes.
   The MAXUPROC defines the maximum number of processes per user. The oracle user typically needs to be allowed to create a lot of processes as the listener will spawn a process for every connection (dedicated server).

Solution

 Increase the kernel parameter MAXUPROC to 8192 and restart the listener.                                  
The OS commands in order to find the current maxuproc value and change it :                                       
-Display:   lsattr -E -l sys0 -a maxuproc 
-Change:    chdev -l sys0 -a maxuproc=NewValue

 Change takes effect immediately and is preserved over boot.If value is reduced, then it goes into effect only after a system boot. 









Niciun comentariu:

Trimiteți un comentariu