on 08-23-2010 9:52 AM
Hello Guru,
Good day!
I'm not sure if I'm in the correct forum, please bare with me if I'm not.
We are actually planning to increase our Production [Physical Memory] server from its current size 15360GB including [oracle, SAP & OS] to 44GB memory. Do you have any idea how can we calculate to the most needed SAP / DB parameter should be increase after we allocate the 44GB in preparation for Go-Live. Below are details of my systems [oracle version, kernel, R/3 System, OS version, SAP parameter and DB parameter.
Reason for memory upgrade: will create two client in one system with a different number of users and different plant e.g. America / Canada
======================================================================
SAP R/3 Version: SAP 4.6C
Oracle Version: 10.2.0.4.0
OS Level: AIX 5.3
orapaa> oslevel -g
Fileset Actual Level Maintenance Level
-
bos.rte 5.3.8.0 5.3.0.0
Physical Memory
Real,MB 15360
======================================================================
kernel release 46D
kernel make variant 46D_EXT
compiled on AIX 1 5 0056AA8A4C00
compiled for 64 BIT
compile time Aug 17 2007 10:57:49
update level 0
patch number 2337
source id 0.2337
======================================================================
orapaa> prtconf
System Model: IBM,9117-MMA
Machine Serial Number: 06DDD01
Processor Type: PowerPC_POWER6
Processor Implementation Mode: POWER 6
Processor Version: PV_6_Compat
Number Of Processors: 4
Processor Clock Speed: 4208 MHz
CPU Type: 64-bit
Kernel Type: 64-bit
LPAR Info: 9 SWT_AMR_SADCB335_SAP_HA_PRI
Memory Size: 15360 MB
Good Memory Size: 15360 MB
Platform Firmware level: Not Available
Firmware Version: IBM,EM340_095
Console Login: enable
Auto Restart: true
Full Core: false
======================================================================
Our current used SAP parameter
Profile parameters for SAP buffers Parameters Name Value Unit
Program buffer
abap/buffersize 850000 Kb
CUA buffer
rsdb/cua/buffersize 10000
Screen buffer
zcsa/presentation_buffer_area 20000000 Byte
Generic key table buffer
zcsa/table_buffer_area 100000000 Byte
Single record table buffer
rtbb/buffer_length 60000
Export/import buffer
rsdb/obj/buffersize 40000 kB
Table definition buffer
rsdb/ntab/entrycount 30000
Field description buffer
rsdb/ntab/ftabsize 60000 kB
Initial record buffer
rsdb/ntab/irbdsize 8000 kB
Short nametab (NTAB)
rsdb/ntab/sntabsize 3000 kB
Calendar buffer
zcsa/calendar_area 500000 Byte
Roll, extended and heap memory EM/TOTAL_SIZE_MB 6144 MB
ztta/roll_area 6500000 Byte
ztta/roll_first 1 Byte
ztta/short_area 1400000 Byte
rdisp/ROLL_SHM 16384 8 kB
rdisp/PG_SHM 16384 8 kB
rdisp/PG_LOCAL 150 8 kB
em/initial_size_MB 4092 MB
em/blocksize_KB 4096 kB
em/address_space_MB 4092 MB
ztta/roll_extension 2000000000 Byte
abap/heap_area_dia 2000000000 Byte
abap/heap_area_nondia 2000000000 Byte
abap/heap_area_total 2000000000 Byte
abap/heaplimit 40000000 Byte
abap/use_paging 0
======================================================================
Oracle Parameter
Oracle Parameter Name Value Unit
SGA_MAX_SIZE 6192 MB
PGA_AGGREGATE_TARGET 400 MB
DB_CACHE_SIZE 0
SHARED_POOL_SIZE 960 MB
LARGE_POOL_SIZE 16 MB
JAVA_POOL_SIZE 32 MB
LOG_BUFFER 14246912
db_block_buffers 655360
Thanks and regards,
Mike
I feel the best way to get the parameters which needs to be adjusted is to go for EarlyWatch Check after increasing the Physical Memory of your SAP system, as we cannot say how and which parameters needs to be checked and changed.. as there is some dependiblity also between the parameters...
All the best !
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
User | Count |
---|---|
87 | |
10 | |
10 | |
9 | |
7 | |
6 | |
6 | |
5 | |
4 | |
3 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.