Oracle Memory Setup during SAPINST

[former_member229542]

Hi Guys,

Im actually performing an Unicode Migration, therefore Original system is deleted and then a new system is installed with R3load

My main question focus on how SAPINST, distributes Oracle memory when during Database Steps, you setup a memory value in Mb

The actual Oracle DB 11.2.0.3 has these values

Total System Global Area             2339151872 bytes

Fixed Size                                   2161424 bytes

Variable Size                               2248148208 bytes

Database Buffers                          67108864 bytes

Redo Buffers                                 21733376 bytes

Actual Hardware specs

SunOS bwp 5.10 Generic_142900-14 sun4u sparc SUNW,SPARC-Enterprise

root@bwp # prtconf |head -3 |grep Mem

prtconf: devinfo facility not available

Memory size: 81920 Megabytes

This new Upgraded system is a Netweaver 740 Business Intelligence, according to Note 1431798 - Oracle 11.2.0: Database Parameter Settings

For OLAP systems PGA_AGGREGATE_TARGET should be around 40% of available Memory from SGA

and sga_max_size is currently set to 2240M

pga_aggregate_target  1932736000

SAP System is CI+DB and has 25 Dialog WP and 5 Update, and user concurrence in around 40 users

So, if I have 80GB total memory on the server, how much should I predefine during SAPInst to get similar values as recommended by SAP?

Is the 70% SAP /30% DB memory rule applicable to a BW system?

Any hint on how to better determine this values would be highly appreciated.

Best

Martin

[former_member229542 · Accepted solution]

Thanks Deepak, Benjamin.

I agree with Note for Oracle Settings for R3load; after migration has been completed, which basic considerations should be taken for a BW System running Oracle DB?

Original parameters are OK or do you recommend any change in the settings?

Best

Martin

[former_member188883 · Accepted solution]

Hi Martin,

Post migration for BI systems general recommendation is 60% SAP and 40% DB.

Regards,

Deepak Kori

[Reagan · Accepted solution]

I would keep the source system memory configuration on the target system after the migration and observer the cache hit ratio and if required increase the memory assignment for SGA and PGA.

1431798 - Oracle 11.2.0: Database Parameter Settings

If you read that SAP note it says clearly that we are allowed to optimize the memory parameters and it is not giving any general recommendations.

[Reagan]

For the migration I would follow the memory recommendations given in the SAP note 936441 - Oracle settings for R3load based system copy

The memory settings and configuration provided in the SAP note is basically for the R3load based operation. Once the migration has been completed you need to set the parameters based on the recommended values for the BW system.

[former_member229542]

Hi Benjamin, quick question on that R3load Based system copy Note

• pga_aggregate_target         =  70% of main memory size (for target database)

70% of Main Memory size, means 70% of Solaris Total Memory?

[Reagan]

Martin Simois wrote:

Hi Benjamin, quick question on that R3load Based system copy Note


pga_aggregate_target         =  70% of main memory size (for target database)


70% of Main Memory size, means 70% of Solaris Total Memory?

Correct.

Regards

RB

[former_member188883]

Hi Martin,

As Unicode migrations will be R3load based refer to below SAP note for Oracle database configurations.

936441 - Oracle settings for R3load based system copy

Hope this helps.

Regards,

Deepak Kori