APAR status |
Closed as documentation error.
| Error description
WASINSK
Refer to PMR 26643,1LD,000.
.
Environment:
HPUX 11.0
WebSphere Application Server 3.5 Fixpack 2
DB2 7.1 fixpack 1
.
Description:Environment:HPUX 11.0WebSphere Application Server 3.5 Fixpack 2DB2 7.1 fixpack 1.
The WAS 3.5.2 fixpack backs up and deletes the old
libioser12.sl and doesn't install the new one. This occurs in
other platforms too, but it is normally benign. On HPUX with DB2
installed locally, the lack of this file causes the following
exception to occur when WAS is started:Description:The WAS 3.5.2 fixpack backs up and deletes the oldlibioser12.sl and doesn't install the new one. This occurs inother platforms too, but it is normally benign. On HPUX with DB2installed locally, the lack of this file causes the following
.
/usr/lib/dld.sl: Unresolved symbol: sqloxlatchinit (code) from
/opt/IBMdb2/V7.1/lib/libdb2jdbc.sl
.
WEBSJAVA.INSTALL developers wanted to know if the customer
installed WAS using the native install or the java install. The
customer originally installed WAS 3.5 using the java install
(not the native install). exception to occur when WAS is started:./usr/lib/dld.sl: Unresolved symbol: sqloxlatchinit (code) from/opt/IBMdb2/V7.1/lib/libdb2jdbc.sl.WEBSJAVA.INSTALL developers wanted to know if the customerinstalled WAS using the native install or the java install. Thecustomer originally installed WAS 3.5 using the java install(not the native install). Local fix
Copy old libioser12.sl into WebSphere/AppServer/bin directory. Problem summary
User must have jdk update installed on the machine with
3.5.2; otherwise the class file libioser12.sl will not be found
happen in 3.5.2 and that the jdk upgrade contains
the file that was deleted by the was ptf 2 installer.
Once the required jdk upgrade is made there is not a
problem.
Keeping defect open for documentation for future 3.5 ptf
rleases so that this point is made more clearly. Problem conclusion
Followup note:
Found out customer had unpacked the install on a second
machine then copied the websphere files to the actual install.
Documentation should include notes about the fact you need
to unpack the ptf install on the machine to be upgraded. Followup note:Found out customer had unpacked the install on a secondmachine then copied the websphere files to the actual install.Documentation should include notes about the fact you needto unpack the ptf install on the machine to be upgraded. Temporary fixComments
APAR information | APAR number | PQ45548 | Reported component name | WEBSPHR HP-UX V | Reported component ID | 5648C8403 | Reported release | 350 | Status | CLOSED DOC | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-01-26 | Closed date | 2001-01-26 | Last modified date | 2001-02-12 |
APAR is sysrouted FROM one or more of the following:
APAR is sysrouted TO one or more of the following:APAR is sysrouted FROM one or more of the following:
Modules/Macros APAR is sysrouted TO one or more of the following:Modules/Macros
Applicable component levels |
|