Per-process memory size limit

Hi,
Could someone tell me if there is a per proccess memory size limit in Solaris 8 (sparc)? Specifically I'm running a 420R with 4gigs of physical memory and 8gigs of swap. I have an application that is no longer able to get memory after it grows (to what appears to be) 2042megs.
In addition, is there a maxsize for core dumps? I have all of the limits turned off with ulimit when running the application.
Thanks!
Gus

No mention about it on other regional sites.. but on this one its Max. 2 GB..
http://www.nokiausa.com/find-products/phones/nokia-6085/technical-specifications
Read the Nokia recommendation too...

Similar Messages

How to increase the per-process file descriptor limit for JDBC connection 15

If I need JDBC connection more that 15, the only solution is increase the per-process file descriptor limit. But how to increase this limit? modify the oracle server or JDBC software?
I'm using JDBC thin driver connect to Oracle 806 server.
From JDBC faq:
Is there any limit on number of connections for jdbc?
No. As such JDBC drivers doesn't have any scalability restrictions by themselves.
It may be it restricted by the no of 'processes' (in the init.ora file) on the server. However, now-a-days we do get questions that even when the no of processes is 30, we are not able to open more than 16 active JDBC-OCI connections when the JDK is running in the default (green) thread model. This is because the no. of per-process file descriptor limit exceeded. It is important to note that depending on whether you are using OCI or THIN, or Green Vs Native, a JDBC sql connection can consume any where from 1-4 file descriptors. The solution is to increase the per-process file descriptor limit.
null

maybe it is OS issue, but the suggestion solution is from Oracle document. However, it is not provide a clear enough solution, just state "The solution is to increase the per-process file descriptor limit"
Now I know the solution, but not know how to increase it.....
pls help.

Error BI Apps HR and Fin full load - ORA-04030: out of process memory......

Hi Experts,
I loaded HR it went well, but now I am trying to load both HR and Financial Full load. I am getting below issue for some DAC tasks:
ORA-04030: out of process memory when trying to allocate 1049100 bytes (kxs-heap-w,kllcqgf:kllsltba)
Environment:
Source System:
Win server 2008 - 2 GB RAM; EBS R12.1.1.
Target System:
Windows Server 2008 32 bit (with /3G, /PEA switches enabled) – 4 GB RAM; obiee 10g;biapps 7.9.6.2;dac 10.1.3.4.1;Informatica PC 8.6.1 Hotfix 11;Oracle DB 11.1.0.7.
DAC Tasks that failed:
TASK_GROUP_Extract_GLLinkageInformation
SDE_ORA_GL_COGS_LinkageInformation_Extract
SDE_ORA_GL_AP_LinkageInformation_Extract
SDE_ORA_GL_AR_REV_LinkageInformation_Extract
SDE_ORA_GL_PO_LinkageInformation_Extract
All the above tasks are failing with above error.
Below are the memory parameters for BI Apps database:
SQL> show parameter target
NAME TYPE VALUE
archive_lag_target integer 0
db_flashback_retention_target integer 1440
fast_start_io_target integer 0
fast_start_mttr_target integer 0
memory_max_target big integer 820M
memory_target big integer 820M
pga_aggregate_target big integer 257374182
sga_target big integer 0
I also tested by increasing below parameters:
memory_max_target 2G
memory_target 2G
pga_aggregate_target 1G
sga_target 900M
But it didn’t work, same errors.
Please let me know how can I solve this issue. Thanks for your time.

