Preparing for upgrade – bmc server automation 8.5

While upgrading from a previous version to BMC Server Automation 8.5, ensure that the BMC Server Automation user is granted the DBMS_LOCK privilege. Database training This privilege is required for carrying out a handshake between BMC Server Automation database and the BMC BladeLogic Decision Support for Server Automation ETL during database clean up. Data recovery hardware You can use the SYS user to grant the DBMS_LOCK privilege by entering the following command:

In BMC Server Automation version 8.5, the PropertySync feature has been deprecated. Best database software During migration of the database to version 8.5, the Data Migration Manager disables PropertySync and the migration results table displays the migration warning: PropertySync has been changed from true to false. Database gui Please contact BMC Support for further assistance.

Upgrade to version 8.5 deprecates the Provision provisionDevice BLCLI command. Data recovery technician Earlier releases supported the Provision:provisionDevice command. Database engine tuning advisor This command has been deprecated. Data recovery rates BMC recommends that you use the ProvisionJob:createProvisionJob command instead.

After an upgrade from BMC Server Automation version 8.3 or earlier to BMC Server Automation version 8.5, existing Citrix XenServer Provision Jobs fail (QM001706976). Database developer salary Failed jobs display the error message:

To workaround the issue, open the Provision Job in the content editor. Database backup and recovery On the Server Settings panel, browse the Server Properties option to select or create a valid agentless managed object (AMO). Yale b database For more information, see Panel reference for Provision Jobs.


When capturing data from target servers, version 8.5.00 of BMC Server Automation skips IPv6 addresses and masks. Sybase database After an upgrade to version 8.5.00 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.

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Database design Therefore, as part of the upgrade process, you must distribute the latest versions of the custom configuration objects that are not included as part of an RSCD agent. Database 3 normal forms The product installation is automatically upgraded to the appropriate version when you upgrade the agent. Database for dummies However, you must upgrade any custom configuration objects that are not included with the agent by running a Distribute Configuration Objects Job. A database is a collection of Configure this job to target servers to which custom configuration objects need to be distributed. Library database F or a list of those objects that are included as part of an agent installation and those that are not included with the agent and require distribution, see Custom configuration objects.

• Run a Distribute Configuration Objects Job to distribute the latest version of custom configuration objects stored in the Configuration Object Dictionary. Database node The job should target agents that you have upgraded. Data recovery after format The system prevents you from distributing custom configuration objects to agents running an incompatible version. Database 2015 For more information, see Creating or modifying a Distribute Configuration Objects Job.

• If you are not upgrading all of your agents at this time, make copies of all component templates, BLPackages, Snapshot Jobs, and Audit Jobs that reference custom configuration objects that have dependencies on agents running earlier versions. Data recovery nyc You must maintain a version match between component templates, BLPackages, Snapshot Jobs, and Audit Jobs and custom configuration objects and agents. Database weekly The objects that you copy in this step are the objects that you can use to maintain the version match.

To ensure that all configuration-object-based assets within existing content are upgraded, run an Upgrade Model Objects Job that targets any component templates, BLPackages, Snapshot Jobs, or Audit jobs that you want to upgrade. Data recovery utah For more information about the Upgrade Model Objects Job, see Creating or modifying Upgrade Model Objects Jobs.

If you open an existing component template, BLPackage, Snapshot Job, or Audit Job that references a custom configuration object and a later version of that custom configuration object exists, the system displays a message saying it will automatically upgrade the referenced custom configuration object. Data recovery deleted files To maintain a version match with an earlier agent, close the component template, BLPackage, Snapshot Job, or Audit Job without saving.

After executing the Upgrade Model Objects Job, display the results of the job run to see which assets were successfully upgraded and which were not. Database health check If you find that certain assets were not automatically upgraded, you must upgrade them manually. R studio data recovery software Perform the following steps:

• Restart the RSCD agent on which the configuration object is distributed. Data recovery iphone This step is a prerequisite for successful upgrade of the configuration object on the target server.

• Run the Distribute Configuration Objects Job to distribute the configuration objects to the target agent (see Distributing configuration objects).

• To identify the configuration objects that failed, run the Upgrade Model Objects Job on all jobs, templates, and BLPackages that reference the configuration object.

Upgrading to a new release can potentially create mismatches between the version of a custom configuration object, an agent, and any model objects that reference custom configuration objects. Ease use data recovery Therefore, as part of the upgrade process, you must distribute the latest versions of custom configuration objects for the custom configuration objects that are not included as part of an agent. Free database software The installation are automatically upgraded to the appropriate version when you upgrade the agent. Raid 0 data recovery software (See Custom configuration objects for a list of those objects.) You should upgrade any custom configuration objects not included with the agent by running a Distribute Configuration Objects Job. Mail database The job should target servers to which custom configuration objects should be distributed.

• Back up the BMC Server Automation database. Hdata recovery master The data upgrade occurs in place. In database If, for any reason, it should become impossible to complete the upgrade, the only way to restore the database to its pre-upgrade state is from the backups.

Back up the installation directories for all Application Servers and PXE servers. Drupal 7 database query Note that t he user who installed the earlier version of the product might have changed the installation directory from the default location, so ensure that you have the right location. Data recovery usa If your current installation is already an upgrade from a previous version, the paths might be different, due to differences in these locations in earlier versions of BMC Server Automation. Data recovery business If you do not know the installation location for BMC Server Automation components view the contents of the /usr/lib/rsc/HOME file (on Linux or UNIX) or the %WINDIR%\rsc\HOME file (on Windows).

Back up the BMC Server Automation file server storage location. Database visualization For example, copy the entire contents of the storage location to a directory other than the current storage location.

Upgrade one or more Application Servers in your BMC Server Automation system. Data recovery qatar See Upgrading the Application Server on Windows and Upgrading the Application Server on Linux and UNIX. Data recovery no root Related Knowledge Articles

The AMIGO Upgrade Program is designed to assist you with the upgrade of BMC BladeLogic Server Automation environments. Database keywords The process begins when you open an AMIGO Starter Issue and are provided with this document which contains a brief description of the process, a checklist of environmental information to capture and consider when planning your upgrade and links to other documents and manuals which will be helpful in performing your upgrade. Normalization in database The end result is for you to create a written Upgrade Plan which has been reviewed by BMC Support in advance of your upgrade.

banner