Skip to Content

Welcome at the SAP on IBM i update! This time I have the pleasure to forward a contribution out of our development team, stuff you really will benefit from:

 

Database monitoring is a key element to support performance analysis in SAP installations. Information about table sizes and growth, usage statistics and SQL statements can be analyzed using SAP transactions DB02, ST04 and DBACOCKPIT. Up to now, database performance analysis on DB2 for IBM i was bound to an ABAP application server, because the background jobs to collect statistical data for the database were all executed in the ABAP application server. As SAP is integrating more and more monitoring functions into the SAP Solution Manager, this old concept is no longer working well. Beginning last year, the SAP on IBM i Porting team has started a major project to rework the database monitoring functions with SAP on DB2 for IBM i.

Independent Backend for Data Collection

The first step consisted in the separation of the collection component from the ABAP application server. The new SAP Database Performance Collector for IBM i can run on IBM i V5R4 and higher releases. It is shipped through the SAP Software Distribution Center with the latest SAPHOSTAGENT package in release 7.20 or 7.20 EXT and can be installed independent from any SAP system, so it can monitor even Java only or MDM systems. Note 1031096 – Installing Package SAPHOSTAGENT explains how to install the SAPHOSTAGENT package, Note 1622665 – IBM i: SAP Database Performance Collector explains how to setup the SAP Database Performance Collector and has a detailed documentation for it attached as a PDF file. The SAP Database Performance Collector for IBM i is a prerequisite for the next two steps.

Integration of the Backend

In the second step, the existing transactions DB02, ST04 and DBACOCKPIT were reworked to allow using the new SAP Database Performance Collector for IBM i instead of the performance collector jobs that were integrated in the ABAP application server. These changes were implemented in all SAP Basis releases 4.6C and higher. Note 1634283 – IBM i: Changes to Show Data of SAP Database Perf. Collector lists the support packages or correction instructions that are needed to implement these changes. You can activate the changes by setting profile parameter as4/dbmon/central_collector to 1, “on” or “ON”. By activating these changes for all systems in your landscape, you avoid duplicate data collection between the SAP Database Performance Collector for IBM i and the existing ABAP systems.

Performance Warehouse

A third step was completed right now and will be available with SAP Solution Manager 7.1 Support Package Stack 06 plus the correction instructions in Note 1672318 – IBM i: Database Performance Warehouse BI content/extractors or Support Package Stack 07: With these changes, SAP is introducing the extractors and report definitions for the SAP Performance Warehouse for IBM i. The Performance Warehouse offers remote monitoring capabilities, graphical representation of the data, performance history and many reporting and configuration options for reports. Note 1666390 – IBM i: Solution Manager 7.1 Database Performance Warehouse describes how to setup the Performance Warehouse in the SAP Solution Manager and how to register remote SAP systems for reporting. The note also contains an attachment with a detailed description of the reports that are shipped with the Performance Warehouse.

Not the End of the Story

Please stay tuned for future enhancements in the Performance Warehouse and transaction DBACOCKPIT based on the SAP Database Performance Collector for IBM i. There is more to come, and we will inform you through this blog when it is ready.

And not to forget: let us know your opinion, comment to the blog or email to the author – we are always eager to improve.

To report this post you need to login first.

4 Comments

You must be Logged on to comment or reply to a post.

  1. Schlosser Tobias

    This sounds good.

    Will there be possibilities to monitor the database backup through ccms?

    At the moment I don’t know a way to get the status of my backup. (successfull / not successfull).

    You can see the dates when the backup was started in DBACOCKPIT but you can’t see the state.

    E.g. with oracle datbases there is a monitor in RZ20 for this…

    (0) 
    1. Christian Bartels

      Hi Tobias,

      currently the backup information in DBACockpit is based on the “Save date/time” in the object description of each file (table, view, index) in the database library (schema). If the timestamps are the same for all objects, the backup is considered “complete”, otherwise the backup is considered incomplete. The new monitoring will work in the same way.

      We typically see two cases where this concept does not work:

      1. When the whole database is replicated, and the backup is done only on the replicated copy.
      2. When a few objects were saved (e.g. for test purposes) after the backup has completed.

      For both cases, we do not have a good answer how to tell SAP whether the last backup was complete or not. We are thinking about something to allow exit programs sending messages to SAP to inform it about the completeness of a backup, but so far there are no definite plans to implement that.

      Would your situation be covered by one of the two cases above? Or is it something else?

      Kind regards,

      Christian Bartels.

      (0) 
      1. Schlosser Tobias

        Hi Christian,

        thanks for your response.

        I don’t have a problem with this concept. We don’t make backups from a replicated DB or something.

        My problem is how to automatically monitor the SAP backup.

        It would be great if there will be a integration of the backup in the ccms.

        Only a information of successfull or not not succeessfull.

        At the moment you have to monitor the backup manually in the dbacockpit.

        Best regards

        Tobias Schlosser

        (0) 
        1. Christian Bartels

          Hi Tobias,

          unfortunately we have nothing available in CCMS (RZ20) today, and so far nothing was in plan for the new monitoring – it simply affects a different area of the code. As I said before, we know of two shortcomings that we might eventually fix – in that context, we may also consider adding an MTE for RZ20.

          In the meantime, you could define your own MTE based on function module GET_DB4_BACKUP_INFO. The function module is filling an internal table “BACKUP” with the time stamps of the last backups, including a marker “SAVTYPE”, which is ‘C’ for a complete backup or ‘P’ for a partial (=incomplete) backup. You could write a wrapper function around this and set a single value (“good” or “bad”) based on the timestamp and the save type of the last backup and then use that in your own MTE.

          Kind regards,

          Christian Bartels.

          (0) 

Leave a Reply