|
| Problem | A customer is attempting to start AdminServer that is using DB2 as a local repository and encounters the following exception:
[01.03.27 14:02:45:127 EST] a719b087 AdminServer F Encountered an exception in the main method com.ibm.ejs.sm.exception.OpException: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032
at com.ibm.ejs.sm.beans.SeriousEventDataManager.initializeLogger(SeriousEventDataManager.java:115)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:1028)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:360)
FATAL Encountered an exception in the main method {0} com.ibm.ejs.sm.exception.OpException: COM.ibm.db2.jdbc.DB2Exception: [IBM][CLI Driver] SQL1224N A database agent could not be started to service a request, or was terminated as a result of a database system shutdown or a force command. SQLSTATE=55032
at com.ibm.ejs.sm.beans.SeriousEventDataManager.initializeLogger(SeriousEventDataManager.java:115)
at com.ibm.ejs.sm.server.AdminServer.initializeRuntime(AdminServer.java:1028)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:360)
java.lang.Throwable
at com.ibm.ejs.ras.CBuffLogger.fatalEvent(CBuffLogger.java(Compiled Code))
at com.ibm.ejs.ras.Tr.fireTraceEvent(Tr.java(Compiled Code))
at com.ibm.ejs.ras.Tr.fatal(Tr.java:685)
at com.ibm.ejs.sm.server.AdminServer.main(AdminServer.java:372)
| | | | Solution | Before doing the steps below, verify with your DBA that steps 1 through 5 below are not the cause of the problem:
1. The database manager has not been started on the database server
2. The database manager was stopped
3. The database agent was forced off by the system admin
4. The database manager has already allocated the maximum number of agents
5. The database agent was termninated due to an abnormal termination of a key database manager process
If steps 1 through 5 have been taken care of, it is most likely that this will be the problem:
The application is using multiple contexts with local protocol. In this case the number of connections is limited by the number of shared memory segments to which a single process can be attached. For example, on AIX, the limit is ten shared memory segments per process.
Do the following to resolve the problem:
On the machine with the database that you want to connect to: Configure the database manager to use TCP/IP on AIX:- On the server machine, log in as the DB2 instance owner.
- Set DB2COMM to TPC/IP, for example: db2set DB2COMM=tcpip
- Edit /etc/services file to include DB2 connection and interrupt service ports if they do not already exist, such as,
db2cDB2 50000/tcp # DB2 connection service port db2iDB2 50001/tcp # DB2 interrupt connection # service port - Update the database manager configuration, such as, db2 update dbm cfg using svcename db2cDB2
the argument after svcename must match the name of the DB2 connection port service that you placed in /etc/services. - Start and stop db2
% db2stop % db2start
The following instructions allow you to connect to your local machine as though it was a remote client. On the client machine:- Catalog the node, for example:
db2 catalog tcpip node <NodeName> remote <hostname> server db2cDB2
Note: the server name must match the name of the DB2 connection port service which you specified in /etc/services.
To verify that the catalog command worked properly, you may issue the following command: Catalog the database as follows: a. db2 catalog db <database name> as <database alias> b. db2 uncatalog db <database name> c. db2 catalog db <database alias> as <database name> at node <nodename> (this part of the workaround will prevent the SQL1334N error that can occur when the database name is the same as the database alias) Stop and start DB2. % db2stop % db2start The admin.config dbUrl should not change after performing the above catalog instructions.
NOTE: The WebSphere Application Server documentation lists the steps for setting EXTSHM in the online documentation section 1.2.3.1.1 CONFIGURING UNIX SYSTEMS FOR DB2. This is a new environment setting for Websphere 3.5x.
| | | |
| |
|
Product categories: Software, Application Servers, Distributed Application & Web Servers, WebSphere Application Server, Servlet Engine/Web Container Operating system(s): AIX Software version: 3.5.3 Software edition: Advanced Reference #: 1044438 IBM Group: Software Group Modified date: 2003-06-23
(C) Copyright IBM Corporation 2000, 2004. All Rights Reserved.
|