Unsupported content

   

This version of the documentation is no longer supported. However, the documentation is available for your convenience. You will not be able to leave comments.

Adding dependent files to the base repository location

The AIX Analysis job run shows dependency log warning messages. These dependency log warning messages are displayed, if the patch files that you are upgrading or installing require dependent patch files or base patch files that do not exist on the target server. Even though some of the warning messages might indicate that you can ignore the warning and continue with the installation and upgrade, BMC recommends resolving as many warning messages as possible, by providing the missing dependent or base patch files in a base repository location. The missing dependent or base patch files can be obtained from the media CD that IBM provides or by requesting the files from IBM or from other sources.

Installing or upgrading patches from a technology level or service pack

To install or upgrade patches from a Technology Level or Service Pack, you must perform the following steps:

  1. Perform Patch Analysis to obtain dependency information. The Analysis job run shows dependency log warning messages, if some of the patch files that you are upgrading or installing contain dependencies (dependent patch files or base patch files) that do not exist on the target server.
  2. To resolve the dependency log warning messages, you can provide the missing dependent or base patch files in a base repository location. The missing dependent or base patch files can be obtained from the media CD that IBM provides or by requesting the files from IBM or from other sources.
  3. After you have obtained the missing patch files, specify the base repository location as described in Specifying the base repository location and URL.
  4. Continue with Patch Analysis and Deployment to deploy the missing patches.

Specifying the base repository location and URL

The Catalog panel includes a Base Repository Location option that contains the following fields:

  • Base Repository Location
    NSH path to the location where base-level payload files are stored. Base-level payload files are not copied to the repository location.
  • Base Repository Network URL
    URL of the location where base-level metadata and payload files are stored. Specifying a value for this field is optional if you have selected the Copy to agent at staging option for the Network URL Type For Payload Deployment field.

Note

If the patches that you require do not contain dependencies, you need not specify values for the Base Repository Location and Base Repository Network URL fields.

The new Base Repository Location option is shown in the following figure:

Viewing the missing patch filesets

The missing base filesets are added to the catalog as fileset ID filter. To view all the added base filesets, expand the Base Filesets smart group, shown in the following figure:

When you perform Patch Analysis, only base filesets that are required as dependencies are added to the catalog, as shown in the following figure:

Migration considerations

After you upgrade the Application Server to BMC Server Automation version 8.6, you must update any AIX catalogs on versions earlier than 8.6.

Recommendations for adding dependent files in the base repository location

BMC recommends the following actions for AIX patching:

  • Irrespective of whether you are installing or upgrading patches, the base filesets are picked up and installed in case they are applicable and needed by one of the filesets in the catalog.
    To prevent installation of unnecessary patches and to avoid potential file dependency conflicts, BMC recommends that you store the base filesets of only the needed packages in the base repository instead of storing all the available base filesets there.
    • In some cases, including the missing base filesets might introduce dependency conflicts, thereby preventing deployment of the patches. For example, csm.client 1.7.1.0 requires csm.client 1.7.0.0. However, including csm.client 1.7.0.0 introduces dependency conflicts and prevents csm.client 1.7.1.0 from being deployed.
  • To avoid dependency conflicts between different technology levels and service packs, BMC recommends that you create separate base repositories for different technology levels and service packs.
  • To avoid potential dependency conflicts, BMC recommends that you clean the repository location — that is, manually delete irrelevant patches from the repository location — before you change the filters of an existing catalog.

Was this page helpful? Yes No Submitting... Thank you

Comments