cancel
Showing results for 
Search instead for 
Did you mean: 

AWE memory problem...

Former Member
0 Kudos

Hello,

I encountered with a memory problem, while opening the database with following parameters;

*._b_tree_bitmap_plans=false

*._eliminate_common_subexpr=false

*._optim_peek_user_binds=false

*._optimizer_join_sel_sanity_check=TRUE

*._optimizer_or_expansion='depth'

*._sort_elimination_cost_ratio=10

*.background_dump_dest='D:\oracle\BW3\saptrace\background'

*.bitmap_merge_area_size=33554432

*.compatible='9.2.0.8.0'

*.control_file_record_keep_time=30

*.control_files='D:\oracle\BW3\saparch\cntrl\cntrlBW3.dbf','E:\oracle\BW3\origlogA
cntrl\cntrlBW3.dbf','G:\oracle\BW3\sapdata1\cntrl\cntrlBW3.dbf'

*.core_dump_dest='D:\oracle\BW3\saptrace\background'

*.create_bitmap_area_size=33554432

*.db_block_buffers=300000

*.DB_BLOCK_CHECKSUM=false

*.db_block_size=8192

*.db_file_multiblock_read_count=32

*.db_files=254

*.db_name='BW3'

*.dml_locks=9600

*.enqueue_resources=9600

*.event='10191 trace name context forever, level 1','10028 trace name context forever, level 1','10027 trace name context forever, level 1','38068 trace name context forever, level 100','38069 trace name context forever, level 1','38043 trace name context forever, level 1','10171 trace name context forever, level 1','38085 trace name context forever, level 1'

*.filesystemio_options='SETALL'

*.hash_area_size=18874368

*.hash_join_enabled=true

*.java_pool_size=0

*.large_pool_size=8388608

*.log_archive_dest='E:\oracle\BW3\oraarch\BW3arch'

*.log_archive_start=true

*.log_buffer=1048576

*.log_checkpoint_interval=0

*.log_checkpoint_timeout=0

*.log_checkpoints_to_alert=true

*.max_dump_file_size='20000'

*.open_cursors=800

*.optimizer_features_enable='9.2.0'

*.optimizer_max_permutations=2000

*.optimizer_mode='choose'

*.parallel_execution_message_size=16384

*.parallel_max_servers=80

*.parallel_threads_per_cpu=1

*.pga_aggregate_target=600M

*.processes=420

*.remote_os_authent=true

*.replication_dependency_tracking=FALSE

*.row_locking='always'

*.sessions=450

*.shared_pool_reserved_size=71918382

*.shared_pool_size=719183820

*.sort_area_size=2097152

*.star_transformation_enabled='TRUE'

*.timed_statistics=true

*.transaction_auditing=FALSE

*.undo_management='AUTO'

*.undo_retention=43200

*.undo_tablespace='PSAPUNDO'

*.user_dump_dest='D:\oracle\BW3\saptrace\usertrace'

*.workarea_size_policy='auto'

*.use_indirect_data_buffers=true

The system has 16 gb physical memory with /pae and /3gb options in boot.ini file. What can cause the problem?

Thank you.

Accepted Solutions (0)

Answers (5)

Answers (5)

Former Member
0 Kudos

Yes, and exactly yes. I will drop em'all ... Merry christmas and happy new year, my friend...

Orkun

Former Member
0 Kudos

We are planning to go 64 bits soon, my friend.

Former Member
0 Kudos

great, than you can say good by to

AWE

/3GB

/userva

and all the pain getting this under the same hat.

Former Member
0 Kudos

AWE is working but will not deliver the same performance than 64 Bit.

As long as you are running the database standalone it might run fine, but as soon you have an additional SAP Central instance on it, keeping this configuration running stable might create some headaches.

Beleave me, 64 bit is much more powerfull!

regards

Peter

Former Member
0 Kudos

Hi

,

I set the parameter "_DB_BLOCK_LRU_LATCHES" to 16 and resolved the problem.

Regards,

Orkun Gedik

Former Member
0 Kudos

I also attached the error into message;

ORA-27102: out of memory

OSD-00034: Message 34 not found; product=RDBMS; facility=SOSD

O/S-Error: (OS 😎 Not enough storage is available to process this command.

I also, configured local security policy settings.

Thank you