Status Display and Check Tools

Use

The following sections outline how you get information about the structure and status of SAP NetWeaver BI accelerator indexes and list the checks that you can perform.

●      If you want an overview of the technical status of the BI accelerator and access to actions to restore the status, see Using the SAP NetWeaver BI Accelerator Monitor for the relevant information.

●      For more information about checking that the data records of a BI accelerator index are correct, checking the performance of BI accelerator indexes, or specifically rebuilding one or all BI accelerator indexes, see Checking SAP NetWeaver BI Accelerator Indexes (Transaction RSRV).

●      For an overview of the runtimes of specific subprocesses in SAP NetWeaver BI accelerator index maintenance, see Statistics for Maintenance Processes of SAP NetWeaver BI Accelerator Indexes.

●      You have various options for recording traces. For more information, see Traces for SAP NetWeaver BI Accelerator.

●      If due to a communication problem you do not want the BI accelerator server to be available, you can switch on a fallback solution. To do this, you have to enter at least one e-mail address in table RSDDTREXEMAIL. The BI system saves the time of the error in table RSDDTREXHPAFAIL and sends the relevant information to the e-mail address entered in table RSDDTREXEMAIL.

The recipient of the e-mail should trigger measures to remove the cause of the problem and delete the entry in table RSDDTREXHPAFAIL. When the entry has been deleted, queries automatically read from the BI accelerator server again and not from the database.

For 30 minutes after the BI accelerator server goes down, or until the entry in table RSDDTREXHPAFAIL has been deleted, the system directs all query requests for an InfoCube with a BI accelerator index to the database. The system tries to use aggregates for this InfoCube, if they are available.

After 30 minutes, if the problem is not resolved or if the time stamp entry is not deleted or changed, the system directs query requests to the BI accelerator server again. If the problem still exists, the system writes a new time stamp and redirects queries to the database again for the next 30 minutes.

As soon as the BI accelerator is available, the system automatically sends all queries to the BI accelerator index of the affected InfoCube.