The below text is from doc id, I've picked solution part
let me know updates
=====Start======================
Solution
NON-ORACLE SOFTWARE STEPS
1.If you have 4Gb or less of RAM, add more RAM to the 32-bit computer system (add another 4Gb or more, if possible).
2.Enable the /3GB in the BOOT.INI, see note:
Note 225349.1 Implementing Address Windowing Extensions (AWE) or VLM on Windows Platforms
3.If using MS-Windows Enterprise Edition, enable Physical Address Extensions (PAE) by adding the /PAE switch to the BOOT.INI, see note Note 225349.1.
NOTE: The Windows tool Perfmon should be used in ORA-4030 problems on Windows. Task Manager is not a reliable tool to investigate ORACLE.EXE process memory size.
ORACLE SOFTWARE STEPS
Steps for both Enterprise and non-Enterprise Editions of MS-Windows
1.Check for excessive INACTIVE sessions:
select sum(PGA_ALLOC_MEM) from v$process p, v$session s where p.addr = s.paddr and s.status = 'INACTIVE';
If this query returns a large value (i.e. several hundred Megabytes or even greater that 1 Gigabyte), then it is recommended that you automate the cleanup of INACTIVE sessions. To see how this works, see notes;
Note 151972.1 Dead Connection Detection (DCD) Explained
Note 159978.1 How To Automate Disconnection of Idle Sessions
Implement DCD & IDLE_TIME, by doing the following;
Set SQLNET.EXPIRE_TIME = x (minutes) in the Server SQLNET.ORA file,
Create a PROFILE with IDLE_TIME set, and assign it to users.
If you find that the processes remain with status SNIPED, then you will need to implement removal of those processes as well, see note:
Note 96170.1 Script for killing sniped sessions shadow processes
For more information, see Note 601605.1 A discussion of Dead Connection Detection, Resource Limits, V$SESSION, V$PROCESS and OS processes
2.Review Note 46001.1 and determine the pro's and con's of running ORASTACK against the ORACLE.EXE.
If appropriate, shut down the database, and run the following command in an MS-DOS window:
orastack oracle.exe 500000
Re-start the database.
Steps for Enterprise Editions of MS-Windows
Determine if using AWE would fit your database needs. This allows the Buffer Cache component in the SGA to be relocated above the 4Gb memory footprint for the ORACLE.EXE process. Since this configuration requires a virtual memory window to map memory allocations above the 4Gb memory area, this option fits best with database requirements for a 1G and up sized Buffer Cache. It would not be efficient to have a 400M Buffer Cache above the 4Gb memory footprint and yet allocate a 1Gb virtual memory window to map to that memory.
1.Decide on the size of the SGA, PGA requirements and AWE (default 1Gb), given 300Mb overhead for the ORACLE.EXE and the 3Gb memory limit (as per the BOOT.INI /3GB switch). Please note that the minimum AWE size depends on the number of CPU's, see note Note 225349.1.
- Grant OracleService<SID> the 'Lock Pages in Memory' system privilege at the operating system level, see Note 225349.1.
- If necessary, change the Address Windowing Extensions (AWE) size from the default 1Gb, see Note 225349.1.
- Adjust any of the other SGA memory settings; SHARED_POOL_SIZE, LARGE_POOL_SIZE, JAVA_POOL_SIZE & STREAMS_POOL_SIZE.
- Adjust the PGA memory setting, PGA_AGGREGATE_TARGET. NOTE: This is a target, so a decrease in this process will not directly affect the memory footprint of the ORACLE.EXE.
- Unset SGA_TARGET and/or MEMORY_TARGET (11g).
- Set USE_INDIRECT_DATA_BUFFERS=TRUE.
- Unset DB_CACHE_SIZE. Set DB_BLOCK_BUFFERS to the desired size (this will use memory above the 4Gb range).
2.Start the database.
Steps for NON-Enterprise Editions of MS-Windows
1.Decide on the size of the SGA and PGA, given 0.1Gb overhead for the ORACLE.EXE and the 3Gb memory limit (as per the BOOT.INI /3GB switch).
2.Adjust the SGA_TARGET and/or MEMORY_TARGET (11g), or use explicit settings for the SGA components and eliminate auto-tuning. NOTE: Advantages of auto-tuning are often minimal on Windows 32-bit due to memory limit issues.
3.Adjust the PGA memory setting, PGA_AGGREGATE_TARGET (optional on 11g). NOTE: This is a target, so a decrease in this process will not directly affect the memory footprint of the ORACLE.EXE.
4.Start the database.

Photoshop Mix, iOS-App on iPad mini, picture size limit?

Hello!
I tried out this App on my iPad mini RD with the latest iOS, but it denied to open most of my imported pictures.
Some pictures work, most pictures don´t open?!
All taken by Nikon D800 and imported on the iPad.
I don´t know where are the difference between the pictures?
Maybe there exists a limit for picture size?
Who can help?
Greetings
Dirk

Hi Dirk,
Sorry about the inconveniences. Due to the memory size limit of current iPads, PS mix decides to only support images smaller than 20 mega pixel.
Let me know if you have further questions regarding image size. Thank you very much for supporting PS mix.

Is it possible to config memory size for a process?

Dear experts,
I would like to control the memory size assigned for a process on Solaris 9. Can i config memory size assigned for process??
Many thanks,
Shun

You can use ulimit/limit to assign a bound on the amount of space that a process and its children can allocate.
I'm not sure if that's what you're asking though.
Darren

Changing process memory limit for Reserved roles in plan

Is there a way to set our own process memory limit ABOVE 1024 in a plan (which is the default) ? It will not let us make it larger than 1024 and this seems odd

Thanks for your response.
To answer your questions,
1. I'm using RTMP
2. FMS 4.0 out of the box
3. Didn't know I'd have this traffic volume. Just sort of happened.
Don't have 300,000 connections all the time. Most times only 100-1,000. But once in a blue moon a particular client wants to broadcast to really high numbers. I'll have to handle it somehow.
Let me simplify this to make it easier to answer.
Suppose I made an FMS chat app (not video) and passed the link to 300,000 people. Suppose I told them all to log on at 2:00 p.m. tomorrow and send a message. If they all did, would my FMS instance crash?
Suppose I then added something to the app. Suppose I added an interactive poll. The poll pops up a question for the users like this:
What's your favorite color?
A. Red
B. Blue
C. Green
When users answer the question, FMS relays the real time voting updates back to all the clients so they can watch the voting results tally as they happen.
When all the users vote, will that crash the FMS instance?
On your point about multiple FMS boxes, that sounds like it works for video streaming. Edge origin would permit the sharing of video streams across multiple servers. But how do you share and synchronize a "chat" or "poll" app in the same way. If I send a message to FMS box 1, how do the others get it?
Or is FMS not the best choice for non video apps (like chat and poll) in really high numbers?

Very large memory size in process window

I am new to the Mac OS X and in Windows, win explorer never takes any more than 100mb of memory in my processes window, why is it that when i am only surfing one site or no sites but safari is running on the dock, that my memory size is >256mb?! That is just a little to much memory for one program to be taking up considering I only have 512mb.

