|
Problem IC72040
|
Status: Closed |
IF CUSTOMER USING COMBINATION OF REMOTE CONNECT (FROM DIFFERENT BOX) AND LOCAL CONNECT (FROM THE SAME BOX) AND THE DB IS CATALOG |
| product: |
DB2 FOR LUW / DB2FORLUW / 910 - DB2 |
| Problem description: |
If customer using combination of remote connect (from different
box) and local connect (from the same box) and the db is
cataloged using the TCP/IP loopback and similar to the
following:
System Database Directory
Number of entries in the directory = 2
Database 1 entry:
Database alias = IANDB1
Database name = IANORG
Node name = LOOPBK
Database release level = c.00
Comment =
Directory entry type = Remote
Catalog database partition number = -1
Alternate server hostname =
Alternate server port number =
Database 2 entry:
Database alias = IANORG
Database name = IANDB1
Local database directory = /home/ikhono
Database release level = c.00
Comment =
Directory entry type = Indirect
Catalog database partition number = 0
Alternate server hostname =
Alternate server port number =
Node Directory
Number of entries in the directory = 1
Node 1 entry:
Node name = LOOPBK
Comment =
Directory entry type = LOCAL
Protocol = TCPIP
Hostname = 127.0.0.1
Service name = xikhono
==> db2 engine could trap.
--------------------------------------- |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* DB2 LUW V9.1 users with DB cataloged using a different alias *
* name than the database name *
****************************************************************
* PROBLEM DESCRIPTION: *
* When a local database is cataloged using a different alias *
* name than the database name, issuing a connect to the *
* database alias could fail: *
* *
* Case #1: local connect could fail with SQL1224 *
* *
* Case #2: remote connect could fail with SQL30081N *
* *
* Case #3: If customer using combination of remote connect *
* (from different box) and local connect (from the same box) *
* and the db is cataloged using the TCP/IP loopback that *
* similar to the catalog below, db2 engine could trap. *
* *
* System Database Directory *
* *
* Number of entries in the directory = 2 *
* *
* Database 1 entry: *
* *
* Database alias = IANDB1 *
* Database name = IANORG *
* Node name = LOOPBK *
* Database release level = c.00 *
* Comment = *
* Directory entry type = Remote *
* Catalog database partition number = -1 *
* Alternate server hostname = *
* Alternate server port number = *
* *
* Database 2 entry: *
* *
* Database alias = IANORG *
* Database name = IANDB1 *
* Local database directory = /home/ikhono *
* Database release level = c.00 *
* Comment = *
* Directory entry type = Indirect *
* Catalog database partition number = 0 *
* Alternate server hostname = *
* Alternate server port number = *
* *
* *
* *
* Node Directory *
* *
* Number of entries in the directory = 1 *
* *
* Node 1 entry: *
* *
* Node name = LOOPBK *
* Comment = *
* Directory entry type = LOCAL *
* Protocol = TCPIP *
* Hostname = 127.0.0.1 *
* Service name = xikhono *
****************************************************************
* RECOMMENDATION: *
* - keep the default catalog entry in which the "Database *
* name" and the "Database alias" is the same. *
* - upgrade to DB2 Version 91 Fix Pack 10 *
**************************************************************** |
| Local Fix: |
N/A |
| available fix packs: |
DB2 Version 9.1 Fix Pack 10 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 11 for Linux, UNIX and Windows
DB2 Version 9.1 Fix Pack 12 for Linux, UNIX and Windows
|
| Solution |
Problem was first fixed in Version 91 Fix Pack 10 |
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 20.10.2010
30.06.2011
30.06.2011 |
| Problem solved at the following versions (IBM BugInfos) |
9.1.FP10
|
| Problem solved according to the fixlist(s) of the following version(s) |
| 9.1.0.10
|
 |
