Thanks for the info, ulimit looks good and nothing is in the alert
log.
ulimit -a
core file size (blocks, -c) 0
data seg size (kbytes, -d) unlimited
file size (blocks, -f) unlimited
pending signals (-i) 1024
max locked memory (kbytes, -l) 3145728
max memory size (kbytes, -m) unlimited
open files (-n) 63536
pipe size (512 bytes, -p) 8
POSIX message queues (bytes, -q) 819200
stack size (kbytes, -s) 10240
cpu time (seconds, -t) unlimited
max user processes (-u) 557055
virtual memory (kbytes, -v) unlimited
file locks (-x) unlimited
On May 15, 9:24 am, Mladen Gogala <mgogala.SPAM_ME...._at_verizon.net>
wrote:
> On Mon, 14 May 2007 13:23:47 -0700, harvinder76 wrote:
> > Users are getting following errors on 1 of the database machine:
> > "Oracle.DataAccess.Client.OracleException ORA-04030: out of process
> > memory when trying to allocate 16396 bytes (koh-kghu call ,pmuccst:
> > adt/record)"
>
> The error here is: "out of process memory", which means that you
> have problems with the address space of the process. On Linux, you
> can increase the limits in /etc/security/limits.conf, if there are any.
> You can play with data segment size and address space size, both limits
> are in KB. You should first check whether there are any limits for user
> oracle bu logging into oracle and executing ulimit -a. Also, you should
> set overcommit_memory to 1, which will allow processes to allocate memory
> without having an adequate space on the swap partition first.
> The error "ORA-04030: out of process memory when trying to allocate 16396
> bytes (koh-kghu call ,pmuccst: adt/record)" simply means that a malloc
> call has failed. Also, check /var/log/messages on the server side, as well
> as $ORACLE_BASE/admin/$DB_NAME/bdump/alert_$ORACLE_SID.log
>
> --http://www.mladen-gogala.com
Received on Tue May 15 2007 - 13:35:42 CDT
