Red Hat Linux
UNIX_MemShortage Knowledge Script
Intermittent Perl runtime errors encountered when running the UNIX_MemShortage Knowledge Script.
Job iterations result in a 'Perl Runtime' error.
ExportHugeData and ImportHugeData are CPAN modules which work fine in stand-alone Perl scripts, but may prevent release of filehandles when running from an AppManager agent.
In order to resolve the above described issue install the following hotfix which updates the Unix_MemShortage Knowledge Script. This hotfix eliminates intermittent Perl runtime errors that users experienced when running the Unix_MemShortage Knowledge Script with the UNIX agent v6.5. No changes are made to the UNIX agent itself.
To install this hotfix:
- Download the package containing the hotfix from https://download.netiq.com/knowledgedepot/amu/hotfixes/recommended/am602_unix_65_hotfix51985_setup.exe, to the Windows computer where your AppManager Operator Console is installed.
- Double-click the package to extract the contents, this ReadMe file and the Knowledge Script Unix_MemShortage.qml, to a specified folder. The default location is C:\Program Files\NetIQ.
- From the AppManager Operator Console, check out the Unix_MemShortage Knowledge Script. This is your backup copy in case you need to uninstall this hotfix.
- Check in the updated Unix_MemShortage Knowledge Script provided with this fix.
Upgrading Existing Jobs
To take advantage of the updated Unix_MemShortage.qml Knowledge Script provided in this hotfix, you must upgrade any AppManager jobs that are currently running. The updated Knowledge Script will work with earlier versions of the AppManager agent.
To upgrade jobs that are running when you install the hotfix, use the AMAdmin_UpgradeJobs Knowledge Script, with the Override job build version? option enabled. This option is enabled by default.
Note You must enable the Override job build version? option to upgrade jobs whose build version is the same as or earlier than the build version of the Knowledge Script. The job upgrade process only uses the first three characters of the build version to compare versions. For example, if the build version for an AppManager job was 6.0 while the build version of the newer Knowledge Script was 6.0.712, the job upgrade mechanism would not upgrade the job unless this option was enabled.
To upgrade all of the child jobs for a parent, including child jobs that are running on an AppManager agent that has not been upgraded to the latest version, enable the Force option. This option is not enabled by default.
For more information on how to use the AMAdmin_UpgradeJobs Knowledge Script, see the Operator Console online Help.
This hotfix has been developed for AppManager for Unix version 6.5. However, the hotfix can be applied to AppManager for Unix version 6.x as well.