BI Basis Configuration
© SAP 2008 / Page 2
1. Overview - Parameterization
2. Database Parameterization
3. Basis Parameterization
4. Work Process Configuration
Agenda
© SAP 2008 / Page 3
BI technical parameterization
Where can I get recommendations on technical parameterization for BI?
SAP GoingLive Check
SAP EarlyWatch and EarlyWatch Alert
SAP Notes
Database documentation
© SAP 2008 / Page 4
Description – SAP BI GoingLive Check
The SAP GoingLive Check – 3 sessions delivered by certified consultants through a remote connection
Sizing verified with the Quicksizer Report details if hardware resources and parameter settings are sufficient
Analysis
Session
Checks core queries and uploads for performance improvement possibilities
Report details query and upload response times. Where necessary, performance improving recommendations are given.
Optimization
Session
Check of the system to verify hardware and parameter settings Report confirms system configuration and makes recommendations
when necessary
Verification
Session
© SAP 2008 / Page 5
EarlyWatch Alerts
EarlyWatch Alert (EWA):
• Automated service for collecting performance and administration data
• Trend analysis of system
• Free of charge
• Provides recommendations
• Described in note 207223 (activation of service)
• Frequency Weekly
Checked areas and alerts
© SAP 2008 / Page 6
1. Overview - Parameterization
2. Database Parameterization
3. Basis Parameterization
4. Work Process Configuration
Agenda
© SAP 2008 / Page 7
Database Parameters - Oracle
As of Oracle 10g, there is a uniform parameterization recommendation for all systems (BI, R/3…)
Can check the most important parameters via transaction RSRV => Database => Check database parameter(s)
SAP Notes:
830576 Parameter recommendations for Oracle 10g
720886 “Oracle Database 10g: Integration in the SAP environment”.
Oracle 10.2
© SAP 2008 / Page 8
Database Parameters - Informix
BI and R/3 Systems can differ significantly in terms of the configuration of the database.
Note 181945: Performance guide: BW on Informix
Neither s
upported nor
planned for N
etWeaver 7
.0
(PAM 05-2006 )
© SAP 2008 / Page 9
Database Parameters – MS SQL Server
In Microsoft SQL Server the installation and upgrade processes take care of most of the SAP Database configuration details.
SAP Notes:
Note 327494 Configuration Parameters for SQL Server 2000
Note 879941 Configuration Parameters for SQL Server 2005
Microsoft SQL Server 2000, 2005
© SAP 2008 / Page 10
Database Parameters – DB2/LUW (DB6)
SAP Notes:
Note 374502 DB6 DB2 UDB-BW Performance-Overview of notes
Note 546262 DB6: Administration & Performance on SAP BW, SAP SCM, SAP SEM
Note 899322 DB6: DB2 9 Standard Parameter Settings
Note 930487 DB6: Using DB2 9 with SAP Software
DB2/UDB has been renamed to DB2/Linux Unix Windows (LUW)
DB2/LUW 8, 9
© SAP 2008 / Page 11
Database Parameters – DB2 0S/400
DB2/400 V5R3, V5R4
SAP Notes:
Note 541508: iSeries: Check the system parameters for BW
Note 307077: iSeries: Performance Optimization for BW Systems
© SAP 2008 / Page 12
Database Parameters – DB2/zOS
SAP Note 390016 DB2/390: BW: DB settings and performance
Configuration parameters are available in the guide
SAP Database Administration Guide for SAP NetWeaver on IBM DB2 UDB for z/OS SAP NetWeaver 2004s SR1
The guide can be accessed here:
http://service.sap.com/instguides => operations => Database specific guides => SAP DBA Guide for DB2
DB2/zOS V8
© SAP 2008 / Page 13
Database Parameters – MaxDB
SAP Notes:
Note 814704: MaxDB Version 7.6 parameter settings for OLTP/BI
MaxDB Version 7.6
You should also refer to Note 514907 for information about settings for the RSADMIN parameters. For MaxDb, you should set the RSADMIN parameters as follows:
SPLIT_DATAMART_TABL_THRES <= 254 (MaxDB Version 7.6)
SPLIT_QUERY_TABL_THRES <= 254 MaxDB Version 7.6)
© SAP 2008 / Page 14
1. Overview - Parameterization
2. Database Parameterization
3. Basis Parameterization
4. Work Process Configuration
Agenda
© SAP 2008 / Page 15
BI Basis parameters
BI and R/3 Systems can differ significantly in terms of the
configuration of the SAP Basis parameters
SAP Note 192658 Setting basis parameters for BW Systems (extension to R/3 note 103747 Performance: Parameter recommendations for Rel. 4.0)
© SAP 2008 / Page 16
SAP Memory and Buffers - (ST02)
Program Buffer:More swaps acceptable than in R/3
Export/import:Used frequently. Large hierarchies
Exp/imp SHM:Contains the OLAP cache
Extended Memory:Heavy use per user (significantly more than in R/3)
Single record buffer:Master data tables Single record buffered by default
© SAP 2008 / Page 17
BI Basis parameters
Maximum runtime for a work process
The runtime of OLAP BI Queries can’t be compared to the runtime of an OLTP ERP transaction. Dialog processes are also used extensively in BI data loading
The runtime should be set higher than is usual in the R/3 System:rdisp/max_wprun_time 3600
If different settings are required for data loading and queries, refer to the following document:
How To…change the maximum dialog runtime of a process
Database Interface Oracle
Set the parameter large enough to keep the number of array inserts as low as possible (uploading data, roll-up). Depending on the size of the available main memory, set the dbs/ora/array_buf_size parameter to a value of 1000000 (1MB):dbs/ora/array_buf_size 1000000
© SAP 2008 / Page 18
Single record buffering for master data tables
BI Master data tables single record buffered by default
Can cause performance problems for large frequently changed tables during
- Data loading
- ODS activation
Consider deactivating buffering
for these tables or temporary
deactivation if the changes are
for the initial loads only and
the table is not large
© SAP 2008 / Page 19
ICM – Internet Communication Manager
The Internet Communication Manager (ICM)
is the component of the NetWeaver Application Server that receives and sends Web requests (HTTP, HTTPS, SMTP).
The processing timeout is the timeout between the HTTP request being issued and the HTTP response being received. (ICM can be server or client) (PROCTIMEOUT)
The keep alive timeout specifies how long the network should remain open after a request has been processed successfully so that the TCP/IP connection does not have to be reestablished if additional requests are received. (TIMEOUT, icm/keep_alive_timeout)
Kernel Release 6.40 and above
icm/server_port_: PROT=<xxxx>,PORT=<xxxx>,TIMEOUT=60, PROCTIMEOUT=3600
icm/keep_alive_timeout = 60
© SAP 2008 / Page 20
1. Overview - Parameterization
2. Database Parameterization
3. Basis Parameterization
4. Work Process Configuration
Agenda
© SAP 2008 / Page 21
Work Process Configuration
Work Process Type Report and Action (Seq. Read, Insert, Update...)
Table (DB operation)
User Status
DIA WPs: also used during loading to WRITE (insert/update) to tables
DTP is now using Background processes for data loading
BGD WPs: also used to READ during extraction from tables
used regularly to kick off process chain jobs
UPD WPs: used very rarely (can delete UPD2)
A SAP BI system has it’s own type of work process utilization
© SAP 2008 / Page 22
Update Work Processes
If there are no UP2 processes, the UPD processes take over both U1 and U2.
SAP BI does not need an UP2 process and at most 2 UPD processes NOT for BI based SEM BCS!
© SAP 2008 / Page 23
Dialog Processes
Used in BI for data loading (writing to tables) and during reporting.
DTP is now using Background processes for data loading
Upload parallel processes – TA SBIW (Table ROIDOCPRMS) , TA RSCUSTV6 (IDOC, flat file)
InfoPackage processing – “PSA and Data Targets in parallel“
ODS Activation processes – TA RSCUSTA2
Change run in parallel – Note 534630
Multiprovider – Parallel subquery: Notes 629541, 839252
Important BI customizing parameters affecting the use of dialog processes:
© SAP 2008 / Page 24
Background Processes
Mainly used for reading data during extraction, deletion of data, process chains management, aggregation and compression of requests.
NOW USED EXTENSIVELY IN DTP
Rule of thumb: #BTC = 2 * #CPUs not valid in all cases anymoreIf process chains are used intensively and complex scenarios with lots of subchains are designed, then a sufficient number of BTC processes need be configured
BTC (minimum) = number of parallel starting subchains at the widest part of the chain + 1 (SAP note 621400)
BTC (optimal) = number of parallel processes at the widest part of the chain + number of parallel subchains at the widest part + 1
ALSO NEED TO CONSIDER DTP
Special concerns for Background process use in BI
Sometimes it is useful to configure operation mode ’load‘ with more BTC processes and operation mode ‘reporting‘ with just a few BTC processes
© SAP 2008 / Page 25
DTP – Background Work Processes
DTP processing is done with Background Work Processes.
Advantages of Background Processing: Better monitoring Job protocol No time outs Process starts later when no background processes are free.
Dialog Work Processes are only used: When a local file is involved
DataTarget Open Hub, DataSource flatfile on local PC
During manual upload
© SAP 2008 / Page 26
Thank you!
Top Related