Hello Applesr4eva:
Welcome to Apple discussions.
This is a very good knowledge base article that discusses OS X memory utilization:
http://docs.info.apple.com/article.html?artnum=107918
Don't compare Windows with OS X. OS X uses sophisticated algorithms to manage both real and virtual memory resources. My advice to you would be to forget it unless you are having performance problems. I am running a G4 with 512 MB and it does not breathe hard unless I use processor intensive applications (rare for me in my home computing environment).
Barry

Max Character File Size Limit exceeded.The document is too large to process

Hi
I have made set on section on products in report.
the Reports contains around 50 products when im opening the report
in draft mode the following error is displayed
"Max Character File Size Limit exceeded.The document is too large to be proceesed by the server .Contact your business Objects Administrator."
can some body help me out how to increase my report character file size

Hi,
If you are using Business Objects XIR2, there is a performance parameter in the Web_Intelligence Report Server where you can increase the size of that file. The parameter is Maximun Character File Size. Go to the CMC>Server>server.Web_IntelligenceReportServer in the Properties tab you will see it.
Cheers,
Luigi

ORA 04030 Out of process memory error

Dear experts,
I know there are multiple discussions around this error and I have been reading through most of them in the past one week or so, but looks like we are running out of options or are missing the color altogether. Ok, we are getting ORA-04030 - out of process memory while allocating....while one of our batch process runs in the night. It simply tries to insert/update to a table. Our installation is 11.2.0.1.0 with no RAC configuration and on 64-bit AIX having 6 cores, 12 CPUs and 16 GB memory.
We have checked the Workarea_Size_Policy is set to be as Auto so Oracle decides how much memory to allocate to PGA automatically on run-time based on the demand. And based on the AWR report it doesnt look like we are anywhere near the country having a PGA-deficit!! I am attaching the AWR report in a word document here for your reference.
Also attached below are the configurations and the ulimit values.
IKBTRN1> show parameter workarea;
NAME                                 TYPE                             VALUE
workarea_size_policy                 string                           AUTO
oraipeikbtrn1:/home/oracle-> ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         unlimited
stack(kbytes)        4194304
memory(kbytes)       unlimited
coredump(blocks)     unlimited
nofiles(descriptors) unlimited
threads(per process) unlimited
processes(per user) unlimited
Now, nothing seems to have contributed to the out of process memory issue from Oracle standpoint. I would be happy to be proved wrong here, if I am wrong.
So, whats going wrong here? A possible memory leak which we cannot zero down to, a OS memory limit or something else?
Seeking expert's advise on this, and also sincerely appreciate your time in looking at this.
Thanks.
P.S - I am pasting the whole AWR report since there is no 'upload file' option here that I can see.
WORKLOAD REPOSITORY report for
DB Name     DB Id     Instance     Inst num     Startup Time     Release     RAC
IKBTRN1     54659199     IKBTRN1     1     06-Jun-11 02:06     11.2.0.1.0     NO
Host Name     Platform     CPUs     Cores     Sockets     Memory (GB)
oraipeikbtrn1.******.com     AIX-Based Systems (64-bit)     12     6          16.00
     Snap Id     Snap Time     Sessions     Cursors/Session
Begin Snap:     5952     26-Aug-11 03:00:48     34     2.0
End Snap:     5953     26-Aug-11 04:00:52     32     1.9
Elapsed:          60.07 (mins)
DB Time:          1.93 (mins)
Report Summary
Cache Sizes
     Begin     End
Buffer Cache:     1,056M     704M     Std Block Size:     8K
Shared Pool Size:     3,456M     3,456M     Log Buffer:     7,184K
Load Profile
Load Profile
     Per Second     Per Transaction     Per Exec     Per Call
DB Time(s):     0.0     2.0     0.02     0.02
DB CPU(s):     0.0     0.5     0.00     0.00
Redo size:     556.1     34,554.8
Logical reads:     151.4     9,407.6
Block changes:     1.9     119.8
Physical reads:     14.2     882.6
Physical writes:     9.5     590.4
User calls:     1.8     112.8
Parses:     1.5     93.7
Hard parses:     0.1     8.9
W/A MB processed:     -0.1     -6.9
Logons:     0.0     1.6
Executes:     1.9     115.4
Rollbacks:     0.0     0.0
Transactions:     0.0
Instance Efficiency Percentages (Target 100%)
Buffer Nowait %:     100.00     Redo NoWait %:     100.00
Buffer Hit %:     96.63     In-memory Sort %:     99.97
Library Hit %:     95.68     Soft Parse %:     90.49
Execute to Parse %:     18.74     Latch Hit %:     100.00
Parse CPU to Parse Elapsd %:     57.23     % Non-Parse CPU:     86.28
Shared Pool Statistics
     Begin     End
Memory Usage %:     85.72     85.76
% SQL with executions>1:     93.91     96.66
% Memory for SQL w/exec>1:     89.07     87.04
Top 5 Timed Foreground Events
Event     Waits     Time(s)     Avg wait (ms)     % DB time     Wait Class
DB CPU          29          24.66
db file scattered read     3,456     17     5     14.92     User I/O
db file sequential read     4,304     17     4     14.77     User I/O
direct path read temp     764     17     22     14.31     User I/O
direct path write temp     259     5     21     4.70     User I/O
Host CPU (CPUs: 12 Cores: 6 Sockets: )
Load Average Begin     Load Average End     %User     %System     %WIO     %Idle
1.39     1.37     0.2     0.2     0.2     99.6
Instance CPU
%Total CPU     %Busy CPU     %DB time waiting for CPU (Resource Manager)
0.1     20.5     0.0
Memory Statistics
     Begin     End
