APAR status |
Closed as user error.
| Error description
WAS 3.5.4.1 on Redhat 7.1, using remote db2 7.2 as repository.
When running the statupserver.sh script, it cannot find the JDBC
driver.
The documentation does not state to enter the path only, so if a
customer enters a path along with the filename, then the install
fails.
Keywords:
Linux Redhat 3.5.4.1 JDBC path startupserver install.script Keywords:Linux Redhat 3.5.4.1 JDBC path startupserver install.script Local fix
Had customer to look at the adminserver.classpath line in her
admin.config. Where the db2java.zip should be specified, it had
the path of db2_home. We corrected that and now it started. Problem summaryProblem conclusionTemporary fixComments
This APAR was opened due to an error when entering the
DB2 home directory during the WAS 3.5 install on Linux.
There is no need to edit the install script or documentation.
The install.sh file says:
"
Where is the base database directory/home so the JDBC driver
can be located?
Default is: /home/db2inst1/
"
...
The instructions are clear. Hence, there seems to be no need
for the script or documentation to be changed. The install.sh file says:"Where is the base database directory/home so the JDBC drivercan be located?Default is: /home/db2inst1/"...The instructions are clear. Hence, there seems to be no needfor the script or documentation to be changed.
APAR information | APAR number | PQ54723 | Reported component name | WSAS ADV LINUX | Reported component ID | 5648C8407 | Reported release | 350 | Status | CLOSED USE | PE | NoPE | HIPER | NoHIPER | Submitted date | 2001-11-13 | Closed date | 2001-11-30 | Last modified date | 2001-11-30 |
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 |
|