PQ67579: WEBSPHERE INSTALL PROCESS DOESN'T UPDATE ADMIN.CONFIG PROPERLY WHEN USING OCI DRIVER. | |||||||||||||||||||||||||||||||||||||
![]() |
|||||||||||||||||||||||||||||||||||||
APAR status Closed as unreproducible in next release. Error description WebSphere installation process does not handle installation with Oracle OCI JDBC Driver properly because of incorrect update com.ibm.ejs.sm.adminServer.dbdatabaseName parameter in admin.config file. . The data source URL for Oracle OCI JDBC driver has the format: jdbc:oracle:oci8:@<connect_alias> where <connect_alias> is an entry from tnsnames.ora . When you install & configure WebSphere with Oracle OCI driver in the database options, you get a message saying you must specify the database name. Database name is not needed because it is already included in com.ibm.ejs.sm.adminServer.dbURL. But you have to define also database name to proceed in the installation. This is a defect. This is a problem in both releases pof WebSphere 3.5 & WebSphere 4.0.The result is that WebSphere AdminServer does not start after installation. All above examples of admin.config are from WebSphere 4.0.X AE.Local fix Manualy remove the database name (leave dbdatabaseName blank) from admin.config and WebSphere starts up fine.Problem summary **************************************************************** * USERS AFFECTED: Users on WebSphere Application Server 3.5 * * and 4.0 AE using the Oracle OCI driver. * **************************************************************** * PROBLEM DESCRIPTION: WebSphere install process doesn't * * update admin.config properly when using * * OCI driver. * **************************************************************** * RECOMMENDATION: * **************************************************************** WebSphere installation process does not handle installation with Oracle OCI JDBC Driver properly because of incorrect update com.ibm.ejs.sm.adminServer.dbdatabaseName parameter in admin.config. The data source URL for Oracle OCI JDBC driver has the format: jdbc:oracle:oci8:@<connect_alias> where <connect_alias> is an entry from tnsnames.ora When you install & configure WebSphere with Oracle OCI driver in the database options, you get a message saying you must specify the database name. Database name is not needed because it is already included in com.ibm.ejs.sm.adminServer.dbURL. But you have to define also database name to proceed in the installation. All above examples of admin.config are from WebSphere 4.0.X AE. This problem will not arise in WebSphere 5.0 because it does not use a database as it's repository. Solution: Manualy remove the database name (leave dbdatabaseName blank) from admin.config and WebSphere starts up fine.Problem conclusion Temporary fix Comments
APAR is sysrouted FROM one or more of the following: APAR is sysrouted TO one or more of the following: Modules/Macros
|
Document Information |
Product categories: Software > Application Servers >
Distributed Application & Web Servers > WebSphere Application
Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ67579
IBM Group: Software Group
Modified date: Nov 21, 2002
(C) Copyright IBM Corporation 2000, 2006. All Rights Reserved.