Host Mem (MB):     16,384.0     16,384.0
SGA use (MB):     4,704.0     4,352.0
PGA use (MB):     196.1     188.4
% Host Mem used for SGA+PGA:     29.91     27.71
Main Report
•     Report Summary
•     Wait Events Statistics
•     SQL Statistics
•     Instance Activity Statistics
•     IO Stats
•     Buffer Pool Statistics
•     Advisory Statistics
•     Wait Statistics
•     Undo Statistics
•     Latch Statistics
•     Segment Statistics
•     Dictionary Cache Statistics
•     Library Cache Statistics
•     Memory Statistics
•     Streams Statistics
•     Resource Limit Statistics
•     Shared Server Statistics
•     init.ora Parameters
Back to Top
Wait Events Statistics
•     Time Model Statistics
•     Operating System Statistics
•     Operating System Statistics - Detail
•     Foreground Wait Class
•     Foreground Wait Events
•     Background Wait Events
•     Wait Event Histogram
•     Wait Event Histogram Detail (64 msec to 2 sec)
•     Wait Event Histogram Detail (4 sec to 2 min)
•     Wait Event Histogram Detail (4 min to 1 hr)
•     Service Statistics
•     Service Wait Class Stats
Back to Top
Time Model Statistics
•     Total time in database user-calls (DB Time): 115.9s
•     Statistics including the word "background" measure background process time, and so do not contribute to the DB time statistic
•     Ordered by % or DB time desc, Statistic name
Statistic Name     Time (s)     % of DB Time
sql execute elapsed time     101.69     87.75
DB CPU     28.58     24.66
parse time elapsed     10.14     8.75
hard parse elapsed time     9.92     8.56
failed parse elapsed time     4.92     4.25
hard parse (sharing criteria) elapsed time     4.27     3.68
connection management call elapsed time     0.42     0.36
PL/SQL compilation elapsed time     0.34     0.30
PL/SQL execution elapsed time     0.18     0.15
sequence load elapsed time     0.00     0.00
repeated bind elapsed time     0.00     0.00
DB time     115.88
background elapsed time     86.01
background cpu time     5.06
Back to Wait Events Statistics
Back to Top
Operating System Statistics
•     *TIME statistic values are diffed. All others display actual values. End Value is displayed if different
•     ordered by statistic type (CPU Use, Virtual Memory, Hardware Config), Name
Statistic     Value     End Value
NUM_LCPUS     0
NUM_VCPUS     0
AVG_BUSY_TIME     1,260
AVG_IDLE_TIME     360,705
AVG_IOWAIT_TIME     534
AVG_SYS_TIME     483
AVG_USER_TIME     679
BUSY_TIME     16,405
IDLE_TIME     4,329,811
IOWAIT_TIME     7,284
SYS_TIME     7,092
USER_TIME     9,313
LOAD     1     1
OS_CPU_WAIT_TIME     503,900
PHYSICAL_MEMORY_BYTES     17,179,869,184
NUM_CPUS     12
NUM_CPU_CORES     6
GLOBAL_RECEIVE_SIZE_MAX     1,310,720
GLOBAL_SEND_SIZE_MAX     1,310,720
TCP_RECEIVE_SIZE_DEFAULT     16,384
TCP_RECEIVE_SIZE_MAX     9,223,372,036,854,775,807
TCP_RECEIVE_SIZE_MIN     4,096
TCP_SEND_SIZE_DEFAULT     16,384
TCP_SEND_SIZE_MAX     9,223,372,036,854,775,807
TCP_SEND_SIZE_MIN     4,096
Back to Wait Events Statistics
Back to Top
Operating System Statistics - Detail
Snap Time     Load     %busy     %user     %sys     %idle     %iowait
26-Aug 03:00:48     1.39
26-Aug 04:00:52     1.37     0.38     0.21     0.16     99.62     0.17
Back to Wait Events Statistics
Back to Top
Foreground Wait Class
•     s - second, ms - millisecond - 1000th of a second
•     ordered by wait time desc, waits desc
•     %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
•     Captured Time accounts for 78.2% of Total DB time 115.88 (s)
•     Total FG Wait Time: 62.08 (s) DB CPU time: 28.58 (s)
Wait Class     Waits     %Time -outs     Total Wait Time (s)     Avg wait (ms)     %DB time
User I/O     8,949     0     56     6     48.74
DB CPU               29          24.66
System I/O     1,916     0     3     1     2.18
Other     506     88     1     2     0.92
Configuration     2     50     1     500     0.86
Commit     37     0     1     18     0.56
Application     20     0     0     17     0.29
Network     4,792     0     0     0     0.01
Concurrency     1     0     0     0     0.00
Back to Wait Events Statistics
Back to Top
Foreground Wait Events
•     s - second, ms - millisecond - 1000th of a second
•     Only events with Total Wait Time (s) >= .001 are shown
•     ordered by wait time desc, waits desc (idle events last)
•     %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
Event     Waits     %Time -outs     Total Wait Time (s)     Avg wait (ms)     Waits /txn     % DB time
db file scattered read     3,456     0     17     5     59.59     14.92
db file sequential read     4,304     0     17     4     74.21     14.77
direct path read temp     764     0     17     22     13.17     14.31
direct path write temp     259     0     5     21     4.47     4.70
control file sequential read     1,916     0     3     1     33.03     2.18
ADR block file read     38     0     1     28     0.66     0.92
log buffer space     2     50     1     500     0.03     0.86
log file sync     37     0     1     18     0.64     0.56
enq: RO - fast object reuse     14     0     0     24     0.24     0.29
local write wait     44     0     0     1     0.76     0.03
SQL*Net message to client     4,772     0     0     0     82.28     0.01
Disk file operations I/O     110     0     0     0     1.90     0.00
ADR block file write     7     0     0     0     0.12     0.00
SQL*Net message from client     4,773     0     15,396     3226     82.29
Streams AQ: waiting for messages in the queue     720     100     3,600     5000     12.41
Back to Wait Events Statistics
Back to Top
Background Wait Events
•     ordered by wait time desc, waits desc (idle events last)
•     Only events with Total Wait Time (s) >= .001 are shown
•     %Timeouts: value of 0 indicates value was < .5%. Value of null is truly 0
Event     Waits     %Time -outs     Total Wait Time (s)     Avg wait (ms)     Waits /txn     % bg time
control file sequential read     4,950     0     35     7     85.34     40.74
control file parallel write     1,262     0     31     25     21.76     36.46
log file parallel write     383     0     4     10     6.60     4.37
db file parallel write     627     0     2     3     10.81     2.36
change tracking file synchronous read     56     0     2     34     0.97     2.21
os thread startup     17     0     1     88     0.29     1.74
ADR block file read     135     0     1     7     2.33     1.04
change tracking file synchronous write     56     0     1     15     0.97     0.98
SGA: allocation forcing component growth     8     100     1     100     0.14     0.93
db file sequential read     112     0     1     6     1.93     0.75
process diagnostic dump     94     0     0     1     1.62     0.09
ADR block file write     92     0     0     1     1.59     0.07
LGWR wait for redo copy     11     0     0     1     0.19     0.01
log file sync     2     0     0     3     0.03     0.01
ADR file lock     92     22     0     0     1.59     0.01
Parameter File I/O     24     0     0     0     0.41     0.01
direct path write     6     0     0     1     0.10     0.00
Disk file operations I/O     54     0     0     0     0.93     0.00
rdbms ipc message     17,637     97     61,836     3506     304.09
Streams AQ: waiting for time management or cleanup tasks     5     60     11,053     2210602     0.09
DIAG idle wait     7,203     100     7,203     1000     124.19
PX Idle Wait     1,802     100     3,604     2000     31.07
pmon timer     1,212     99     3,603     2973     20.90
Space Manager: slave idle wait     726     99     3,603     4963     12.52
smon timer     12     100     3,600     300004     0.21
Streams AQ: qmn slave idle wait     128     0     3,583     27993     2.21
Streams AQ: qmn coordinator idle wait     256     50     3,583     13996     4.41
SQL*Net message from client     293     0     2     5     5.05
Back to Wait Events Statistics
Back to Top
Wait Event Histogram
•     Units for Total Waits column: K is 1000, M is 1000000, G is 1000000000
•     % of Waits: value of .0 indicates value was <.05%; value of null is truly 0
•     % of Waits: column heading of <=1s is truly <1024ms, >1s is truly >=1024ms
•     Ordered by Event (idle events last)
          % of Waits
