Show TOC

Procedure documentationIdentify Extractor Errors Locate this document in the navigation structure

 

If some extractors provide no data, identify the cause and resolve the error.

Prerequisites

  • You have started the Extraktor Framework management, in the SAP Solution Manager Management work center, in the Landscape or Infrastructure view.

  • In the Extractor Framework tab, you have selected Refresh, to display the current extractor information.

  • You have chosen Change .

Procedure

If extractors provide no data, check the following possibilities.

  1. Activate inactive extractors.

    Inactive extractors are indicated by a switched-off light-bulb.

    Caution Caution

    Extractors cause system load.

    Only activate extractors if you actually use the scenario for which the data is collected.

    End of the caution.

    1. Select the inactive extractor.

    2. Select Activate.

  2. Release inconsistent extractors, when you have resolved the cause of the error:

    Inconsistent extractors are indicated by a bolt of lightning.

    Example Example

    Extractors become inconsistent when, for example, their configuration no longer matches the configuration of the system landscape. This can happen, for example, when you install an updated version of a software component.

    End of the example.

    1. Select the inconsistent extractor.

    2. Choose Delete.

    3. Go to the SAP Solution Manager Configuration work center.

    4. Select the system in the Managed ABAP Systems view, and follow the instructions in the guided procedure, to reconfigure the system.

      The Resource Manager restarts the extractor automatically.

  3. Release forbidden extractors, when you have resolved the cause of the error.

    Forbidden extractors are indicated by a red flag.

    Example Example

    Extractors can be forbidden, for example, because:

    • Downtime of the managed system causes an extractor timeout.

    • The extractor causes a dump in the managed system.

    End of the example.

    1. Select the forbidden extractor.

      The last extractions are displayed under Selected Extractor, in the Extractor Log tab.

    2. To display error messages, select an extraction with errors.

    3. Resolve the cause of the error.

    4. Choose Release.

    5. Save your entries.

  4. If no data is provided, although all extractors run without errors, check whether there is data in the managed system.

    Extractors which are active, and collect data, are indicated by a switched-on light-bulb. The last status is OK.

    Example Example

    Data cannot be collected for the following reasons:

    • There is no new data in the managed system.

    • There is new data in the managed system, but it was not all collected, because the extractor would otherwise have impaired the performance of the managed system. In this case, the message shows that the extractor collects time-dependent chunks.

      Data is divided into chunks, for example when a new managed system is connected to the SAP Solution Manager, and large amounts of data must be uploaded into the SAP Netweaver Business Warehouse.

    End of the example.

    1. Select the extractor.

      The last extractions are displayed under Selected Extractor, in the Extractor Log tab.

    2. Select an extraction, to display the number of data records collected.

      The number of data records which an extractor has collected, and the data loader has, for example, uploaded into the SAP Netweaver Business Warehaus, is displayed under Extractor Phases, in the Data Records column.

      If the number of data records in the Extractor row is 0, there is no new data in the managed system.

More Information

For further information about analyzing errors, see Check and Refresh Content.