_considerationsForUpgrading86

  • Upgrade to version 8.6 or later does not grant the DBMS_LOCK privilege to user - Before you start upgrading from a previous version to TrueSight Server Automation 8.6, ensure that the TrueSight Server Automation user is granted the DBMS_LOCK privilege. This privilege is required for carrying out a handshake between TrueSight Server Automation database and the TrueSight Smart Reporting for Server Automation ETL during database clean up. You can use the SYS user to grant the DBMS_LOCK privilege by entering the following command: GRANT EXECUTE on DBMS_LOCK TO <User>
  • Upgrade to version 8.6 or later disables PropertySync - As of TrueSight Server Automation version 8.5, the PropertySync feature has been deprecated. During migration of the database, PropertySync is disabled and the migration results table displays the migration warning: PropertySync has been changed from true to false. Contact BMC Support for further assistance.
  • Upgrade to version 8.5 or later deprecates the Provision provisionDevice BLCLI command. Earlier releases supported the Provision:provisionDevice command. This command has been deprecated. BMC recommends that you use the ProvisionJob:createProvisionJob command instead.
  • Upgrade to version 8.6 or later causes Citrix XenServer Provision Jobs to fail - After an upgrade from TrueSight Server Automation version 8.3 or earlier to TrueSight Server Automation version 8.5 or later, existing Citrix XenServer Provision Jobs fail (QM001706976). Failed jobs display the error message: com.bladelogic.om.infra.mfw .util.BlException: Proxy cannot be null, Error: Proxy cannot be null. To work around the issue, open the Provision Job in the content editor. On the Server Settings panel, browse the Server Properties option to select or create a valid agentless managed object (AMO).
  • Audit performed with snapshots captured using earlier versions of the RSCD agent can fail - When capturing data from target servers, version 8.6.00 of TrueSight Server Automation skips IPv6 addresses and masks. After an upgrade to version 8.6.00 or later from version 8.3 or earlier, an audit performed with snapshots captured using older versions of an RSCD agent can fail if the targets had IPv6 enabled.
  • In a multiple application server (MAS) environment, if the RSCD Agent is not present on the secondary node and the primary node is using PsExec version 2.43, upgrade to version 21.3 or later on the secondary node fails. To fix the issue, perform one of the following tasks:
    • Install RSCD Agent on the secondary node and start the upgrade process again on the secondary node.
    • Use PsExec version 2.2 instead of version 2.43 on the primary node, and start the upgrade process again on the secondary node.


 

Tip: For faster searching, add an asterisk to the end of your partial query. Example: cert*