Event     Total Waits     <1ms     <2ms     <4ms     <8ms     <16ms     <32ms     <=1s     >1s
ADR block file read     173     80.3     5.2     2.3     5.8     1.7          4.6
ADR block file write     99     96.0     3.0                    1.0
ADR file lock     102     100.0
Disk file operations I/O     165     100.0
LGWR wait for redo copy     11     90.9               9.1
Parameter File I/O     24     100.0
SGA: allocation forcing component growth     8                                   100.0
SQL*Net break/reset to client     6     100.0
SQL*Net message to client     4992     100.0
SQL*Net more data from client     20     100.0
asynch descriptor resize     541     100.0
change tracking file synchronous read     56     83.9                         1.8     14.3
change tracking file synchronous write     56     80.4     7.1               1.8          10.7
control file parallel write     1262     80.3     1.7     .6     .6     .8     1.3     14.7
control file sequential read     6866     94.1     .9     .7     .7     .3     .4     2.9
db file parallel write     628     94.3     2.1     1.0     .8     .3     .3     1.3
db file scattered read     3457     72.6     7.2     5.4     6.9     5.7     .5     1.6
db file sequential read     4525     78.7     2.7     1.8     9.6     5.3     .4     1.5
direct path read temp     764     40.2     18.6     9.4     6.2     11.0     5.8     8.9
direct path sync     1     100.0
direct path write     6     83.3     16.7
direct path write temp     259     .4          1.2     88.8          .4     9.3
enq: RO - fast object reuse     14     42.9     42.9          7.1               7.1
latch free     1     100.0
latch: cache buffers lru chain     2     100.0
latch: checkpoint queue latch     2     100.0
latch: messages     2     100.0
latch: object queue header operation     2     100.0
latch: redo allocation     1     100.0
latch: row cache objects     1     100.0
local write wait     44     100.0
log buffer space     2     50.0                              50.0
log file parallel write     383     92.4     .8          1.0               5.7
log file sync     39     82.1     2.6          2.6               12.8
os thread startup     17                                   100.0
process diagnostic dump     94     34.0     63.8     2.1
reliable message     7     100.0
utl_file I/O     12     100.0
DIAG idle wait     7204                                   100.0
PX Idle Wait     1802                                        100.0
SQL*Net message from client     5067     87.1     6.6     1.0     .5     .5     .1     .5     3.7
Space Manager: slave idle wait     726     .6                                   99.4
Streams AQ: qmn coordinator idle wait     256     49.2     .8                              50.0
Streams AQ: qmn slave idle wait     128                                        100.0
Streams AQ: waiting for messages in the queue     721                                        100.0
Streams AQ: waiting for time management or cleanup tasks     5     40.0                              20.0     40.0
class slave wait     17     100.0
pmon timer     1212     .9                                   99.1
rdbms ipc message     17.6K     1.8     .4     .2     .2     .1     .1     21.0     76.2
smon timer     12                                        100.0
Back to Wait Events Statistics
Back to Top
I couldnt add the rest of the report here since it is telling me I have exceeded 30000 characters. If you want to see the full report, please email me at [email protected]

