Show TOC

Converting Standard InfoCubes to SAP HANA-Optimized InfoCubesLocate this document in the navigation structure

Context

If you are using a SAP HANA database and want to benefit from it when loading data into InfoCubes, we recommend converting existing standard InfoCubes.

Note Note that the table layout changes during conversion. If you access data with programs of your own, you have to adjust these manually after conversion. We generally recommend only using released interfaces to access BW data.

After migration to the SAP HANA database, normal standard InfoCubes are in the SAP HANA database's column-based store and have a logical index (CalculationScenario). In the analysis, they behave like BWA-indexed InfoCubes.

If the InfoCubes have data persistency in BWA, the content is deleted during the system migration to SAP HANA, and the InfoCubes are set to inactive. If you want to continue using one of these InfoCubes as a standard InfoCube, you need to activate it again and reload the data from the former primary persistence (DataStore object for example).

If you have integrated InfoCubes for converting into process chains, there is no need for you to modify the process chains. Certain process types have become obsolete, but can remain in the process chain when a SAP HANA database is used. The obsolete processes do not have any funkction when a SAP HANA database is used. The system simply skips them. More information: Obsolete Process Types When Using the SAP HANA Database

Procedure

Starting Conversion

  1. There are two ways of calling the conversion transaction:

    • You are in the InfoCube editing screen. Choose Start of the navigation path Goto Next navigation step Conversion to SAP HANA-Optimized End of the navigation path. The InfoCube you want to edit is displayed.

    • Call transaction RSMIGRHANADB directly.

  2. You can now use input help to select InfoCubes for conversion.
  3. You can decide when the runtime objects of the associated compound InfoProviders (MultiProviders and HybridProviders) are updated:
    • Rebuild MPRO directly: The runtime objects of the associated compound InfoProviders are updated after every conversion. This can take a long time because the associated metamodel is not generated. A compound InfoProvider can also contain multiple InfoCubes, which can result in the metadata model being rebuilt multiple times.
    • Rebuild MPRO at the end of the list: The runtime objects of the associated compound InfoProviders are updated after the list has been processed. If an error occurs, you have to use the same list when you restart. Otherwise the runtime objects of the associated compound InfoProviders will not be up-to-date.

      If conversion is stopped due to an error, you can restart the conversion using the original list. The InfoCubes that have already been converted are skipped. However at the end of the list, all the compound InfoProviders affected by the conversion are modified.

    • Invalidate MPRO (cache only) - manual restart required (only for experts): The InfoCubes are converted; however, you need to manually update the runtime objects of the associated compound InfoProviders. A log is created, which lists the compound InfoProviders that need to be modified. To update the compound InfoProviders, you can use report RSR_MULTIPROV_CHECK. If the compound InfoProviders are not updated, then queries on these objects are terminated.

      If conversion is stopped due to an error, you can restart the conversion using the original list. The InfoCubes that are already converted are skipped.

  4. You can specify whether the log is displayed after conversion.
  5. Choose Execute. The InfoCubes are converted.

Stopping Conversion

  1. If the conversion of a list of InfoCubes takes longer than planned, you can cancel the conversion in a controlled way. In order to cancel all running conversions in a system in a controlled way, you have to set parameter CUBE_STOP_ALL_CONVERSIONS to X in table RSADMIN. You can set this parameter using report SAP_RSADMIN_MAINTAIN. If the parameter is set, the conversion currently being performed and a further conversion are terminated and then list processing is terminated.
    If you activate option Rebuild MPRO at the end of the list, the compound InfoProviders of InfoCubes already converted are modified before conversion is stopped. The affected objects are listed in the log.

    If you activate option Invalidate MPRO (cache only) - manual restart required (only for experts), all compound InfoProviders whose InfoCubes have already been converted are listed in the log.