Other BMC CMDB upgrade issues
This topic provides tips and solutions for troubleshooting issues that might occur when you upgrade BMC CMDB.
Important
If an upgrade fails, you might view two versions numbers of BMC CMDB. For example, if you upgrade from 9.1.04 to 19.02, you see 9.1.04 and 19.02 displayed on the CMDB UI. This occurs due to installation rollback. To resolve this issue, you need to repeat the upgrade activity.
To troubleshoot issue with isVirtual attribute
When you upgrade from BMC CMDB version 19.02 or earlier to BMC CMDB 19.08 or later, the attribute isVirtual
is renamed to isVirtual_old
and a new attribute isVirtual
is created under BMC_BaseElement. The isVirtual attribute is under the following classes:
- BMC_System
- BMC_SystemComponent
- BMC_Collection
If the renaming activity and creation of the new isVirtual attribute under BMC_BaseElement fails for certain instances, perform the following steps to fix the issue:
Issue | Resolution |
---|---|
isVirtual_old and isVirtual attributes are not displayed in Class Manager. | After upgrading, the CMDB and AR System metadata displays that the attribute Solution:
If this procedure does not resolve the issue, you must perform the following procedure to rename and create the isVirtual attribute:
|
All required abstract classes are not modified with isVirtual. | After an upgrade, the following abstract classes are modified to reflect the isVirtual attribute name change to isVirtual_old:
Solution: Verify if
If any of the locations does not display
|
To troubleshoot miscellaneous upgrade issues
Check the memory usage of your computer during the upgrade.
Tip
To check the memory usage, use:
- (Microsoft Windows) Windows Task Manager.
- (UNIX)
Top
command.
- If you see a
malloc failed
error, increase the virtual memory on your computer.
- On Microsoft Windows, if you see no CPU activity for an hour or more, check the arerror.log file, which is the BMC Remedy AR System server log, for any errors.
On UNIX, if you see a message that the AR System is terminated, search for a stack trace for errors.
- When you start BMC CMDB for the first time after fresh installation or upgrade, you might get the following error:
Plug-in not
initialized.
To resolve this error, restart the MidTier Tomcat application and then start BMC CMDB.
Comments
Log in or register to comment.