|
Problem IT38107
|
Status: Closed |
CONNECT TO A INCORRECTLY CATALOGED DATABASE CAUSED AGENT SPAWNING
|
| product: |
DB2 FOR LUW / DB2FORLUW / B10 - DB2 |
| Problem description: |
When the remote server is the actual server where it is
cataloged and the database that is cataloged does not exists,a
simple "db2 connect to" will fork threads (agents) until
exhaustion(32K), sometimes it leads to DB2 coming down.
The problem is easy to reproduce:
db2 catalog tcpip node mynode remote server
db2 catalog database rsample as rsample at node mynode
Note: rsample is non-existent database.
db2 connect to rsample user using
==> This connect command will cause agent spawning. |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* The problem will be fixed in next releases. *
**************************************************************** |
| Local Fix: |
Avoid cataloging non-existent database as remote. |
| Solution |
|
| Workaround |
****************************************************************
* USERS AFFECTED: *
* All users *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* The problem will be fixed in next releases. *
**************************************************************** |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 24.08.2021
16.03.2022
16.03.2022 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
