Quote Originally Posted by PAVB
1- You probably already did it but just to be sure, don't forget to check "Note 233869.1 Diagnosing and Resolving ORA-4030 errors".

2- Be sure you set ALL unlimited values for both -ha and -sa.

3- If your offending code relies in bulk collect, try the code without it. In a 10g environment -even after working a TAR for two month- our only practical solution was to get rid of bulk collect to avoid the error.

PAVB

Thanks for your prompt reply.


1- Yes I went through 233869.1 Note id, Made some changes also but no success, “There can be issues with other OS parameter settings such as maxuproc” , I am not sure how oracle link 4030 with Maxuproc process, Oracle not able to justified this….anyway my current setting for this parameter is 2048

2- Hard ulimit and soft ulimit shows different values but our SA say that this is maximum and we cant go beyond this, Everything is set unlimited? Any suggestion on this from your side?

abc:/optware/oracle$ ulimit -Ha
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) unlimited
stack(kbytes) 4194304
memory(kbytes) unlimited
coredump(blocks) unlimited
nofiles(descriptors) unlimited

abc:/optware/oracle$ ulimit -sa
time(seconds) unlimited
file(blocks) unlimited
data(kbytes) 16777216
stack(kbytes) 4194304
memory(kbytes) 16777216
coredump(blocks) 2097151
nofiles(descriptors) unlimited


3) I had open STR number of times, every time I got different answer....but finally I got only one answer.....apply latest patches....I did that also.......but still problem...is same....