BWA 7.00: Analyzing write performance

[] [] [] [] [] [] [] [] [] [] [] []

Related:

  1. SAP BusinessObjects Explorer Performance & ReliabilitySymptom SAP Note 1366180 “SAP BusinessObjects Explorer PERFORMANCE & RELIABILITY”...
  2. BWA 7.00: Optimal settings for Intel Xeon 5570 CPUsSymptom You want to configure optimal settings for Intel Xeon...
  3. Upgrade Performance Problem mit ErweiterungenSymptom Sie beobachten beim Update eines ERP Systems auf ERP2005...
  4. BWA 7.00: Restricted Use of OCFS2Symptom If you observe one or more of the following...
  5. BIA 7.00: reduce amount of parallel queriesSymptom You experience a high memory consumption on some or...
  6. BWA 7.00: Sizing figureSymptom You want to find out whether your BWA sizing...
  7. BWA 7.00: Indexing fails due to GPFS issueSymptom Filling, rollup or changerun of BWA indexes fails Other...
  8. DB2-z/OS: Bad performance in method READ_SR_ACTIVITYSymptom DB2 is not using multiple index operation for the...

Symptom

You find that indexing in SAP NetWeaver BW Accelerator is slow and you want to check whether the write calls to the BWA filer are slow.
Other terms

BIA, BWA, Accelerator, performance, rollup, changerun, filer, initial filling
Reason and Prerequisites

You find that BWA indexing calls are taking a long time to execute and you want to check whether the write calls to the BWA filer are responsible for the slow execution.
Solution

Raise trace level for BWA components “indexoptperf” and “AttrTempFilePerf” to “DEBUG”.
To raise a trace level, you can use the TREX standalone admin tool or the SAP transaction TREXADMIN: in view “Trace” press button “Levels …” and choose Service “Indexserver”.
The new trace level is activated when you save the change. You do not need to restart the TREX index server.
Note:You should only raise the trace level if you are asked to do so by an SAP support engineer.

[Slashdot] [Digg] [Reddit] [del.icio.us] [Facebook] [Technorati] [Google] [StumbleUpon]

Leave a Comment