I encountered the exact same problem and here was the fix:
----------------------------------------------------------------------------
Solution: Local connections can be routed to communicate through TCP/IP as
opposed to
shared memory segments. Doing this requires the following modifications:
1. A TCP/IP port must be setup in /etc/services. (An existing port for
remote DB2 clients
may be used) The DB2 registry variable DB2COMM must include tcpip (db2set
DB2COMM=tcpip)
The SVCENAME database manager configuration parameter must be updated to
the service name
as defined in /etc/services.
2. The loopback node and the database must be catalogued as if they were
remote.
db2 catalog tcpip node <node-name> REMOTE <hostname> SERVER <service-name>
db2 catalog database <name> as <alias> at NODE <node-name>
3. The application must be modified to connect to the new alias, and must
use the <user>
and <using> parameters on the connect in order to perform authentication.
----------------------------------------------------------------------------
I believe there is also a general fix with fixpak 7 (check the fixpak
readme file).
Regards,
Rob Arthur
IBM Certified Solutions Expert - DB2 UDB V6.1 Database Administration
Sr. I/T Specialist
IBM Global Services
Global Smart Card Solutions
=====
To unsubscribe, send 'unsubscribe' to [EMAIL PROTECTED]
For other info (and scripts), see http://people.mn.mediaone.net/scottrmcleod
