Legacy ID:KA344330
Step 1
Select the patch to download from the following links. When the browser prompts you choose to Save the file to disk (rather than open it). This will download the patch package to the location you selected.

Linux patch packages for alternate platforms
For Perform version 7.4.10 and earlier, Red Hat Linux and SuSE Linux patch packages for zSeries, pSeries, and IA64 architectures are not available from the FTP site.
Step 1
Start an ftp session to ftp.bmc.com:
> ftp ftp.bmc.com
Connected to ftp.bmc.com.
220 BMC FTP Server Ready
Name (ftp.bmc.com:user):
The FTP login prompt should appear.
Step 2
Log in as "anonymous".
> ftp ftp.bmc.com
Connected to ftp.bmc.com.
220 BMC FTP Server Ready
Name (ftp.bmc.com:paska): anonymous
331 Anonymous login ok, send your complete email address as your password.
Step 3
Use your email address for your password.
Name (ftp.bmc.com:paska): anonymous
331 Anonymous login ok, send your complete email address as your password.
Password: Enter your e-mail address
230-
Software FTP service at ftp.bmc.com.
Information about your login and any transfers you complete are
logged on this host. If you do not like this policy, please disconnect
now. Mirroring of this archive is not allowed. Users looking for
illegal software will be disappointed.
Please contact support@bmc.com with any technical problems you may have
accessing this archive. Please reference your salesperson(s)
and support reference number (if applicable) on all correspondence.
230 Anonymous access granted, restrictions apply.
ftp>
Step 4
Change to the appropriate directory. Patches are in sub-directories based upon the OS vendor (Solaris, HP-UX, Windows, ...) and Product version (6.6.10, 7.1.01, ...).
Architecture | Product Version | Directory |
---|
AIX | 9.5.00 | /pub/perform/gfc/patches/9.5.00/aix |
HP-UX | 9.5.00 | /pub/perform/gfc/patches/9.5.00/hpux |
Solaris | 9.5.00 | /pub/perform/gfc/patches/9.5.00/solaris |
Linux | 9.5.00 | /pub/perform/gfc/patches/9.5.00/linux |
Microsoft Windows | 9.5.00 | /pub/perform/gfd/patches/9.5.00/windows |
|
AIX | 9.0.00 | /pub/perform/gfc/patches/9.0.00/aix |
HP-UX | 9.0.00 | /pub/perform/gfc/patches/9.0.00/hpux |
Solaris | 9.0.00 | /pub/perform/gfc/patches/9.0.00/solaris |
Linux | 9.0.00 | /pub/perform/gfc/patches/9.0.00/linux |
Microsoft Windows | 9.0.00 | /pub/perform/gfd/patches/9.0.00/windows |
|
AIX | 7.5.10 | /pub/perform/gfc/patches/7.5.10/aix |
HP-UX | 7.5.10 | /pub/perform/gfc/patches/7.5.10/hpux |
Solaris | 7.5.10 | /pub/perform/gfc/patches/7.5.10/solaris |
Linux | 7.5.10 | /pub/perform/gfc/patches/7.5.10/linux |
Microsoft Windows | 7.5.10 | /pub/perform/gfd/patches/7.5.10/windows |
|
AIX | 7.5.00 | /pub/perform/gfc/patches/7.5.00/aix |
HP-UX | 7.5.00 | /pub/perform/gfc/patches/7.5.00/hpux |
Solaris | 7.5.00 | /pub/perform/gfc/patches/7.5.00/solaris |
Linux | 7.5.00 | /pub/perform/gfc/patches/7.5.00/linux |
Microsoft Windows | 7.5.00 | /pub/perform/gfd/patches/7.5.00/windows |
|
Solaris | 7.4.10 | /pub/perform/gfc/patches/7.4.10/solaris |
AIX | 7.4.10 | /pub/perform/gfc/patches/7.4.10/aix |
HP-UX | 7.4.10 | /pub/perform/gfc/patches/7.4.10/hp |
Linux [Red Hat/SuSE] | 7.4.10 | /pub/perform/gfc/patches/7.4.10/linux |
Microsoft Windows | 7.4.10 | /pub/perform/gfd/patches/7.4.10 |
|
Solaris | 7.4.00 | /pub/perform/gfc/patches/7.4.00/solaris |
Solaris | 7.3.00 | /pub/perform/gfc/patches/7.3.00/solaris |
Solaris | 7.2.10 | /pub/perform/gfc/patches/7.2.10/solaris |
Solaris | 7.2.00 | /pub/perform/gfc/patches/7.2.00/solaris |
AIX | 7.4.00 | /pub/perform/gfc/patches/7.4.00/aix |
AIX | 7.3.00 | /pub/perform/gfc/patches/7.3.00/aix |
AIX | 7.2.10 | /pub/perform/gfc/patches/7.2.10/aix |
AIX | 7.2.00 | /pub/perform/gfc/patches/7.2.00/aix |
HP-UX | 7.4.00 | /pub/perform/gfc/patches/7.4.00/hp |
HP-UX | 7.3.00 | /pub/perform/gfc/patches/7.3.00/hp |
HP-UX | 7.2.10 | /pub/perform/gfc/patches/7.2.10/hp |
HP-UX | 7.2.00 | /pub/perform/gfc/patches/7.2.00/hp |
Tru64 | 7.2.10 | /pub/perform/gfc/patches/7.2.10/tru64 |
Tru64 | 7.2.00 | /pub/perform/gfc/patches/7.2.00/tru64 |
Linux [Red Hat/SuSE] | 7.4.00 | /pub/perform/gfc/patches/7.4.00/linux |
Linux [Red Hat/SuSE] | 7.3.00 | /pub/perform/gfc/patches/7.3.00/linux |
Linux [Red Hat/SuSe] | 7.2.10 | /pub/perform/gfc/patches/7.2.10/linux |
Microsoft Windows | 7.4.00 | /pub/perform/gfd/patches/7.4.00 |
Microsoft Windows | 7.3.00 | /pub/perform/gfd/patches/7.3.00 |
Microsoft Windows | 7.2.10 | /pub/perform/gfd/patches/7.2.10 |
Microsoft Windows | 7.2.00 | /pub/perform/gfd/patches/7.2.00 |

