PQ63672,4.0.4: Incorrect FileSystemSpace() Error on
WebSphere Application Server
Downloadable files
Abstract
When customer executes the install.sh script file for
WebSphere® Application Server fix pack prior to V4.0.5 on HP-UX, customer
gets message indicating not enough disk space
Download Description
ERROR DESCRIPTION:
The customer executes the install.sh script file it start the process to
install fixpack 2 for WebSphere Application Server V4.0.1 on HP-UX it
fails when checking the file set space available, in reality the customer
has plenty of space available. The error reported is "prereq failure 50".
The specific error 51.
LOCAL FIX:
Recommended workaround is to edit a copy of the install.sh script to add
the "-SkipVer" parameter to the invocation of the java code to install the
fix pack. This is documented in technote 1041535. Modifying the operating
system's "df" command is not a recommended solution.
DETAILS:
When a Unix system has a long filesystem name, the user may receive the
following error during the installation of a fix, or a fix pack, even
though there is more than enough space available to perform the
installation:
2002/07/17 09:45:03 Error 52 -- The class FileSystemSpace() returned the
following messages:
2002/07/17 09:45:03 Error in FileSystemSpace() v1.8 -- Returned line() has
insufficent tokens.
2002/07/17 09:45:03 Error 51 -- The minimum space required of 110,000,000
bytes is not available on file system.
PROBLEM CONCLUSION:
The Fix Installer code is executing a "df -k" command on the directory
where the fix or fix pack will be installed. If the file system path is
too long then rest of the output would be pushed down to the next line.
The code was only checking the first line of the output and because of the
long file system name, that was the only text on that line, thus the
available disk space fields were not found by the installer. The code was
changed to check the following line in the output if the installer
determines the file system field was too long to fit it all on one line.
TEMPORARY FIX:
This fix will update a class file within the jar file that is causing the
problem. The user must point to the specific jar file using the EFIX_JAR
property.
For example, java -jar -DEFIX_JAR=/opt/was_ae_ptf_2.jar PQ63672_eFix.jar
Prerequisites
None
Installation Instructions
Please review the readme for detailed Installation instructions