There are some changes between the earlier versions and the current version that can cause issues or changes with thresholds, the user interface, and reports.
For other upgrade issues, see Known-and-corrected-issues.
The following table provides upgrade issues with thresholds, the user interface, reports, and also provides workarounds for these issues.
| A java.lang.NumberFormatException appears after upgrade
Explanation:
The pw\custom\pronet.conf file does not end with a new line.
User Response:
Open the pw\custom\pronet.conf file, and add a new line at the end. (Press Enter.) |
| The cell process does not run after upgrading with a non-root user
Explanation:
When upgrading the BMC TrueSight Infrastructure Management Server with a non-root user, the cell process does not run after the upgrade, and an error message is generated. This occurs only when a Utilities folder exists in the /var/tmp directory.
User Response:
Before upgrading the server with a non-root user, delete the Utilities folder from the /var/tmp directory. |
| The instance hierarchy is not displayed
Explanation:
For the instance hierarchy to work, you must upgrade all the remote agents to the same version and wait for the first scheduled autosync poll to occur.
User Response:
Upgrade all the remote agents, and wait for the first scheduled autosync poll to occur. After an autosync, the instances are displayed in the hierarchy on the Show Monitors, Group Matrix, Service Matrix, Monitor Matrix, Show Parent, and Show Children links on the graph windows. In Admin Auto, the Add children to the Group works as expected after the first scheduled autosync. |
| Navigation tree is missing
Explanation:
After the upgrade, the navigation tree is not displayed in the Infrastructure Management Console.
User Response:
Clear the browser cache. This might occur once after each upgrade. |
| Reusing customized local actions after upgrading
Explanation:
You can reuse customized local actions after upgrading BMC TrueSight Infrastructure Management Server.
User Response:
You can reuse customized local actions by completing one of the following procedures:
Procedure 1
- Extract the localactions.jar file from the location to which you copied it during the upgrade.
- Open the LocalAction.xml file and copy all customized local actions to installationDirectory\tomcat\webapps\localaction\localactions.jar. When copying customized local actions, replace all the <Role> tags with the <UserGroup> tag. Change the values of roles to groups because from this version of Infrastructure Management onwards, permission to access any local action depends on user groups.
- Run the pw system start command to restart TrueSight Infrastructure Management server.
Procedure 2
1. Backup of the localactions.jar file from the installationDirectory\tomcat\webapps\localaction.
2. Copy the localactions.jar file from the location to which you copied it during the upgrade, and save it in the inatallationDirectory\tomcat\webapps\localaction location.
3. Open installationDirectory\custom\conf\pronet.conf and add the following property: collectorPermissionBasedOn=2
4. Run the following command on the client system to delete the .jar files related to the earlier versions of local actions:
javaws -viewer
|
| Child server status is not accurate Explanation:
Even after upgrading the Child server, the status might display that the Child server version is lower than the Central Monitoring Administration version.
User Response:
Restart the TrueSight Infrastructure Management server of the Child server by running the pw system start command. |
Restoring the earlier version of BMC TrueSight Infrastructure Management Server if the upgrade fails
When you upgrade the BMC TrueSight Infrastructure Management Server to 9.6, the installer automatically backs up the installation and configuration files of the earlier Infrastructure Management installation in the following folder:
- (Microsoft Windows) installationDirectory\BMC Software\ProactiveNet
- (Solaris or Linux) installationDirectory/BMC Software/ProactiveNet
However, the Sybase database files and the cell configuration files are not copied into the folder. BMC recommends that you back up the database files and cell configuration files before upgrading the BMC TrueSight Infrastructure Management Server. For information about backing up the Sybase database and the cell configuration files, see Prerequisites-for-upgrade.
The installer also creates a new folder, ProactiveNet9.6, where all the installation and configuration files of 9.6 installation are copied.
Resuming the upgrade if the preinstallation check fails
Before the upgrade process, Infrastructure Management runs a preinstallation check to check for the required settings and processes. If the check fails, an error message is displayed and the Next button is disabled. You cannot proceed to the upgrade.
Workaround: Restart the Infrastructure Management processes manually and resume the upgrade process.