ftp> cd [patch directory]
250 CWD command successful.
Step 5
Change to binary mode:
ftp> bin
200 Type set to I
This is important when transferring patch packages as they will become corrupt if transferred using an ASCII transfer, the default mode.
Step 6
Select the appropriate patch package for download.
Perform version 7.4.10 and earlier patch packages have the following naming convention:
- pp_[V.V.VV]_[console|agent]_patch_[arch].###.tar.Z
Perform version 7.5.00 patch packages have the following naming convention:
- bpa[console|agent]_[arch]_[V.V.VV]_[console|agent]_patch_###_with_installer.tar
Where:
- [V.V.VV] is the Perform version (for example 7.4.10, 7.5.00, ...)
- [console|agent] is 'console' for a console patch set (which contains patches for files only installed on the managing node) or 'agent' for an agent patch set (which contains patches for the agent component of Perform)
- [arch] is the machine architecture of the package (for example: Solaris, HP-UX, AIX, Tru64, Windows, ...)
- ### is either the patch number or 'latest'. Both the numbered patch and the patch marked 'latest' should be the same package. They are uploaded as separate packages to allow a static download location for when patch packages are referenced in a Technical Bulletin
So, the latest PATROL Perform version 7.4.10 console patch for Solaris will be called:
- pp_7.4.10_console_patch_Solaris.latest.tar.Z
The latest PATROL Perform version 7.5.00 console patch for Solaris will be called:
- bpaconsole_solaris_7.5.00_patch_latest_with_installer.tar
There is always a PATROL Perform agent install on any Perform console machine as the agent install is done automatically as part of the console install. Some of the binaries in the agent install (such as the best1collect.exe binary) are used by the console. Therefore, some console fixes may be available in the agent patch set since the binary being fixed is actually part of the agent install.
ftp> get [patch name]
200 PORT command successful
150 Opening BINARY mode data connection for [patch name]
226 Transfer complete.
Step 7
Run "quit" to exit the ftp utility.
ftp> quit
221 Goodbye.
At this point the patch package should have been downloaded and can now be installed.
Perform version 7.5.00 and later on UNIX
Step 1
Extract the appropriate patch or patches into a temporary directory using the following commands:
> tar -xvf bpa[console|agent]_[arch]_[V.V.VV]_[console|agent]_patch_###_with_installer.tar
where 'bpa[console|agent]_[arch]_[V.V.VV]_[console|agent]_patch_###_with_installer.tar' is the name of the patch package.
Step 2
Once extracted, install the patch according to the directions in the README.bpa[console|agent]_[arch]_[V.V.VV]_[console|agent]_patch_install.txt file available from the extracted patch package.
Perform version 7.5.00 and later on Microsoft Windows
Step 1
On a machine capable of extracting a .zip file double-click the .zip file to unzip and save the patch.
Step 2
Install the patch according to the directions in the README.INSTALL.bpa[console|agent]_[arch]_[V.V.VV]_latest_patch.txt file available in the same directory as the patch package on the BMC FTP site.
Perform version 7.4.10 and earlier on UNIX
Step 1
Uncompress and extract the appropriate patch or patches into a temporary directory using the following commands:
> uncompress pp_[V.V.VV]_[console|agent]_patch_[arch]_latest.tar.Z | tar -xvf -
where 'pp_[V.V.VV]_[console|agent]_patch_[arch]_latest.tar.Z' is the name of the patch package.
Step 2
Once extracted, install the patch according to the directions in the README.INSTALL.bpa[console|agent]_[arch]_[V.V.VV]_latest_patch.txt file availablein the same directory as the patch package on the BMC FTP site.
NOTE - If running an integrated installation of the Perform and Patrol products, the Patrol agent will need to be stopped to insure the bgsagent and the bgscollect processes are stopped and the new binaries are used to start the processes during the installation.
Perform version 7.4.10 and earlier on Microsoft Windows
Step 1
On a machine capable of extracting a .zip file (all Windows XP or 2003 machines, Windows 2000 and earlier with a 3rd party utility such as WinZIP) double-click the .zip file to unzip and save the patch.
Step 2
Install the patch according to the directions in the README.install.win.txt file available from the extracted patch package.
Related Products:
- BMC Performance Assurance for Servers
- BMC Performance Assurance for Virtual Servers
- BMC Performance Analyzer for Servers
- Visualizer
- BMC Performance Analysis for Servers