Summary
Symptom
Poor performance in SAP BW system while Extracting data from source system.
Other terms
Infopackage performance, DTP Performancne
Reason and Prerequisites
Extraction Performance problems due to incorrect parameter settings and other factors related to BW system
Solution
1. Load performance in source system.
If the dataload is taking more time in source system, check all paramaters that are suggested in the SAP note 1597364.
2.PSA Performance
Partition Size:
Set the PSA partition size according to the expected packagesizes.
If.you expect many small packages, set the partition size to a rather small value, so that these partitions can be deleted quickly. In transaction RSCUSTV6 the size of each PSA partition can be defined.
Set the Partition Size to 1,000,000 in RSCUSTV6. Test the recommended values before applying them to the production system
3.DSO Performance
Do not set automatic activation when loading in parallel to an DSO.as this might lead to activation starting when requests are not yet greenin the ODS.
If the dataload is taking more time in source system, check all paramaters that are suggested in the SAP note 1597364.
2.PSA Performance
Partition Size:
Set the PSA partition size according to the expected packagesizes.
If.you expect many small packages, set the partition size to a rather small value, so that these partitions can be deleted quickly. In transaction RSCUSTV6 the size of each PSA partition can be defined.
Set the Partition Size to 1,000,000 in RSCUSTV6. Test the recommended values before applying them to the production system
3.DSO Performance
Do not set automatic activation when loading in parallel to an DSO.as this might lead to activation starting when requests are not yet greenin the ODS.
- RSODSO_SETTINGS Transaction
Optimal packet size in the transaction is around 10000.
Select a higher runtime than is usually selected.
in:rdisp/max_wprun_time 3600
SAP common recommendations:
Batch processes = (All Processes/2)+1
Wait Time in Sec. = 3 * rdisp/max_wprun_time
rdisp/max_wprun_time - RZ11 (Note 25528)
Please refer to the Note 1118205 for more detailed info.
Select a higher runtime than is usually selected.
in:rdisp/max_wprun_time 3600
SAP common recommendations:
Batch processes = (All Processes/2)+1
Wait Time in Sec. = 3 * rdisp/max_wprun_time
rdisp/max_wprun_time - RZ11 (Note 25528)
Please refer to the Note 1118205 for more detailed info.
- DSO Activation performance:
In Transaction RZ04 get the total number of background work. process.
Check what is the total workproess, see that in SUM column
Get the ideal work process by the formula.
Batch processes = (All Processes/2)+1
Example:
RZ04
SUM = 81
Batch Process = 42.
Increase the parallel processes in transaction RSODSO_SETTINGS upto 5 if it is less.
PSA and DSO
Large amounts of data in PSA and DSO change log tables may have negative effects on loading performance. Times that are needed for database backups and restores are longer.
Define retention times for DSO change logs and PSAs individually per DataSource or DSO, respectively. Delete older data and start with the PSAs and DSOs highlights in the result lists of based the report given the the SAP note 1150831. After that, schedule regular deletion accordingly.
Refer SAP Note 1150831 (BI 7.00 EHP 1: Flexible PSA deletion) for details on new PSA/CHANGELOG deletion process introduced with EhP1.
4.Master Data
During a change run in delta mode, aggregates are adjusted using a delta request that contains the changes. You can define a value for this in Customizing to specify a percentage of changes (to master data or hierarchies) as of which the delta procedure should switch to reconstruction. The value "0" means that all aggregates are always reconstructed, which normally has a negative impact on performance.
To avoid performance issues, set the delta limit value to "20" (20%) for parameter "Limit with Delta" using transaction RSCUSTV8.
5.DTP Performance
Parallel Processing:
Set the Number of process to 3 in DTP, Follow the path.
RSA1 -> Display DTP -> Goto Menu -> Settings for Batch Manager
This can be checked in Batch Manager also.
Transaction RSBATCH
Settings for parallel processing > DTP_LOAD > Click on parameter settings.
Check note to enable parallel extraction in packages from DSO.
1530373
6.Large Non-BW tables
Table RSBERRORLOG contains the error logs for DTP errors. These errors logs include loads for master data for duplicate records and customer specific transformation routines. SAP Note 1095924 - Correction: Deletion/analysis report for error - provides a number of reports for handling the growth of this table.
Tables RSMON* (for example, table RSMONMESS) and tables RS*DONE (for example, table RSSELDONE) continuously increase in size in the BW system with each request that is created. This data can be archived in a BW 7 system but there is no possibility to delete records in BW 3.5.
Have a look at help.sap.com for further information:
http://help.sap.com/saphelp_nw70/helpdata/EN/42/ead8d7b55e1bd2e10000000a11466f/frameset.htm
Please review SAP Note 706478 for information on managing the size and growth of your basis tables.
7.Process Chain Performance
From the process chain monitor get the step that is causing the performance issue and optimize that step. Follow the recomendations given above if the performance is degraded because of PSA, DSO, DTP.
If you have performance problem in RSPCM transaction create an index on EDIDC including the fields MANDT, CREDAT and MESTYP. Additionaly try to archive the tables such as RSMONMESS etc.
Check what is the total workproess, see that in SUM column
Get the ideal work process by the formula.
Batch processes = (All Processes/2)+1
Example:
RZ04
SUM = 81
Batch Process = 42.
Increase the parallel processes in transaction RSODSO_SETTINGS upto 5 if it is less.
PSA and DSO
Large amounts of data in PSA and DSO change log tables may have negative effects on loading performance. Times that are needed for database backups and restores are longer.
Define retention times for DSO change logs and PSAs individually per DataSource or DSO, respectively. Delete older data and start with the PSAs and DSOs highlights in the result lists of based the report given the the SAP note 1150831. After that, schedule regular deletion accordingly.
Refer SAP Note 1150831 (BI 7.00 EHP 1: Flexible PSA deletion) for details on new PSA/CHANGELOG deletion process introduced with EhP1.
4.Master Data
During a change run in delta mode, aggregates are adjusted using a delta request that contains the changes. You can define a value for this in Customizing to specify a percentage of changes (to master data or hierarchies) as of which the delta procedure should switch to reconstruction. The value "0" means that all aggregates are always reconstructed, which normally has a negative impact on performance.
To avoid performance issues, set the delta limit value to "20" (20%) for parameter "Limit with Delta" using transaction RSCUSTV8.
5.DTP Performance
Parallel Processing:
Set the Number of process to 3 in DTP, Follow the path.
RSA1 -> Display DTP -> Goto Menu -> Settings for Batch Manager
This can be checked in Batch Manager also.
Transaction RSBATCH
Settings for parallel processing > DTP_LOAD > Click on parameter settings.
Check note to enable parallel extraction in packages from DSO.
1530373
6.Large Non-BW tables
Table RSBERRORLOG contains the error logs for DTP errors. These errors logs include loads for master data for duplicate records and customer specific transformation routines. SAP Note 1095924 - Correction: Deletion/analysis report for error - provides a number of reports for handling the growth of this table.
Tables RSMON* (for example, table RSMONMESS) and tables RS*DONE (for example, table RSSELDONE) continuously increase in size in the BW system with each request that is created. This data can be archived in a BW 7 system but there is no possibility to delete records in BW 3.5.
Have a look at help.sap.com for further information:
http://help.sap.com/saphelp_nw70/helpdata/EN/42/ead8d7b55e1bd2e10000000a11466f/frameset.htm
Please review SAP Note 706478 for information on managing the size and growth of your basis tables.
7.Process Chain Performance
From the process chain monitor get the step that is causing the performance issue and optimize that step. Follow the recomendations given above if the performance is degraded because of PSA, DSO, DTP.
If you have performance problem in RSPCM transaction create an index on EDIDC including the fields MANDT, CREDAT and MESTYP. Additionaly try to archive the tables such as RSMONMESS etc.
Header Data
| Release Status: | Released for Customer |
| Released on: | 13.04.2012 07:58:20 |
| Master Language: | English |
| Priority: | Recommendations/additional info |
| Category: | FAQ |
| Primary Component: | BW-WHM Data Warehouse Management |
| Secondary Components: | SV-BO-BI Business Information |
Affected Releases
Release-Independent
Related Notes
1 comment:
Hey,
I noticed your Article. I just loved it.
Experience one of the sap fico Training in hyderabad and take your carrier to next level.
If you like it feel free and share it.
Cheers,
Varsha.
Post a Comment