ORA-04030 And ORA-273XX Errors On HP-UX Itanium (Doc ID 2006587.1)

Last updated on AUGUST 14, 2016

Applies to:

Oracle Database - Enterprise Edition - Version 11.2.0.1 to 12.1.0.2 [Release 11.2 to 12.1]
HP-UX Itanium

Symptoms

Following memory related errors are reported in alert.log file during normal database operations:

Wed Apr 22 16:17:01 2015
Errors in file /oradata/bsmdb/data_files/admin/diag/rdbms/bsmdb/bsmdb/trace/bsmdb_ora_5693.trc  (incident=127173):
ORA-04030: out of process memory when trying to allocate 184 bytes (kxs-heap-b,kxsbb info)
Wed Apr 22 16:17:06 2015
Errors in file /oradata/bsmdb/data_files/admin/diag/rdbms/bsmdb/bsmdb/trace/bsmdb_ora_5251.trc  (incident=127997):
ORA-04030: out of process memory when trying to allocate 102984 bytes (QERHJ hash-joi,kllcqc:kllcqslt)
Incident details in: /oradata/bsmdb/data_files/admin/diag/rdbms/bsmdb/bsmdb/incident/incdir_128597/bsmdb_w002_6270_i128597.trc
............................
Process startup failed, error stack:
Wed Apr 22 16:19:19 2015
Errors in file /oradata/bsmdb/data_files/admin/diag/rdbms/bsmdb/bsmdb/trace/bsmdb_psp0_3571.trc:
ORA-27300: OS system dependent operation:fork failed with status: 12
ORA-27301: OS failure message: Not enough space
ORA-27302: failure occurred at: skgpspawn3
Process m002 died, see its trace file
Wed Apr 22 16:21:19 2015
Process startup failed, error stack:
Wed Apr 22 16:21:21 2015
Errors in file /oradata/bsmdb/data_files/admin/diag/rdbms/bsmdb/bsmdb/trace/bsmdb_psp0_3571.trc:
ORA-27300: OS system dependent operation:fork failed with status: 11
ORA-27301: OS failure message: Resource temporarily unavailable
ORA-27302: failure occurred at: skgpspawn5

 
The trace file does not show a process with high memory allocation:

*** 2015-04-22 16:18:07.386
=======================================
PRIVATE MEMORY SUMMARY FOR THIS PROCESS
---------------------------------------
******************************************************

*** 2015-04-22 16:18:08.661
PRIVATE HEAP SUMMARY DUMP
2346 KB total:
 1954 KB commented, 290 KB permanent

*** 2015-04-22 16:18:09.691
  103 KB free (0 KB in empty extents),
   1663 KB,   1 heap:    "session heap   "          
     82 KB,   1 heap:    "PLS PGA hp     "            64 KB free held

*** 2015-04-22 16:18:10.638
     74 KB,   1 heap:    "Fixed UGA heap "          
------------------------------------------------------
Summary of subheaps at depth 1

*** 2015-04-22 16:18:11.584
1896 KB total:
 1528 KB commented, 351 KB permanent
   17 KB free (0 KB in empty extents),

*** 2015-04-22 16:18:12.585
    408 KB, 381 chunks:  "kxsc: kkspsc0 2           "
    392 KB, 380 heaps:   "kxs-heap-p     "          
    388 KB, 379 heaps:   "kxs-heap-d     "          

*** 2015-04-22 16:18:13.597
     74 KB,   1 chunk:   "Fixed Uga                 "
     52 KB,   4 heaps:   "Alloc server h "          
     41 KB,  10 chunks:  "kxsFrame4kPage            "


 
However, the OS log file contains warnings for the problem period:

Apr 22 16:17:40 bsmdb sshd[22135]: error: openpty: Not enough space
Apr 22 16:17:40 bsmdb sshd[22176]: error: session_pty_req: session 0 alloc failed
Apr 22 16:17:40 bsmdb sshd[22176]: error: do_exec_no_pty: fork: Not enough space
........................
Apr 22 16:18:40 bsmdb sshd[1316]: error: fork: Not enough space
...................
Apr 22 16:18:43 bsmdb cimserver[1961]: fork failed
Apr 22 16:18:49 bsmdb cimserver[1961]: fork failed
..........................
Apr 22 16:19:20 bsmdb vmunix: Pid 21284 was killed due to failure in writing the signal context - possible stack overflow.

Cause

Sign In with your My Oracle Support account

Don't have a My Oracle Support account? Click to get started

My Oracle Support provides customers with access to over a
Million Knowledge Articles and hundreds of Community platforms