SAP BW Online Training|SAP BW Online Course|SAP BW Online Trainer
BW sys management - All Questions - SAP Q&A · 2019-11-12 · SAP AG2004, S P TechEd / BW 201 / 5...
Transcript of BW sys management - All Questions - SAP Q&A · 2019-11-12 · SAP AG2004, S P TechEd / BW 201 / 5...
Know-How Network: Effective SAP BW System Management
Ron SilbersteinTechnologist & Architect SAP NetWeaver Regional Implementation Group SAP Labs, LLC
SAP AG 2004, SAP TechEd / BW 201 / 2
Agenda
Overview
Process Chainsn Key Conceptsn Implementation
System Monitoring
Data Management
Capacity Planning
Summary
SAP AG 2004, SAP TechEd / BW 201 / 3
Learning Objectives
As a result of this workshop, you will be able to:n Understand key concepts of BW system managementn Develop enhanced strategies for effective BW system
managementn Incorporate best practices into BW system management
procedures
SAP AG 2004, SAP TechEd / BW 201 / 4
Agenda
Overview
Process Chainsn Key Conceptsn Implementation
System Monitoring
Data Management
Capacity Planning
Summary
SAP AG 2004, SAP TechEd / BW 201 / 5
Collaborative efforts: technical and functional team members
Exploit all advantages of process chains: automate all key system activities
Proactive monitoring: Utilize the available tools to their potential, optimize accordingly
Data management: Consistently delete temporary data, summarize, consolidate and reduce data volume; minimize object sizes
Plan for growth: Sound capacity planning ensures system sizing and resource allocation is commensurate with user load and data volume growth rates
Service excellence: Vigilance in providing strong and performant SAP BW production environment AND attentively support ongoing development phases, ensuring quality via change management process
Characteristics of Effective SAP BW System Management
SAP AG 2004, SAP TechEd / BW 201 / 6
Ongoing Maintenance and Optimization Efforts
Monitoring and System Management
Performance Tuning and Optimization
EvaluationIdentify BottlenecksCoordinate EffortScheduling
Tactical TuningResource Allocation Track ConcernsManage Data Volume
SAP AG 2004, SAP TechEd / BW 201 / 7
Agenda
Overview
Process Chainsn Key Conceptsn Implementation
System Monitoring
Data Management
Capacity Planning
Summary
SAP AG 2004, SAP TechEd / BW 201 / 8
Process Chains Motivation & Key Functionality
Automation of key SAP BW operational activities: data load and other tasks (ie compression, aggregate rollup, reporting agent)
Graphical modelling: build a control flow of tasks to be executed in a defined sequence
Central monitoring of SAP BW operational activities
Ability to Create and implement a custom process type: powerful!
These activities may require a significant administrator effort, without using process chains, risks include:
•Inefficient utilization of BW and basis teams’ time•Possibility of missed activities, , human error•Limited monitoring capabilities
Some Important Process Chains Features:
Openness: Interface for Job Scheduling for SAP BW (Integration scenario to process chains for certified partners)
SAP AG 2004, SAP TechEd / BW 201 / 9
Process Chains Concepts: Typical Data Load Cycle
Data Load Monitor
Other Monitors
Start
Change Run (MD activation)
Data loaded into ODS
Object
Activate ODS Object data
Data loaded into InfoCubeRoll up
Aggregates
Reporting Agent Jobs
Load Master Data
Data Mining Jobs
SAP AG 2004, SAP TechEd / BW 201 / 10
Concept Example: Building a process control flow
Start
IC Data Load 1
Failure
IC Data Load 2
IC Data Load 3
Success off all 3? Failure
Email System Admin
Failure
Email System Admin
Load 3 InfoPackages concurrently into 1 InfoCube
Rollup Aggregates
Load Master Data
Activate Master Data
Success
Success
Email System Admin
Failure
Email System Admin
Perform change run (master data activation)
SAP AG 2004, SAP TechEd / BW 201 / 11
Process Chains Graphical Modeling and Monitoring
SAP delivers
many
process types!
SAP AG 2004, SAP TechEd / BW 201 / 12
Process Chains: Log View (aka Monitoring View) - RSPC
Process in Green shows a successful completion
Processes in Red indicate a failure
Processes in Grey have yet to be executed
Note: CCMS has an overview of process chain successes and failures
SAP AG 2004, SAP TechEd / BW 201 / 13
BMC (Control-M)CA (Unicenter job mgmt adapter)TIDAL (Enterprise Scheduler)UC4 (UC4 Global)ORSYP (Dollar Universe)Redwood (Europe) (Cronacle)
CA
Certified scheduling/monitoring tools offering integration with process chains:
Third-Party Scheduling & Monitoring Tools BW-Certified
SAP AG 2004, SAP TechEd / BW 201 / 14
Agenda
Overview
Process Chainsn Key Conceptsn Implementation
System Monitoring
Data Management
Capacity Planning
Summary
SAP AG 2004, SAP TechEd / BW 201 / 15
Project Preparation Final
PreparationRealization Go Live &SupportBusiness
Blueprint
ContinuousImprovement
Project planning and project organization
Project planning§ Process chains should be designed after modelling data flows but
during the realization phase§ Use the final preparation phase of your project to test your process
chains for performance, correctness and robustness
Project organization§ Team members must be able to use process chains, but also need
knowledge about:§ Data warehouse administration § Single process types used in process chains
§ If several project teams build process chains in the same system, a central documentation process is critical
SAP AG 2004, SAP TechEd / BW 201 / 16
How to start – process overview
Collect all processes that have to run before data can be released to end user§ Data Loading processes§ Administration processes§ Reporting Agent processes
Define time windows for process chains § Requirements on data availability from business § Contact basis administration team for information on jobs in source
systems that have to run before data loading
Define dependencies and priorities§ Define whether one or several predecessors processes have to run
before a single process can start§ Define whether a single process has to run when the process chain is
executed or whether failures can be (temporarily) accepted
What ?
When ?
How ?
SAP AG 2004, SAP TechEd / BW 201 / 17
Example on process overview
possible additional fields:
Reporting Scenario, for example “Sales statistics”
* Not always necessary, sometimes needed as of different time zones or different source data availability in one source system
*
Collect all relevant processes in a central document to prepare modelling of process chains
SAP AG 2004, SAP TechEd / BW 201 / 18
Aspects of using process chain hierarchies
Complexity of a single chain (number of processes) should be reasonable§ “One process chain for everything” approach could create
(unwanted) cross dependencies between processes
§ Benefits on using process chain hierarchies (sub chains)§ Better visualization of dependencies
§ Enhanced administration capabilities
(e.g. Restarting of single sub chain)
§Maximum number of process chain hierarchy levels: 2 – 3 (recommendation)
SAP AG 2004, SAP TechEd / BW 201 / 19
Common SAP BW Tasks: Process Chain Automation
Data Load (all kinds)
ODS Object Activation
Aggregate Rollup
InfoCube Compression
DB statistics (RDBMS dependent)
Change Run
PSA Deletion
Strongly Recommended Highly Recommended
Reporting Agent: OLAP Cache
Reporting Agent: Pre-calculated Templates
Reporting Agent: Exceptions & Conditions
Master Data Reorganization
Local Process Chain
Other tasks, such as export of data via Open Hub, should be utilized as needed.
SAP AG 2004, SAP TechEd / BW 201 / 20
Agenda
Overview
Process Chainsn Key Conceptsn Implementation
System Monitoring
Data Management
Capacity Planning
Summary
SAP AG 2004, SAP TechEd / BW 201 / 21
Some Important Monitoring Tools
Scenarion Generally slow query or data load performance (systemic)n Look for CPU utilization bottlenecksn If adequate CPU time is available, check other factors
What can you check?n Operating system (ST06)n Database Information (DB02)n Database monitor (ST04)n Analysis of BW objects (RSRV)n Performance Analysis (ST03, BW Statistic Business Content)n Computer Center Management System (BWCCMS)n Memory Management (ST02)
SAP AG 2004, SAP TechEd / BW 201 / 22
Monitoring Tools: Operating System Monitor (ST06)
Useful Key Figuresn Current Values (snapshots) and history (previous hours)
uCPUuMemoryuSwap
Check following parameter values:n CPU utilizationn Free memoryn Also check SM50 for process bottlenecks
SAP AG 2004, SAP TechEd / BW 201 / 23
Monitoring Tools: Database Monitor (DB02)
Utilizationn General DB Monitorn Check for missing indices
Useful Featuresn Missing indicesn Table and Index extent growth (non-local
tablespaces, RDBMS dependent)n Monitor tablespace allocation
SAP AG 2004, SAP TechEd / BW 201 / 24
Tools: Analysis and Repair of BW Objects (RSRV)
UtilizationMany various analyses of InfoCubes and master data
Useful Featuresn Database
uDB statistics for an InfoCube and its aggregatesuDB indices for an InfoCube and its aggregatesuDB parameter settings checkuDB Information about InfoProvider tables
l InfoCube: Relative size of dimension tables compared to fact table
n “Repair” feature
Check following parameter values:n Ensure DB statistics are up-to-date for an InfoCuben Ensure indices exist for InfoCuben Check for unbalanced InfoCubes
u(dimension table size 10% or more compared to fact table size)
SAP AG 2004, SAP TechEd / BW 201 / 25
SAP BW Reporting Performance Analysis Tools
BW Statistics Business Content
SAP BW Workload Analysis –ST03
Tip: Build a monitoring cockpit using BW statistics content, custom query and BW web applications
SAP AG 2004, SAP TechEd / BW 201 / 26
Monitoring Tools: ST03 - Drill Down to Query
Double Click
Highest contributor in Total Run Time per
InfoCube
High % DB Time
Drill down – check if there is any single query that could be the major contributor. Where is the major contribution coming from?
Example shows an active query, high DB time, with low OLAP & front-end time.
No of runs
Highest DB time
Low Front-end
time
SAP AG 2004, SAP TechEd / BW 201 / 27
System-wide monitoring with BWCCMS
The CComputing CCenter MManagement SSystemis part of SAP’s technolgy platform.
CCMS is SAP’s open, integrated infrastructure for:
n Centrally monitoring SAP landscapes comprising:u Components based on SAP Web Application
Server, or SAP Basis Release as of 3.0u Other SAP componentsu Non-SAP components
n Background and print processingn New with BW Release 3.52: n History data of the Central Performance History (CPH) can be transferred to SAP BW for efficient analysis
SAP AG 2004, SAP TechEd / BW 201 / 28
SAP Solution Manager: Central System Administration
n Central administration of systemsin one SAP solution
n SAP Solution Manager, Central Monitoringfeature
n Automated support of periodic and sporadic administration tasks
n Time savings due to central access to administered systems
n Automated logging of activitiesn Reporting across the whole solution
Task
Solution
Benefits
SAP AG 2004, SAP TechEd / BW 201 / 29
SAP Solution Manager
Satellite Systems
System Monitoring
Continous Monitoring:Service Data Download
(SDCC)
Continous Monitoring:Service Data Download
(SDCC)
Real-time Monitoring:CCMS Monitoring
Infrastructure (RZ20)
Real-time Monitoring:CCMS Monitoring
Infrastructure (RZ20)
SolMan System & Solution Monitoring – Data Collection
SAP EarlyWatchAlerts
Detailed Reporting
SAP AG 2004, SAP TechEd / BW 201 / 30
Solution Manager System Monitoring – Workflow
n System monitoring of core components to detect critical situations as early as possible
n Support administrators working with new SAP products
n System monitoring and Central System Administration complement each other
Expert monitors directly linked in satellite systems
Expert monitors directly linked in satellite systems
Alert graphicsAlert graphicsSystem-related tasks with integrated and automated log
System-related tasks with integrated and automated log
SAP AG 2004, SAP TechEd / BW 201 / 31
Solution Manager Monitoring: Integration of 3rd-Party Tools
SAP Solution Manager
CCMS Monitoring Infrastructure (“RZ20)
MonitoringInfrastructure
SolutionLandscape
Monitoring Agent
3rd-Party Components
Report Alerts
3rd-Party System
Management Console
Trigger consolein case of an alert(SAPConnect;SNMP; XML)
Detailed Analysiswith 3rd-party tools
SolutionMonitoring
SAP AG 2004, SAP TechEd / BW 201 / 32
Agenda
Overview
Process Chainsn Key Conceptsn Implementation
System Monitoring
Data Management
Capacity Planning
Summary
SAP AG 2004, SAP TechEd / BW 201 / 33
What about your Data Volume growth?
0.00
100.00
200.00
300.00
01.0
3.20
02
01.0
4.20
02
01.0
5.20
02
01.0
6.20
02
01.0
7.20
02
01.0
8.20
02
01.0
9.20
02
01.1
0.20
02
01.1
1.20
02
01.1
2.20
02
01.0
1.20
03
01.0
2.20
03
01.0
3.20
03
01.0
4.20
03
01.0
5.20
03
01.0
6.20
03
01.0
7.20
03
01.0
8.20
03
01.0
9.20
03
DB growth:~15 GB/month
'Without'Archiving
InitialArchiving
Reduction:~60GB
With regular archiving
DB growth: ~7 GB/month
Allocated DB content
400.00
500.00
600.00
700.00 Expected size
without Archiving
Allocated DB size
SAP AG 2004, SAP TechEd / BW 201 / 34
Distribution of the memory costs
“ Hard disk costs do not even represent a quarter of the memory costs “(Giga Information Group)
“ Administrative expense for 1 Terabyte of memory are appropriate for five to seven times more higher than the memory costs themselves “(Dataquest/Gartner)
Misc (Purchasing,
training)
10%
Environment(Electricity, Space)
3%
Storage-Mangement
(Soft- & Hardware)
19%
Hard disk 23%
Personel45%
SAP AG 2004, SAP TechEd / BW 201 / 35
Data Aging Strategy Implementation
üüFrequently read /updated data
Very rarelyread data
Infrequentlyread data
üüüüüü
üüüü
BW data archiving
Near line Storage
Online DatabaseStorage
Data aging is a strategy for managing data over time, balancing data access requirements with TCO. n Each data aging Strategy is uniquely determined by the customer’s
data and the business value of accessing the data.
Which tools should I consider to use when?
SAP AG 2004, SAP TechEd / BW 201 / 36
PSA Deletion: Temporary inbound data load layer, exists for recovery or reload purposes. l Retain daily loads 1 week, monthly retain 60 daysl Customer example: DB growing at 450 GB/month
without PSA deletion, 150 GB/month with deletion
ODS Object Change Log Deletion: It’s like a PSA. l Optimize ODS Object activation performance
Caution: Do not delete if ODS Object “generates” delta for the next level!
Data Consolidation: Eliminate redundant datal Merge data from similar data martsl Optimize aggregatesl Consider carefully number of ODS Object and InfoCube
levels; aggressively archive and delete from “Data warehouse” layer
l Summarize at the InfoCube and aggregate level (RRI)
Remote Access: Use RRI, Virtual InfoProviders, UDI, etc: operational processing possibly might remain in OLTP system
Data Volume Minimization Strategies
SAP AG 2004, SAP TechEd / BW 201 / 37
Agenda
Overview
Process Chainsn Key Conceptsn Implementation
System Monitoring
Data Management
Capacity Planning
Summary
SAP AG 2004, SAP TechEd / BW 201 / 38
Multi-Tier Architecture & System Landscape
Scalability via multiple application servers
Architecture of SAP basis system supports multi-user environment: If number of concurrent users grows significantly, you can add more application servers
SAP AG 2004, SAP TechEd / BW 201 / 39
SAP BW CPU Sizing Approach (Quicksizer)
90%10%0%Authors & Analysts
0%50%50%Knowledge Workers
0%10%90%Information Consumers
HeavyMediumEasy
Use
r cat
e gor
y
Analytical Complexity
high
Consumer
Analyst
Author
Information Consumers
Knowledge Workers
Authors & Analysts
~ 70%
~ 30%
~ 10%
Low
Assumptions and Findings:
üOne navigation in BW (drill-down, filter, etc.) = ~9 dialog steps
üA medium type query is1.5x the load on the DB server as an easy query
üA heavy query exerts 5 times the load on the DB server as an easy query
üUsers of a specific category do not only run queries of the corresponding category
Query Type: Distribution Assumptions
SAP AG 2004, SAP TechEd / BW 201 / 40
Sizing and Re-sizing: Preparing for New Project Phases
SAP recommends to work closely with the hardware vendors to ensure your system is sized properly
Quicksizer: SAP-delivered tool for estimating hardware sizing requirementsn Only useful in conjunction with HW vendor assistance
Estimates of concurrent user load and data volume, if obtained at project startup, may not be sufficient for future project phased implementations!
Recommendations: If project scope changes significantly (in terms of expected data volume or number of concurrent users), conduct a capacity planning session where sizing estimates are revisitedn Work with business owners to get realistic user numbersn Analyze to estimate potential data volumen Use the Quicksizer in re-sizingn Work with hardware vendors
SAP AG 2004, SAP TechEd / BW 201 / 41
Summary
n Use process chains heavily to automate and monitor critical and important system tasks
n Build process chain development into project plan, organize effort around comprehensive BW administration strategy
n Good use of available tools for system monitoring can help ensure a smooth running system and good performance
n Best practices for data management entails deleting PSA data regularly, active capacity planning, use of archiving and consideration of near-line storage option
n Effective collaboration between technical and functional team members is necessary for successful BW system management
SAP AG 2004, SAP TechEd / BW 201 / 42
è Public Web:http://www.sap.com > Solutions > NetWeaver
è SAP Online Help:http://help.sap.com > NetWeaver > BI
è SAP Service Marketplace:
http://service.sap.com/bwlBW InfoIndex – Process ChainslBW InfoIndex – ArchivinglBW InfoIndex – BW StatisticslPartner – Certified Software Partnerswww.service.sap.com/educationlBW360 BW Administration & Performance (5 days)
Further Information
è SAP Developer Networkhttp://www.sdn.sap.com > Business information Warehouse
SAP AG 2004, SAP TechEd / BW 201 / 44
nNo part of this publication may be reproduced or transmitted in any form or for any purpose without the express permission of SAP AG. The information contained herein may be changed without prior notice.nSome software products marketed by SAP AG and its distributors contain proprietary software components of other
software vendors.nMicrosoft, Windows, Outlook, and PowerPoint are registered trademarks of Microsoft Corporation. n IBM, DB2, DB2 Universal Database, OS/2, Parallel Sysplex, MVS/ESA, AIX, S/390, AS/400, OS/390, OS/400, iSeries,
pSeries, xSeries, zSeries, z/OS, AFP, Intelligent Miner, WebSphere, Netfinity, Tivoli, and Informix are trademarks or registered trademarks of IBM Corporation in the United States and/or other countries.nOracle is a registered trademark of Oracle Corporation.nUNIX, X/Open, OSF/1, and Motif are registered trademarks of the Open Group.nCitrix, ICA, Program Neighborhood, MetaFrame, WinFrame, VideoFrame, and MultiWin are trademarks or registered
trademarks of Citrix Systems, Inc.nHTML, XML, XHTML and W3C are trademarks or registered trademarks of W3C®, World Wide Web Consortium,
Massachusetts Institute of Technology. n Java is a registered trademark of Sun Microsystems, Inc.n JavaScript is a registered trademark of Sun Microsystems, Inc., used under license for technology invented and
implemented by Netscape. nMaxDB is a trademark of MySQL AB, Sweden.nSAP, R/3, mySAP, mySAP.com, xApps, xApp, SAP NetWeaver and other SAP products and services mentioned herein
as well as their respective logos are trademarks or registered trademarks of SAP AG in Germany and in several other countries all over the world. All other product and service names mentioned are the trademarks of their respective companies. Data contained in this document serves informational purposes only. National product specifications may vary.nThese materials are subject to change without notice. These materials are provided by SAP AG and its affiliated
companies ("SAP Group") for informational purposes only, without representation or warranty of any kind, and SAP Group shall not be liable for errors or omissions with respect to the materials. The only warranties for SAP Group products and services are those that are set forth in the express warranty statements accompanying such products and services, if any. Nothing herein should be construed as constituting an additional warranty.
Copyright 2004 SAP AG. All Rights Reserved