Upgrading to SAP BOBJ 4.2 SP4 Error

[former_member83847]

When upgrading to BOBJ 4.2 SP4, Server Crashed, after investigation we found the profile file hashed 😞

Anyone have Idea!

Profile File:

#export LC_ALL=en_us.UTF8 #export ODBC_HOME=$TERADATA_HOME/odbc_64 #export ODBCINI=/Bo4_installation/sap_bobj/enterprise_xi40/odbc.ini

Log Error:

|89BB5606E2CD47F1B178943495A934440|2017 06 19 13:06:49.668|+0000|Information| |==| | |SIA_uatbiapp|8651006| 1|main | ||||||||||||||||||||com.businessobjects.cad.syslog||Server uatbiapp Request Port Published Addresses: uatbiapp:6410. Listening on port(s): 10.11.91.54:6410. |89BB5606E2CD47F1B178943495A934441|2017 06 19 13:06:50.451|+0000|Information| |==| | |SIA_uatbiapp|8651006| 1|main | ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent is running. |89BB5606E2CD47F1B178943495A934442|2017 06 19 13:06:50.509|+0000|Information| |==| | |SIA_uatbiapp|8651006| 54|uatbiapp.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: CMS uatbiapp.CentralManagementServer is being auto-booted. |89BB5606E2CD47F1B178943495A934443|2017 06 19 13:06:50.954|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer has been started. |89BB5606E2CD47F1B178943495A934444|2017 06 19 13:06:58.461|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer stopped with exit code = 1 (0x1). |89BB5606E2CD47F1B178943495A934445|2017 06 19 13:06:58.484|+0000|Error| |==|E| |SIA_uatbiapp|8651006| 54|uatbiapp.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer stopped unexpectedly. |89BB5606E2CD47F1B178943495A934446|2017 06 19 13:06:58.529|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer has been started. |89BB5606E2CD47F1B178943495A934447|2017 06 19 13:06:59.479|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer stopped with exit code = 1 (0x1). |89BB5606E2CD47F1B178943495A934448|2017 06 19 13:06:59.480|+0000|Error| |==|E| |SIA_uatbiapp|8651006| 54|uatbiapp.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer stopped unexpectedly. |89BB5606E2CD47F1B178943495A934449|2017 06 19 13:06:59.520|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer has been started. |89BB5606E2CD47F1B178943495A93444a|2017 06 19 13:07:00.515|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer stopped with exit code = 1 (0x1). |89BB5606E2CD47F1B178943495A93444b|2017 06 19 13:07:00.523|+0000|Error| |==|E| |SIA_uatbiapp|8651006| 54|uatbiapp.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer stopped unexpectedly. |89BB5606E2CD47F1B178943495A93444c|2017 06 19 13:07:00.571|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer has been started. |89BB5606E2CD47F1B178943495A93444d|2017 06 19 13:07:01.904|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer stopped with exit code = 1 (0x1). |89BB5606E2CD47F1B178943495A93444e|2017 06 19 13:07:01.905|+0000|Error| |==|E| |SIA_uatbiapp|8651006| 54|uatbiapp.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer stopped unexpectedly. |89BB5606E2CD47F1B178943495A93444f|2017 06 19 13:07:01.964|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer has been started. |89BB5606E2CD47F1B178943495A9344410|2017 06 19 13:07:03.007|+0000|Information| |==| | |SIA_uatbiapp|8651006| 55|uatbiapp.CentralManagementServer (Native Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer stopped with exit code = 1 (0x1). |89BB5606E2CD47F1B178943495A9344411|2017 06 19 13:07:03.009|+0000|Error| |==|E| |SIA_uatbiapp|8651006| 54|uatbiapp.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: server uatbiapp.CentralManagementServer is considered failed because it has stopped 5 time(s) within 60 minute(s). Please restart this server. |89BB5606E2CD47F1B178943495A9344412|2017 06 19 13:07:03.009|+0000|Error| |==|E| |SIA_uatbiapp|8651006| 54|uatbiapp.CentralManagementServer (Process Agent)| ||||||||||||||||||||com.businessobjects.cad.syslog||Server Intelligence Agent: CMS uatbiapp.CentralManagementServer has failed and the Server Intelligence Agent has not been able to connect to the cluster. Please verify your CMS port and database settings are correct.

[denis_konovalov]

What version are you upgrading from ?
What OS is this ?
What do you mean profile is hashed ?
What do you mean server crashed - which server, the actual OS/machine or a BOE server/service ?

The log appear to be from SIA or maybe CMS service, it will not have anything installation related. For those u need to look in setupengine.log, which for failed install will be in install user temp directory.

If your OS or actual server machine crashed during upgrade, best way to recover is to

a. investigate why server crashed (BOE processes usually do not and cannot crash OS/server itself)

b. restore machine to pre-upgrade status from backup (don't forget CMS DB restore as well) , and attempt upgrade again using best practices
KBA

https://launchpad.support.sap.com/#/notes/1757132