Scribd Logo
Upload

Welcome to Scribd!

  • 278 views

    Tcode

    Uploaded by

    vlsharma7
    This document provides a list of SAP transactions and reports used for system monitoring and reorganization. It includes descriptions of what each transaction and report is used for, and recommended job names and frequencies for scheduling regular runs of the reports. Roadmaps are also provided for analyzing different types of performance problems and checking database memory, I/O, cache, and CPU utilization.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd

    Tcode

    Uploaded by

    vlsharma7
    278 views11 pages
    This document provides a list of SAP transactions and reports used for system monitoring and reorganization. It includes descriptions of what each transaction and report is used for, and recommended job names and frequencies for scheduling regular runs of the reports. Roadmaps are also provided for analyzing different types of performance problems and checking database memory, I/O, cache, and CPU utilization.

    Original Title

    tcode

    Copyright

    © Attribution Non-Commercial (BY-NC)

    Available Formats

    PDF, TXT or read online from Scribd

    Did you find this document useful?

    Is this content inappropriate?

    This document provides a list of SAP transactions and reports used for system monitoring and reorganization. It includes descriptions of what each transaction and report is used for, and recommended job names and frequencies for scheduling regular runs of the reports. Roadmaps are also provided for analyzing different types of performance problems and checking database memory, I/O, cache, and CPU utilization.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    278 views11 pages

    Tcode

    Uploaded by

    vlsharma7
    This document provides a list of SAP transactions and reports used for system monitoring and reorganization. It includes descriptions of what each transaction and report is used for, and recommended job names and frequencies for scheduling regular runs of the reports. Roadmaps are also provided for analyzing different types of performance problems and checking database memory, I/O, cache, and CPU utilization.

    Copyright:

    Attribution Non-Commercial (BY-NC)
    Download as PDF, TXT or read online from Scribd
    Download as pdf or txt
    of 11

    AL08 Users logged on

    DB01 Database Lock Monitor


    DB02 tables and indexes monitor
    DB13 DBA Planning Calendar
    Se30 ABAP Objects Runtime analysis
    SM02 System messages
    SM12 Single transaction analysis
    SM13 analysis & monitoring tool collection
    SM21 System Log
    SM22 application Analysis
    SM37 Simple job selection
    SM66 System wide work process overview
    SMICM ICM Monitor
    SMGW Gateway Monitor
    SP01 Output Controller
    SP02 Display spool requests
    SPAD Spool administration
    ST01 system trace
    ST02 setup/tune buffers
    ST03 performance, sap statistics, workload
    ST03N Global workload statistics
    ST04 db performance monitor
    ST04_MSS monitoring sql server (remote/local)
    ST05 performance trace
    ST06 operating system monitor
    ST07 application monitor
    ST10 Table call statistics
    ST11 display developer traces
    ST22 ABAP dump analysis
    STAD Statistics display for all systems
    STATTRACE Global statistics & traces
    RZ21 Monitoring: Properties and Methods used to verify db os collector
    RZ20 CCMS Monitor Sets used to verify db os collector
    AL15 SAPOSCOL destination used to verify db os collector
    RZ21 Monitoring: Properties and Methods
    RZ20 CCMS Monitor Sets
    OS07 OS Collector
    sm19 audit log configuration
    sm20 audit log
    su53 Display authorization data
    ST13 Tool RSECNOTE
    RZ04 Operation Modes
    SM63 periods for the operation modes
    se10 change request
    d to verify db os collector
    d to verify db os collector
    d to verify db os collector
    CPU utilization idle / hr >20% / > 35% (optimally)
    IO utilization < 50%
    paging rate / hr < 20%
    response time < 1000ms
    wait time < 10% of response time
    cpu time < 40% of response time
    database time < 40% of response time
    load time < 50ms
    roll-in / roll-out time < 20ms
    GUI Time < 200ms
    expensive sql < 5% of total database time in a SAP system
    lock time < 5ms
    buffer hit ratio > 95%
    Parallel to the roll-out, the dispatcher sends
    the response to the front end. Therefore, roll-out time, although measured, is
    Roll-out time no direct part of the response time!

    Wait time, roll-in time, load and generation time, enqueue time, database request,
    and (optionally) roll-wait time contribute to the dialog response time. Thus,
    processing time is calculated by subtracting these components from the dialog response time.

    RFC+CPIC time consists of the time


    needed for establishing the RFC communication, the time needed for roll-out, the
    roll wait time and the subsequent roll-in time.

    Roadmap for Analyzing Performance Problems


    0
    9
    0
    5 High wait time: Insufficient number of free work processes
    0
    9
    0
    5 High roll-wait time: Communication problem with GUI, external system,
    or large amount of data requested
    0
    9
    0
    5 High load and generation time: SAP buffers (Program, CUA or Screen)
    too small
    0
    9
    0
    5 High database request time: CPU/memory bottleneck on database server;
    communication problem with database server, expensive SQL statements,
    database locks, missing indexes, missing statistics or small database buffer(s)
    0
    9
    0
    5 High CPU time: Expensive ABAP processing, for example, processing
    large tables; inefficient programming
    0
    9
    0
    5 Processing time more than twice CPU time: CPU bottlenecks
    me, although measured, is
    Virtual memory = Physical memory and swap memory
    Virtual memory = Shared memory and local memory (allocated at instance start), heap memory (allocated on demand)
    Shared memory = buffer memory, extended memory, roll buffer (roll file), sap paging buffer (page file)

    Problems with the SAP memory configuration may be indicated if:


    0
    9
    0
    5 For extended memory: Max use is more than 80% of In memory (Extended
    Memory only exists in memory).
    0
    9
    0
    5 For roll area: Max use is more 80% of In memory (part of the roll data might
    be stored on file level)

    Memory Allocation Sequence for Dialog Workprocesses in Detail, Avoiding PRIV mode
    Roll Memory up to ztta/roll_first
    EM up to ztta/roll_extension or EM exhausted (shared memory)
    Roll memory reminder of ztta/roll_area
    Heap memory up to abap/heap_area_dia or HM exhausted

    Memory Allocation Sequence for non-Dialog Workprocesses on all platforms except windows
    Roll memory reminder of ztta/roll_area
    Heap memory up to abap/heap_area_dia or HM exhausted
    EM up to ztta/roll_extension or EM exhausted (shared memory)
    , heap memory (allocated on demand)
    ging buffer (page file)

    ms except windows
    Report Frequency Recomm. Jobname, add. Notes
    RSBTCDEL daily SAP_REORG_JOBS, RSBTCDEL2 w/ note 525933

    RSPO0041 daily SAP_REORG_SPOOL

    RSPO1041 daily SAP_REORG_SPOOL, note 130978

    RSPO1043 daily SAP_REORG_TSP, note 98065

    RSBDCREO daily SAP_REORG_BATCHINPUT

    RSBPSTDE monthly SAP_REORG_JOBSTATISTIC

    RSSNAPDL daily SAP_REORG_SNAP

    RSBPCOLL daily SAP_COLLECTOR_FOR_ JOBSTATISTIC

    RSBTCPRIDEL monthly SAP_REORG_PRN, note 307970

    RSAL_BATCH_TOOL_ DISPATCHINGhourly SAP_REORG_TOOL_DISP

    RSXMILOGREORG weekly SAP_REORG_XMI, note 182963

    RSTS0024 weekly SAP_REORG_JOB2, note 666290


    Short Description scheduled?
    Report RSBTCDEL deletes entries from tables BTC* that contain yes
    background job administration data.
    Report RSPO0041 deletes entries from spool tables TSP* that contain yes
    spool job administration data and spool data.
    Report RSPO0041 deletes entries from spool tables TSP* that contain yes
    spool job administration data and spool data.
    Report RSPO1043 deletes inconsistent objects in spool tables TSP* that no
    contain spool job admin data
    Report RSBDCREO deletes entries from BDC* and APQ* tables that yes
    contain Batch Input administration data.
    Report RSBPSTDE deletes entries from tables BTCJSTAT, and deletes by yes
    this statistics for background job runtimes.
    Report RSSNAPDL gradually deletes old short dumps that are not marked yes
    for retention from the SNAP table.
    Report RSBPCOLL collects runtime statistics of background jobs which are yes
    used e.g. for an SAP Going Live check.
    Report RSBTCPRIDEL reorganizes print parameters for background jobs no
    that before 4.6A had been deleted by RSBTCDEL
    Report RSAL_BATCH_ TOOL_DISPATCHING is necessary to start method no
    dispatching for SAP system monitoring in the background
    Report RSXMILOGREORG reorganizes the table TXMILOGRAW which yes
    contains log info on the XMI interface.
    Report RSTS0024 deletes job logs that no longer belong to any job and no
    orphaned jobs after run of RSBTCDEL.
    daily
    DB IO
    - PAGEIOLATCH_SH: < 20 ms/request
    Typical values are in the range of 4 to 10 ms/request.

    - WRITELOG: < 10 ms/request


    Typical values are in the range of 1 to 5 ms/request.
    When using these counters for short time intervals (as the 20
    minutes used in the SAP database monitor) reference values
    twice as high can be used.

    - It is reasonable to expect values less then 10 ms/read on data files


    and less then 5 ms/write on transaction log files.

    use master;
    select * from sys.configurations;
    select @@version;
    go

    DB memory
    Before increasing SQL Server memory, you must check if there is sufficient main memory available.
    Operating system paging is a sign of insufficient main memory; especially on the database server.
    Call Transaction ST06 and choose Detail analysis menu → F2 00 Previous hours → F2 00 Memory. The amount
    of page in per hour should not exceed 20% of the available physical memory. For optimal
    performance, the value should be 0.

    DB cache

    average percentage of requested data pages found in the cache. This is the average value since
    startup. The value should always be above 98 (even during heavy workload). If it is significantly
    below 98, the data cache could be too small. To check the history of these values, use Transaction
    ST04 and choose Detail analysis menu → 2F 00 Performance database. A snapshot is collected every 2
    hours.

    DB CPU
    The value for CPU busy (2) should always be approximately < 70%, that is, CPU idle > CPU busy / 2
    Memory. The amount

    You might also like

    pFad - Phonifier reborn

    Pfad - The Proxy pFad of © 2024 Garber Painting. All rights reserved.

    Note: This service is not intended for secure transactions such as banking, social media, email, or purchasing. Use at your own risk. We assume no liability whatsoever for broken pages.


    Alternative Proxies:

    Alternative Proxy

    pFad Proxy

    pFad v3 Proxy

    pFad v4 Proxy