Raghu:
I believe the fix is to catalog WAS as if it were remote....i.e create a
remote tcp/ip node on the same box and create WASALIAS as database alias
pointing to WAS at that node. In websphere refer to WASALIAS rather than
WAS.
Thanks,
Manas.
----- Original Message -----
From: "Raghu Raman" <[EMAIL PROTECTED]>
To: <[EMAIL PROTECTED]>
Sent: Friday, April 20, 2001 12:43 PM
Subject: DB2EUG: Websphere 3.5 and UDB 6.1 FP 4
> Hi all,
>
> We have an environment on AIX with Websphere 3.5 and UDB 6.1 fixpack 4.
The installation went well and now when we start the Websphere we get an
error message COM.ibm.db2.jdbc Exception
>
> with SQL error SQL1224N.
>
> the MAXUPROC is set to 500 and no users are connected. Am just starting
websphere and getting this error message.
>
> Details of SQL1224N error from DB2 Messages.
> Has anyone seen this before. any help would be appretiated.
>
> BTW, whats that "federated servers" ????
>
> **********************************************************
> 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.
>
> Explanation: The message may be attributed to any of the
> following cases.
>
> o The database manager has not been started on the database
> server
>
> o The database manager was stopped
>
> o The database manager has already allocated the maximum number
> of agents
>
> o The database agent was forced off by the system
> administrator
>
> o The database agent was terminated due to an abnormal
> termination of a key database manager process
>
> o 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.
>
> Additional federated server cases are:
>
> o The maximum number of processes per user (maxuproc on AIX) at
> the operating system level has been exceeded.
>
> o In the client/server environment using the TCP/IP protocol,
> the port number assigned to the TCP/IP service name on the
> client is not the same as the port number on the server.
>
> This situation can be detected by federated server or by the data
> source.
>
> User Response: Reissue the database request. If a connection
> cannot be established, then ensure that the database manager has
> been started successfully. Additionally, ensure that the
> maxagents database manager configuration parameter is
> appropriately configured.
>
> Federated system users, should also:
>
> o Isolate the problem to the data source rejecting the request
> (see the problem determination guide for procedures to
> follow to identify the failing data source) and ensure that
> the communication subsystem is active and that the database
> manager and required communication protocol server processes
> have been started on the database server.
>
> o For AIX operating systems, check the setting of maxuproc and
> change it if needed. maxuproc restricts the number of
> processes that can run under a given federated server. The
> default setting is 40.
>
> You can check the current setting of maxuproc with the
> command:
> **************************************
>
> Regards,
> Ragu
>
>
> Get 250 color business cards for FREE!
> http://businesscards.lycos.com/vp/fastpath/
>
> =====
> To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
> For other info (and scripts), see
http://people.mn.mediaone.net/scottrmcleod
>
>
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
