BIA Monitoring & Maintenance

[Former Member]

  1) Restarting a BIA Service for a particular BLADE

   Go to T-Code RSDDBIAMON2, below is the GUI for the T-code.

  Go to the following path from main menu: Goto  TREX Administrator Tool.

  Below is the screen that appears.

   The CPU usage and Memory usage are highlighted in the above screen.

   In case, the Memory usage for any BIA blade is 15 Mb or above, we need to go for a Service Restart for that Blade.

   Before restarting the service, we need to ensure that there are no processes running on the BIA server.

   This can be checked in the T-code SM66, below is the screen for the same.

  Select the entire row of the blade in discussion and click Restart Service, this is indicated in the below screen.

  Click ‘Yes’ in the following window.

  A message appears as shown below:

  It can be noticed that the Memory Usage for the blade is now reduced

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  2) Restarting a BIA Server:

  If the CPU Usage is 100 %, in the below TREX Admin screen, we need to go for s BIA server reboot.

  Note: No need to check SM66 before restart as 100 % CPU usage means no users can access reports / no roll-up happening

  Go to the home screen of BIA Monitor and check the check-box for the following:

·         Restart BIA Server

·         Reorganize BIA Landscape

  Click Execute.

  Click ‘Start’ on the window that appears.

  Once the Reboot is done, we get the below highlighted messages

  Also, we need to check the status of all the BIA blades whether available.

  Go to TREX Admin screen and check the below highlighted status, all should be Green.

+++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++++

  3) Error Handling in BIA

  Scenario 1:

  The below issue describes issue with the RFC connection.

  In this case, the solution is to Restart the BIA server

   Scenario 2:

   Consider a Warning message on the BIA Monitor screen.

   Click on the Details button.

  To resolve this, we need to drop the BIA indexes for this particular cube and rebuild the indexes.