Anyone who has experience with SAP BusinessObjects its common to upgrade systems and applying patches. From my experience these are the most common issues everyone will face with BOBJ upgrades.
- Servers not starting up after the Upgrade
After the server upgrades to Service Packs and Patches some servers will not start or struck in initializing state. If you are upgrading server to SP and then Patch, always check servers are up and running after every SP and every Patch.
Solution: In most of the cases new SP is expecting new server command line but servers don’t have it. As quick check Create new server (Don’t clone) after the upgrade. New server should start without any issues.
- Tomcat is not Upgraded in Windows
Tomcat versions will be upgraded with major Services packs. When upgrading the systems in some cases Tomcat will not be upgraded.
Solution: In windows make sure you didn’t open the Tomcat Configuration while the installation is running. If the Tomcat configuration window is opened installation will not upgrade the server and the install logs will be written as Other process is being used error.
- Loosing SSO settings and BI Launchpad customizations
This is quite common issue Admins face after every upgrade. This is because of customized .properties files are wiped out by new SP or Patch with the default ones.
Solution: Copy Custom files <INSTALL DIR>\tomcat\webapps\BOE\WEB-INF\config\custom
to: <INSTALL DIR>\SAP BusinessObjects Enterprise XI 4.0\warfiles\webapps\BOE\WEB-INF\config\custom
- BI 4.0/4.1 to 4.2 Upgrade License Key issues
BI 4.2 is using new license model. Prior to upgrading the system from 4.0/4.1 to 4.2 must required to get new 4.2 to license key. After the upgrade navigate to CMC > License key you will see invalid license key error.
Solution: After adding the license key from command line still some cases we get the issue. In that scenarios BusinessObjects_KCDefinitions_dfo.xml is not updated properly. Please follow KB 2308674 to update the 4.2 License key.
- Tomcat Not starting after the Upgrade
In case of memory parameters are not configured properly Tomcat will not start after the upgrade.
Solution: Open Tomcat configuration and make sure Initial Memory Pool always less than the Max memory pool
- Installation struck in CMS Starting State
If installation struck in starting CMS server for more than 20 mins that means there is issue with CMS DB not starting up
Solution: Prior to SP or Patch upgrade, open CCM and double click on SIA to open the settings. In SIA settings navigate to “Configuration” tab and make sure there are not errors thrown. In case of bootstrap or DB issues error will be shown here. If there is an error stop SIA and update CMS DB Settings.