**Please Note that you can not use ASMM i.e SGA_TARGET when using AWE.**

-Amit

Still i am facing ORA-04030- out of process memory error during daily opeations.
Please help me or suggest me how to resolve this issue.

Regards
Bhupendra

sga_max_size = sga_target = 584M
pga_aggregat_target = 300M
shared_pool_size = 0
db_cached_size = 0

I am using Oracle 10.2.0.1.0 with Win Server 2003 Enterprise x32 with 10Gb RAM. ASMM is enabled. I use /3GB and /PAE in boot.ini.

I want to increase the memory more than 2GB but it seems limited. In “Database Configuration Assistant: Step 10″ (when you create new database using wizards) , oracle can read only 2GB of RAM.
I can’t set “use_indirect_data_buffers” to TRUE as it will stop oracle instance (it will throw error ora-12514) and therefore i cant use AWE_WINDOW_SIZE.
If i get my AWE working, is it better using ASMM ?

Can you please give me suggestion. I want to enable AWE… Thanks.

-tongkimongki @ yahoo . com-

What was initial setting for large_pool. RMAN and parallel query slaves use large pool. So would recommend increasing large_pool to 200 or more (depending on your earlier setting).

Cheers
Amit

The instance started up without error , but after a few hours of using it, with 30 users, it started to give errors like:
ora-4031 unable to allocate shared…..(‘large pool’), and RMAN was reporting trouble also.

No sga_ parameters are used, Thank you in advance.

Can you please unset SGA_MAX_SIZE parameter and try again.

Regards
Amit

Oracle 9.2i
CPU’s = 8
Total ram = 16GB

AWE is set at 536 870 192

DB_BLOCK_BUFFERS = 384216
sga_max_size = 1500M
shared_pool_size = 500M
PGA_AGGREGATE_TARGET = 700M

/3GB and /PAE are set in boot.ini.

We have tried several configs with all different sizes for SGA, PGA, block_buffers etc. but still we get:

MAN-03002: failure of backup command at 06/24/2010 14:26:10

ORA-04030: out of process memory when trying to allocate 1049100 bytes (pga heap,KSFQ Buffers)

with our RMAN..
Do you have any suggestions to get RMAN working again? Must be something with PGA i would suspect!

Thanks!!!
regards,
Jargo

Cheers
Amit

In your case you are getting ora-4030 error i.e process memory (PGA) +SGA has gone beyond 2.7 gb . I think you will have to look at two options

a) Try looking at why the pga requirement is high. May be you can tune the sql and try for optimal plan

b) Reduce sga size and see if you are still getting errors.

You can try using /PAE switch but i think you will have to change AWE_WINDOW_SIZE too. Refer to MOS note on finding appropriate size.

Regards
Amir

I found you post realy helpful.

I need your advise to set these parameters for my database also: Below is the details:

Database version = 10.2.0.2
Oracle Applications Version= 12.0.6

OS= Windows Server 2003 Enterprise Edition Service Pack 2

Boot.ini
———–
[boot loader]
timeout=30
default=multi(0)disk(0)rdisk(0)partition(2)\WINDOWS
[operating systems]
multi(0)disk(0)rdisk(0)partition(2)\WINDOWS=”Windows Server 2003, Enterprise” /noexecute=optout /fastdetect /pae /3gb /userva=3030
————————————————-
Total Physical Memory = 16 GB
————————————————-
Total System Global Area 2147483648 bytes
Fixed Size 1293536 bytes
Variable Size 872416032 bytes
Database Buffers 1258291200 bytes
Redo Buffers 15482880 bytes
—————————————————————————
db_block_buffers integer 0
db_block_size integer 8192
db_cache_size big integer 0
java_pool_size big integer 0
large_pool_size big integer 0
log_buffer integer 15244288
sga_max_size big integer 2G
sga_target big integer 2G
shared_pool_size big integer 800M
streams_pool_size big integer 0
—————————————————————————
use_indirect_data_buffers boolean FALSE
—————————————————————————
sessions integer 1600
processes integer 800
—————————————————————————

