BIA High Avaliability
Weu2019ve noticed the fact that even if one blade isnu2019t available all the process interacting with BIA will fail, nevertheless backups seem to be configured correctly (according to information from basis team). This strange behavior appears either when initial filling of indexes or rolling up info cubes with requests.
Logs from SLG1 describe some index failures:
u201CIndex is corrupt, rollback or commit required;inde
Error Creation of the BIA index for InfoCube 'IMP_TCPPA' terminated while fillingu201D
Logs from TREX show us networks problems:
u201C 2008-08-19 11:27:43.784 e TrexNet EndPoint.cpp(00251) : ERROR: failed to open channel 172.31.24.149:30403! reason: connection refused
 2008-08-19 11:27:43.784 e NameServer TREXNameServer.cpp(00731) : pingTREXService(indexserver@sb2:30403) net exceptionu201D
Is it network or backup bug?