Unless your database is strictly a DSS-type of database, your AWR report exposes loads of issues with it. And I think none of the time during the AWR window was spent on database. Look at the DB time (with all those multi cores) compared with the elapsed time of the AWR.
As you are on 11g, why not make use of MEMORY_TARGET (a single parameter to manage both SGA and PGA)? If you are already on it, ignore this as I can't see it anywhere. If not, get rid of SGA_TARGET and PGA_AGGREGATE_TARGET and replace it with a single MEMORY_TARGET parameter. However you may have a minimum threshold set for different SGA pools so that they won't shrink beyond that point.
Having said that, setting MEMORY_TARGET is not a guarantee to avoid ORA-4030. Just a single bad PL/SQL code could go and exploit the untunable part of your process memory and even go and blow up the physical memory. If you are using FORALL and BULK load, see if you can cut it down into few chunks rather than running as a single process.
What does your V$PGASTAT say?

Error ORA-04030: out of process memory when trying to allocate 8512 bytes

Good Afternoon estimated
I want to see if anyone has the following problem occurred while there are about 70 concurrent connections to the Oracle instance. if anyone has any solution.
is grateful for the help in advance:
Dump file d:\oracle\data\admin\ppmdb\bdump\ppmdb_mmon_5032.trc
Thu Aug 11 09:23:40 2011
ORACLE V10.2.0.4.0 - Production vsnsta=0
vsnsql=14 vsnxtr=3
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
With the OLAP, Data Mining and Real Application Testing options
Windows NT Version V5.2 Service Pack 2
CPU : 8 - type 586, 1 Physical Cores
Process Affinity : 0x00000000
Memory (Avail/Total): Ph:5642M/8181M, Ph+PgF:17775M/20246M, VA:9M/2047M
Instance name: DBMM
Redo thread mounted by this instance: 1
Oracle process number: 11
Windows thread id: 5032, image: ORACLE.EXE (MMON)
*** 2011-08-11 09:23:40.429
*** SERVICE NAME:(SYS$BACKGROUND) 2011-08-11 09:23:40.413
*** SESSION ID:(161.1) 2011-08-11 09:23:40.413
*** KEWROCISTMTEXEC - encountered error: (ORA-04030: out of process memory when trying to allocate 8512 bytes (pga heap,kgh stack)
*** SQLSTR: total-len=267, dump-len=240,
STR={insert into wrh$_sysmetric_history (snap_id, dbid, instance_number, begin_time, end_time, intsize, group_id, metric_id, value) select :snap_id, :dbid, :instance_number, begtime, endtime, intsize_csec, groupid, metri}
===============
Note: This allows us to continue to connect more users and the only way to make new connections is restarting the instance
I Have Configurate: pga_aggregate_target integer 379584512
Total System Global Area 1577058304 bytes
Fixed Size 1299216 bytes
Variable Size 729812208 bytes
Database Buffers 838860800 bytes
Redo Buffers 7086080 bytes
Thank you for your possible help
Claudio T.

804135 wrote:
Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 - Production
Windows NT Version V5.2 Service Pack 2
Memory (Avail/Total): Ph:5642M/8181M, Ph+PgF:17775M/20246M, VA:9M/2047M
I Have Configurate: pga_aggregate_target integer 379584512
Total System Global Area 1577058304 bytesHave a search on this forum (or google) for the error code, there should be lots of previous discussion on this one.
From no sign of 64-bit in the product banner plus VA (address space) 2 GB (close enough), it looks like the server is running as 32-bit process.
With SGA + PGA (target) adding up to nearly 1900 MB, my guess is you are hitting the 2 GB per process limit.
Lower SGA, it should help in the very short term. For longer term: lower resource demands or start planning for migration to 64-bit.

ORA-04030: out of process memory opening a cursor

Hi,
We are wonking on Oracle 9i dedicated server OLTP.
When a Pro*C process tries to open a big query cursor the ORA-04030 is returned by Oracle. Below is the query plan:
| Id | Operation                 | Name           | Rows | Bytes | Cost |
|   0 | SELECT STATEMENT          |                 |    41 | 4182 | 1038K|
|   1 | SORT UNIQUE              |                 |    41 | 4182 | 1038K|
|   2 |   HASH JOIN               |                 |    41 | 4182 | 1038K|
|   3 |    VIEW                   |                 |   157K| 8002K|   164K|
|   4 |     SORT UNIQUE           |                 |   157K|    11M|   162K|
|   5 |      HASH JOIN            |                 |   157K|    11M|   160K|
|   6 |       VIEW                |                 | 3151K|   126M| 51970 |
|   7 |        SORT ORDER BY      |                 | 3151K|   117M| 51970 |
|   8 |         TABLE ACCESS FULL | RE_ASNEF        | 3151K|   117M| 17637 |
|   9 |       VIEW                |                 | 6427K|   208M| 89856 |
| 10 |        SORT ORDER BY      |                 | 6427K|   214M| 89856 |
| 11 |         HASH JOIN         |                 | 6427K|   214M| 25130 |
| 12 |          TABLE ACCESS FULL| TIPO_CLIENTE    |    21 |   357 |     2 |
| 13 |          TABLE ACCESS FULL| LISTA_CLIENTES |    11M|   204M| 25084 |
| 14 |    VIEW                   |                 |    12M|   599M|   861K|
| 15 |     SORT ORDER BY         |                 |    12M|   695M|   861K|
| 16 |      TABLE ACCESS FULL    | RECIBOS         |    12M|   695M|   670K|
-----------------------------------------------------------------------------We guess that the problem is that the dedicated server process is triying to allocate more memory that allowed by OS per process:
cobros1p:$ ulimit -a
time(seconds)        unlimited
file(blocks)         unlimited
data(kbytes)         131072
stack(kbytes)        32768
memory(kbytes)       32768       <<<-----
coredump(blocks)     2097151
nofiles(descriptors) 2000OS memory limit can´t be increased, so we guess that one posible solution is to split the query using temporary tables to reduce "hash join/sort" PGA space.
Are we right? Any hint about other possible solutions?
Thanks in advance,
Jose Luis

From various notes you can find on MOS about 4030:
"Each Operating System will handle memory allocations with Oracle slightly differently."
"The application developer of an Oracle precompiler program or OCI program can explicitly open cursors, or handles to specific private SQL areas, and use them as a named resource throughout the execution of the program. Recursive cursors that Oracle issues implicitly for some SQL statements also use shared SQL areas.
The management of private SQL areas is the responsibility of the user process. The allocation and deallocation of private SQL areas depends largely on which application tool you are using, although the number of private SQL areas that a user process can allocate is always limited by the initialization parameter OPEN_CURSORS. The default value of this parameter is 50.
A private SQL area continues to exist until the corresponding cursor is closed or the statement handle is freed. Although Oracle frees the runtime area after the statement completes, the persistent area remains waiting. Application developers close all open cursors that will not be used again to free the persistent area and to minimize the amount of memory required for users of the application. "
"However, from within the database framework you cannot place a hard limit on the size of a process by setting any initialization parameters or database configuration.
You can limit the size of a process from the OS side by setting kernel limits or user shell limits.
However, this leads to the ORA-4030 and will cause transaction rollback."
You need to have some serious discussions with both your app developers and your OS admins, though if you are running something from the last century, that could be pointless.

File size limit on export doesn't.

I have an export option for a photo forum I post to, where the size limit is 200kb. I have set 200kb, 600x600 JPG as the export limits, and I routinely get files much bigger, memory-wise, than that, up to 260kb.
I can set the export dimension limit to 500x500, and still get files over 200kb. Today, after a file went to 260kb at 600x600, I set the dimension limit to 500x500, and the exported file size did not change: at 500x500, it was still a 260kb file. If I go through and tweak compression by hand, on every photo, or set a file size limit of 150kb, I can get under 200kb per file.
I've tried files where I set the limit from 200, to 190, to 180, to 170, and see no change in the exported file (still well over 200 in size), and then when I set it to 160 it jumps down to 150-160 in size. If the file was only 210kb on export with the 200kb limit, setting it to 180kb will generally get the file under 200kb.
Really, the file size limit does not do what it purports to do. It can clearly get the file below that size if I direct it by hand every time: I haven't specified anything that would artificially bulk the file up, like a quality setting that would be incompatible with the file size limit. It's free to compress the file as needed to meet the limit.
What I want it to do is meet the limit I set for it. I shouldn't have to dance around. I have this export setting for the express purpose of quickly producing under-200kb files, and I sort of expect Lightroom to manage it.

I've had this problem too, but it isn't the only one when creating small jpeg files from LR.
There is something seriously amiss in the export module. I also create a lot of 600 pixel wide/high files and not only are the file sizes far too high, but the quality is poor. I have two workarounds for this, both of which add a little time to the job, but make a big difference.
First is to export my files as full size jpegs (which I do anyway,) LR does a good job with these. Then get another programme to batch process these to give me the small sRGB files I also need!
Second is to use LR's web module and create a basic html site for a batch of images in a folder in a temp directory at the precise size I want. This has the advantage that I can add a watermark. Then just rename and move the folder containing the images from the web folder that has been created to where I want them, followed by deleting the rest of the web folder.
Working at low quality (38%) from the Export module gave me a file size for one image of 455KB. So then I told it to export at a max of 200KB, and it came out at 565KB. Using the web module with quality set at 70 gave a higher quality result and a file size of 105KB!
The problem seems to be worse on images where I've done quite a bit of work using local adjustments - rather as if they are actually performing these on the small jpeg and re-saving each time. Certainly something going very wrong - just like it was in LR2.x and I think it must be a logical error as presumably the web module uses the same library to create jpegs.

Per Process system memlock and huge page

Hello All,
I noticed in our new environment while database starts It shows the dump of system resource information for SGA. This is showing us few information of which I am confused.
It says,
Per process system memlock (soft) limit =193g
Expected per process system memlock (soft) limit to lock.
Shared Global area into memory 4096M.
Available system page size
4K, 2048k
Supported system pagesize:
pagesize =4K, available_pages=configured, expected_pages=1048581, Allocated pages=1048581 and No errors.
Reasons, for not supporting certain system pagesizes:
2048K- Dynamic allocate and free memory regions
Now I am not understanding where from 193G is coming!
cat /proc/meminfo | grep -i Huge
AnonHugePages:     407552 kb
Hugepages_total:     0
Hugepages_free:     0
Hugepages_rsvd;     0
Hugepages_Surp:     0
Hugepagesize:          2048 Kb
cat /etc/sysctl.conf | grep -i huge     says nothing.
shmmni=4096
shmall =1835008
shmmax= 6388763852
sem = 250 32000 100 128
Could you please help me to understand where from getting the value 193g?
Oracle versoin: 12.1.0.2.0 and RHEL 6.6
Regards,
J_DBA_Sourav

Hello,
It is a normal file system and database upon that.
GRID is not being used. Though what you have asked to post about limit.conf
* hard core 0
only this is mentioned.
inside /etc/security/limits.d there is file, 91-oracle.conf where below are mentioned.
oracle soft memlock 202457088               -> I calculated this number, if it is in KB then it is 193.07G but I don't know what is this doing.
oracle hard memlock 202457088
oracle soft core unlimited
oracle hard core unlimited
oracle soft noproc 131072
oracle hard noproc 131072
oracle soft nofile 131072
oracle hard nofile 131072
there is generic file in $ORACLE_HOME/crs/install/s_crsconfig_defs
there a segment for CRS_LIMIT_MEMLOCK=unlimited is mentioned and CRS_LIMIT_CORE =unlimted other than lots of other parameters. I am not able to copy and paste as operation is not allowed.
Regards,
J_DBA_Sourav

ERROR : ORA-04030 -out of process memory when trying to allocate 16396 byte

hi,
i have written a procedure that insert as well as update few table.
But when i am trying to execute the procedure then it throws error:
ORA-04030: out of process memory when trying to allocate 16396 bytes something like that.
I don't know why it is?
I am using cursor with bulk collect and forall block to insert and update.

The error message says that you ran out of PGA memory. You are bulk collecting into a variable that resides in PGA memory. So likely you fetched everything from the query into the collection variable at once. You would need at least (number of rows of result set * average number of bytes per row) bytes. And you don't have that amount of bytes apparently.
A solution is to use the limit clause while bulk collecting and set it to a reasonable amount of rows, say 100 or 1000 at most. And use an extra loop while exiting when <collection variable>.count = 0.
Regards,
Rob.
Message was edited by:
Rob van Wijk
Way too slow ...

JVM heap size limit under Windows

Hi,
I'm looking either for some help with a workaround, or
confirmation that the information I've found is still the case for the
current state of Java.
Development machine is Win XP Pro, 2G RAM.
Biggest heap I can allocate is about 1.6G, and that is not large enough for this
app.
I have a Swing application that
1) must run on Win XP, 32 bit
2) must implement an editor (similar to Excel but with fewer features) to handle large csv files
( up to about 800Mb).
3) Strong preference for Java 5, though higher could conceivably be supported.
Research so far tells me that this is the result of process memory limitations
of Windows and the JVM, and that I might be able to squeeze a little more heap with
Windows' rebase command, but probably not enough and I would start running the
risk of conflicts with other applications on my users' systems. Ugh.
Also I read of the Windows /3GB switch, but posts say that the JDK's available are not
built to be able to use that feature. I havent had a chance to add memory to
test that yet. However, I'm also under the impression that I should be able to
allocate a heap larger than physical RAM ... except for that process size limit.
So ... my information is basically that I'm stuck with a limit of about 1.6G for
heap size, regardless of the RAM on my computer.
Can anyone confirm whether that is still correct, preferably with a pointer to some
official reference ?
Or better yet, point me toward a workaround?
Thanks!
-tom

>
Some bookmarks I have on this topic.
http://sinewalker.wordpress.com/2007/03/04/32-bit-windows-and-jvm-virtual-memory-limit/
http://stackoverflow.com/questions/171205/java-maximum-memory-on-windows-xp
The first link pulled together what I found in lots of bits and pieces elsewhere, nice to have a coherent summary :)
The second link offered a bit of insight into the jvm that I hadn't seen yet .
Thanks!

Per-process memory size limit

Similar Messages

Maybe you are looking for