Please advise what step should I follow to utilize memory more than 4 GB?

As we are facing the following issue:
An internal error has occurred in the program XLA_AE_LINES_PKG.SetNullLine. ORA-06500: PL/SQL: storage error
ORA-04030: out of process memory when trying to allocate 16396 bytes (koh-kghu sessi,pmucalm coll).
An internal error occurred. Please inform your system administrator or support representative that:

Waiting for your reply

Thanks
Saleem

As a thumb rule, set SGA_TARGET to 256mb * Number of CPU’s i.e 1024 M in your environment.
Can also set shared_pool_size to 256M so that you do not see reloads/invalidations. May be before touching these values, you can look at hard parses or reloads/invalidations in V$librarycache or your statspack/awr reports.

Regards
Amit

Thanks for your response. I just wanted you to check the variables defined like sga etc. If this is OK then I will certainly log an SR for resolution.

Regards
Vinod

I think instead of looking at alert log, you should try generating AWR/Statspack report for 30-60 mins and try to see what is consuming time in database. Also if any specific session is slow, you can trace it with 10046 event.
You can also log a SR for same and Oracle specialists can assist you in diagnosing and resolving the issue.

Regards
Amit

Windows Server 2003 Version V5.2 Service Pack 1
CPU : 4 – type 586, 2 Physical Cores
Process Affinity : 0×00000000
Memory (Avail/Total): Ph:3671M/4094M, Ph+PgF:5646M/5971M, VA:1941M/2047M
Fri Feb 05 09:32:08 2010
Starting ORACLE instance (normal)
Fri Feb 05 09:32:09 2010
Specified value of sga_max_size is too small, bumping to 612368384
LICENSE_MAX_SESSION = 0
LICENSE_SESSIONS_WARNING = 0
Picked latch-free SCN scheme 2
Using LOG_ARCHIVE_DEST_10 parameter default value as USE_DB_RECOVERY_FILE_DEST
Autotune of undo retention is turned on.
IMODE=BR
ILAT =18
LICENSE_MAX_USERS = 500
SYS auditing is disabled
ksdpec: called for event 13740 prior to event group initialization
Starting up ORACLE RDBMS Version: 10.2.0.1.0.
System parameters with non-default values:
processes = 150
resource_limit = TRUE
sga_max_size = 612368384
__shared_pool_size = 121634816
__large_pool_size = 50331648
__java_pool_size = 8388608
__streams_pool_size = 0
spfile = F:\ORACLE\PRODUCT\10.2.0\DB_1\DBS\SPFILEORCL.ORA
sga_target = 612368384
control_files = F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL01.CTL, F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL02.CTL, F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\CONTROL03.CTL
db_block_size = 8192
__db_cache_size = 423624704
compatible = 10.2.0.1.0
db_file_multiblock_read_count= 16
db_recovery_file_dest = F:\oracle\product\10.2.0/flash_recovery_area
db_recovery_file_dest_size= 2147483648
undo_management = AUTO
undo_tablespace = UNDOTBS1
remote_login_passwordfile= EXCLUSIVE
license_max_users = 500
db_domain =
dispatchers = (protocol=TCP)
shared_servers = 10
job_queue_processes = 10
audit_file_dest = F:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\ADUMP
background_dump_dest = F:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\BDUMP
user_dump_dest = F:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\UDUMP
core_dump_dest = F:\ORACLE\PRODUCT\10.2.0\ADMIN\ORCL\CDUMP
db_name = orcl
open_cursors = 300
pga_aggregate_target = 203423744
PMON started with pid=2, OS id=1100
MMAN started with pid=4, OS id=1036
PSP0 started with pid=3, OS id=296
DBW0 started with pid=5, OS id=1644
LGWR started with pid=6, OS id=1648
CKPT started with pid=7, OS id=1608
SMON started with pid=8, OS id=1588
RECO started with pid=9, OS id=1592
CJQ0 started with pid=10, OS id=1892
MMON started with pid=11, OS id=1896
MMNL started with pid=12, OS id=1956
Fri Feb 05 09:32:12 2010
starting up 1 dispatcher(s) for network address ‘(ADDRESS=(PARTIAL=YES)(PROTOCOL=TCP))’…
starting up 10 shared server(s) …
Fri Feb 05 09:32:14 2010
alter database mount exclusive
Fri Feb 05 09:32:18 2010
Setting recovery target incarnation to 2
Fri Feb 05 09:32:19 2010
Successful mount of redo thread 1, with mount id 1237934366
Fri Feb 05 09:32:19 2010
Database mounted in Exclusive Mode
Completed: alter database mount exclusive
Fri Feb 05 09:32:19 2010
alter database open
Fri Feb 05 09:32:19 2010
Beginning crash recovery of 1 threads
parallel recovery started with 3 processes
Fri Feb 05 09:32:20 2010
Started redo scan
Fri Feb 05 09:32:20 2010
Completed redo scan
403 redo blocks read, 113 data blocks need recovery
Fri Feb 05 09:32:20 2010
Started redo application at
Thread 1: logseq 639, block 3015
Fri Feb 05 09:32:21 2010
Recovery of Online Redo Log: Thread 1 Group 2 Seq 639 Reading mem 0
Mem# 0 errs 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO02.LOG
Fri Feb 05 09:32:21 2010
Completed redo application
Fri Feb 05 09:32:21 2010
Completed crash recovery at
Thread 1: logseq 639, block 3418, scn 44383502
113 data blocks read, 113 data blocks written, 403 redo blocks read
Fri Feb 05 09:32:22 2010
Thread 1 advanced to log sequence 640
Thread 1 opened at log sequence 640
Current log# 3 seq# 640 mem# 0: F:\ORACLE\PRODUCT\10.2.0\ORADATA\ORCL\REDO03.LOG
Successful open of redo thread 1
Fri Feb 05 09:32:22 2010
MTTR advisory is disabled because FAST_START_MTTR_TARGET is not set
Fri Feb 05 09:32:22 2010
SMON: enabling cache recovery
Fri Feb 05 09:32:23 2010
Successfully onlined Undo Tablespace 1.
Fri Feb 05 09:32:23 2010
SMON: enabling tx recovery
Fri Feb 05 09:32:24 2010
Database Characterset is WE8MSWIN1252
replication_dependency_tracking turned off (no async multimaster replication found)
Starting background process QMNC
QMNC started with pid=28, OS id=3052
Fri Feb 05 09:32:30 2010
Completed: alter database open
Fri Feb 05 09:32:30 2010
db_recovery_file_dest_size of 2048 MB is 0.00% used. This is a
user-specified limit on the amount of space that will be used by this
database for recovery-related files, and does not reflect the amount of
space available in the underlying filesystem or ASM diskgroup.

I am facing a lot of problems with regards to performance. The goes dead slow. Kindly suggest the changes to be done.

Thanks & Regards
Vinod

my oracle 9i is install on window server 2003 standard version.Due to this oracle is not using more than 2 gb ram…please suggest

You had mentioned that you are running Windows Server 2003 (Standard Edition) which does not provide functionality of enabling /PAE switch.

Secondly to use you need to se /PAE switch explicitly (not sure what NOEXECUTE function does). In face /NOEXECUTE option is present by default.

As mentioned earlier , you are able to start your database because you are not crossing 2.7 Gb limit. To prove it, lets try this

a) Remove sga_max_size and sga_target
b) set USE_INDIRECT_DATA_BUFFERS =true
c) Set buffer cache to 3G i.e set db_block_buffers=393216 (assuming you have db_block_size=8k) . Does your oracle instance start?