Troubleshooting when Displaying DSRs

You want to display Distributed Statistics Records (DSRs) of any DSR components with release SAP NetWeaver 7.1 in the global workload monitor, and have performed the required configuration steps in accordance with the corresponding procedure:

Scenario Configuration Description

Displaying DSRs of components of the local system

Configuring the Display of DSRs of the Local System

Displaying DSRs from components (AS Java/TREX) of remote systems that do not have an ABAP instance

Configuring the Display of DSRs of Remote Systems

Displaying DSRs from components of remote systems that have their own ABAP instance

Configuring the Display of Statistics Data from Remote Systems

If the desired DSRs are not displayed in the global workload monitor, proceed as follows to correct the error:

  1. Check that the instance is actually writing DSRs. It writes the DSRs to the directory $DIR_LOGGING/dsr.
  2. Check whether the associated sapstartsrv instance agent is running. More information: Restarting SAP NetWeaver Management Agents.
  3. Check whether the transfer of the DSRs of the relevant instance has been activated in the responsible sapstartsrv instance agent. This is the case, if the following two profile parameters are set in the relevant instance profile:
    • dsr/loaddsrlib = YES
    • dsr/dsrroot = $DIR_LOGGING/dsr
  4. After setting the above profile parameters, you need to restart the responsible instance agent for the changes to take effect. If you are not sure whether you restarted the agent, perform the restart now:
    1. Under Microsoft Windows, you restart the agents by restarting the corresponding service SAP<SysID>_<instance number>.
    2. Under UNIX, you use the following command:

      sapcontrol -nr <instance number> -function RestartService

  5. Required settings are automatically written by various jobs during the transfer of the DSR aggregates. If you have only set the instance parameters in the context of this troubleshooting, wait for two hours after restarting the instance agent.
  6. Check in the ABAP system in which the DSR aggregates are stored whether the corresponding logical Web Service ports have been created for the instance agent sapstartsrv.

    The Web Services have the naming convention N3STATWS.<host>.<instance number> (host and instance number are those of the DSR instance); you can check the existence of the Web Services as follows:

    • If it exists, the Web Service must be entered in the System Component Repository (SCR), under CCMS Domain → Logical Port. You can display the SCR by calling transaction RZ21 and choosing Technical Infrastructure → System Repository → Display.
    • You can also use transaction SOAMANAGER.

    If the logical Web Service port does not exist, restart the sapstartsrv instance agent as described above.

  7. Check in the ABAP system in which the DSR aggregates are stored whether there is also a DSR component for the corresponding logical Web Service port. You can also check this in the SCR.

    The DSR components for the logical ports are entered by the report RSN3CRAWLR. Start the report manually, and - if there is no DSR component entered - check the application log. To do this, start transaction SLG1, and filter by the object BCSWNC and the subobject DSR.

  8. If you have not been able to discover any errors so far, use the test program RSN3STAD.
  9. If you are still unable to discover where the error lies, activate tracing for the DSR library. You do this through the general tracing of sapstartsrv by setting the following two profile parameters in the corresponding instance profile:
    • service/trace = 2
    • dsr/trace = <path for DSR trace file>

    To activate tracing, restart the sapstartsrv instance agent as described above after setting the profile parameters.