Skip to Content

  1) Restarting a BIA Service for a particular BLADE

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

Untitled.jpg

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

  Below is the screen that appears.

Untitled1.jpg

   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.

Untitled2.jpg

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

Untitled3.jpg

  Click ‘Yes’ in the following window.

  A message appears as shown below:

Untitled4.jpg

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

Untitled5.jpg

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

  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

Untitled6.jpg

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

·         Restart BIA Server

·         Reorganize BIA Landscape

  Click Execute.

Untitled7.jpg

  Click ‘Start’ on the window that appears.

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

Untitled7.jpg

 

  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.

Untitled7.jpg

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

  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

Untitled7.jpg

   Scenario 2:

   Consider a Warning message on the BIA Monitor screen.

   Click on the Details button.

Untitled7.jpg

Untitled7.jpg

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

To report this post you need to login first.

2 Comments

You must be Logged on to comment or reply to a post.

  1. Dheen AJ

    Hi Naveen,

    Really very useful for knowing about BWA.

    I have one doubt. You have mentioned “

    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.”

    My doubt is if we check from our id , same ll be shown in SM66. Am I correct?

    (0) 

Leave a Reply