Special issues for patch management – bmc server automation 8.8

The following OS versions are not supported as patching targets if the target system has version 8.8 of the BMC Server Automation agent installed.

Earlier versions of the agent (for example, versions 8.6 and 8.7) are supported on RHEL 5/OEL 5/SUSE 10. Gif database Issues while patching on Red Hat Enterprise Linux

• You maybe unable to install or update the open-vm-tools-deploypkg (from the VMware repository) on a RHEL7 target due to a known issue with this patch. Data recovery lifehacker See https://access.redhat.com/solutions/1449563, for more information about this known issue.

Workaround: You can try excluding the all open-vm-tool patches during the patch analysis job or removing open-vm-tools-deploypkg from the target server.

• While creating a SuSE Linux Catalog, certain rpm files might cause the Catalog Update Job to fail, with the following message: “BLPAT1700 – RPM verification failed on selected repository location. Top 10 data recovery software 2014 Please use SuSE platform repository location and run the catalog.”. Database gale This issue is due to SuSE Enterprise Linux limitations. Database life cycle For this Catalog Update Job, ensure that you specify a repository location on a SuSE Enterprise Linux host computer.

• While you are creating a SuSE Linux Catalog in the Online mode, the Catalog fails with an rpm-python dependency.


Data recovery dallas The error message states rpm-python needed by createrepo-0.4.6-1.el4.rf.noarch.

Workaround : You must check the version of create-repo and python-urlgrabber in the repository server and either ensure that the lower versions are installed or remove the higher versions, if they exist. Data recovery usb In addition, you must ensure that rpm-python exists on the system and the version of rpm-python is compatible with the create-repo version that is shipped with the product.

• For SUSE Linux Enterprise version 10 SP1, hplip17-hpijs-1.7.2-0.15.x86_64.rpm and hplip-hpijs-0.9.7-19.9.x86_64.rpm packages obsolete each other during installation. Database 4th normal form If hplip17-hpijs-1.7.2-0.15.x86_64.rpm is installed, the hplip-hpijs-0.9.7-19.9.x86_64.rpm package is removed from the SUSE target and the other way around. V database in oracle Therefore, when one of these packages is installed, the other package is shown as missing on the next Patch Analysis Job run.

• For SUSE Linux Enterprise version 10, the SP3 Pool catalog contains a lower version of the SPident-0.9-74.27.8.noarch.rpm file. Data recovery tampa If you perform an analysis on a SUSE Linux Enterprise version 10 SP3 target (for example, by using the Online mode catalog), the SPident-0.9-74.27.8.noarch.rpm is reported as missing. R studio data recovery with crack This issue occurs due to a conflict in the repositories provided by Novell and can be ignored. Database uses This issue will be resolved when Novell updates its repository with a newer version of the rpm.

For SUSE Linux Enterprise version 10 SP4, the Patch Analysis Job fails with an error message for the kernel-default rpm: STDERR: cat: rpm-includes.lst: No such file or directoryERROR::YUM dry run failedERROR::sysconfig conflicts with kernel-defaultERROR::cmd: failed! This issue occurs due to a conflict in the repositories provided by Novell and will be resolved when Novell updates its repository with a newer version of the kernel-default rpm.

Workaround : If you encounter this package conflict, you must exclude the conflicting kernel-default rpm by using the include/exclude functionality in the Patching Job.

A SuSE Patch Analysis Job with Install mode and an include list (include all RMP) using Zypper tries to copy the linux_zypper_analyse.sh file from the wrong Application Server location.

Workaround: If you encounter this error, ensure that the registry keys and home value reflect the correct Application Server installation location (for example, C:\Program Files\BMC Software\BladeLogic\appserver\NSH\)

As noted in this KB article from SuSE, SuSE 11 SP2 systems need both SuSE 11 SP1 and SuSE 11 SP2 repositories. Database history Therefore, if you attempt to run patch analysis using a SuSE 11 SP2 catalog on a SuSE 11 SP1 target, dependency issues can occur, as the required RPM packages are not part of the SuSE 11 SP2 repositories.

SuSE’s Subscription Management Tool (SMT) internally maintains metadata in a MySQL database on the repository server. Database b tree By default, SMT creates the MySQL database using the latin1 character set and latin1_swedish_ci collation. Database optimization Because the latin1 character set does not support multibyte characters, you will encounter an error if your SuSE patch description contains a multibyte character.

Workaround: To solve this issue, you must change the character encoding for the DESCRIPTION column in the Patches table of the MySQL database, as follows:

After you create and execute an online AIX patch catalog job with the SUMA download option enabled, you cannot cancel the patch catalog job.The SUMA process continues to run in the repository even after you cancel the job.

AIX remediation job fails to deploy ‘rsct.lapi.rte 3.1.6.0’ on some targets due to a problem in the third-party patch. Data recovery software reviews For more information about this issue, see the following third-party resource:

AIX remediation job fails to deploy ‘rsct.lapi.bsr.bsrpd.odmdel’ (rsct.lapi.bsr 3.1.5.0) on some targets due to a problem in the third-party patch. Cnet data recovery For more information about this issue, see the following third-party resource:

After deploying AIX 6.1 TL9SP1 on a target, the ‘bos.rte.install 6.1.9.1’ fileset enters a broken state if you try to Undo the deploy job. Database systems This ‘bos.rte.install 6.1.9.1’ fileset enters a broken state even if you reject the fileset manually.

• If the broken fileset is an update, reinstall the update using options in the installation program that will apply, commit, and automatically install the required software without saving the replaced files (-acgN flags).

You might encounter dependency errors while performing patch analysis on AIX 6.1 TL09 for security fixes. Data recovery for mac Before you run the analysis job, add AIX 6.1 TL08 to the catalog filter and run the catalog update job to add AIX 6.1 TL08 content to the catalog.

• For Oracle Enterprise Linux, the Patch Analysis Job fails in the Install Mode because of missing rpms in the repository. Data recovery damaged hard drive A single repository will contain updates for all available packages. Database builder The Install Mode is intended to install new packages on the target. Data recovery cnet Hence, BMC recommends the use of Install Mode on selective packages, rather than using the Install Mode on the complete repository.

• You may encounter errors if you try applying more than one patch or hotfix, on a Windows target, at the same time. Database log horizon To resolve this issue, BMC recommends applying only a single patch or a single hotfix at a time. Data recovery raid Note that patches and hotfixes must be applied on Windows targets only if it is required to solve a specific issue. Database design for mere mortals For best practices while applying patches and hotfixes, see MSDN – Best Practices for Applying Service Packs, Hotfixes and Security Patches.

• Before you apply multiple hotfixes, you must check whether the hotfix changes are available in the latest released service pack. Database hardening This is because, Shavlik recommends that it is better to apply the latest service pack instead of applying several hofixes on the server. Data recovery linux distro For best practices while applying patches and hotfixes, see MSDN – Best Practices for Applying Service Packs, Hotfixes and Security Patches.

If patch KB2810009 is found missing during patch analysis, BMC recommends that you first separately deploy patch KB2810009 and then re-run the remediation job for the other missing patches. Data recovery key This KB2810009 missing patch needs to be deployed separately because of dependency issues.

• BMC Server Automation automatically creates the required pre-installation and post-installation environment on a Windows target server for patching Java installation files. Data recovery macbook However, BMC Server Automation does not decide whether to reboot the Windows target server.. Data recovery los angeles The target must be rebooted after each version of Java installation patch is deployed on the target. Database yml You can specify this reboot option while creating a Deploy Job, see Deploy Job – Job Options for more information.

banner