Using DB2 Control Centre when authorized to the schema

[Database Administrator]

Our DBA has setup one DB on AIX with 6 schemas to be accessed by 6 different development groups.

My DB2 userid gives me full access to the schema in one tablespace, but I am not a DB admin. I can only work with my schema (read, write, drop, create).

I want to use DB2 control centre on my Windows workstation to manage my schema. However, I get constantly errors when trying to connect to the DB. Even cataloging the DB locally failed.

Does DB2 control Centre support this scenario. If not, are there other tools that may do the job?

MihaiG.

[Database Administrator]

mihaig@ca.ibm.com wrote:

> Our DBA has setup one DB on AIX with 6 schemas to be accessed by 6
> different development groups.
>
> My DB2 userid gives me full access to the schema in one tablespace, but I
> am not a DB admin. I can only work with my schema (read, write, drop,
> create).

What do you mean? Schemas don't have anything to do with tablespaces
whatsoever.

> I want to use DB2 control centre on my Windows workstation to manage my
> schema. However, I get constantly errors when trying to connect to the DB.
> Even cataloging the DB locally failed.
>
> Does DB2 control Centre support this scenario. If not, are there other
> tools that may do the job?

It would be helpful if you provide the exact error message and a description
under which circumstances it occurs. Also, what is the DB2 version on AIX
and Windows?

--
Knut Stolze
DB2 z/OS Admin Enablement
IBM Germany

[Database Administrator]

> mihaig@ca.ibm.com wrote:
>
> > Our DBA has setup one DB on AIX with 6 schemas to
> be accessed by 6
> > different development groups.
> >
> > My DB2 userid gives me full access to the schema in
> one tablespace, but I
> > am not a DB admin. I can only work with my schema
> (read, write, drop,
> > create).
>
> What do you mean? Schemas don't have anything to do
> with tablespaces
> whatsoever.
>

This is the setup, each schema in a separate tablespace.
Whether it matters or not is something else.

> > I want to use DB2 control centre on my Windows
> workstation to manage my
> > schema. However, I get constantly errors when
> trying to connect to the DB.
> > Even cataloging the DB locally failed.
> >
> > Does DB2 control Centre support this scenario. If
> not, are there other
> > tools that may do the job?
>
> It would be helpful if you provide the exact error
> message and a description
> under which circumstances it occurs. Also, what is
> the DB2 version on AIX
> and Windows?
>

SQL30081N A communication error has been detected.
Communication protocol being used: "TCP/IP". Communication API
being used: "SOCKETS". Location where the error was detected:
"9.21.153.162". Communication function detecting the error:
"connect". Protocol specific error code(s): "10061", "*", "*".
SQLSTATE=08001


DBA0102W Unable to detect nodetype for instance - "ITERMD03
(ephsd03) ". Reason Code: "-1".



db2 => wasuser3@ephsdev1:[/home/wasuser3]# db2level
DB21085I Instance "ephsd03" uses "32" bits and DB2 code release "SQL08025"
with level identifier "03060106".
Informational tokens are "DB2 v8.1.1.112", "s060429", "U807381", and FixPak
"12".
Product is installed at "/usr/opt/db2_08_01".


> --
> Knut Stolze
> DB2 z/OS Admin Enablement
> IBM Germany

[Database Administrator]

mihaig@ca.ibm.com wrote:

>> mihaig@ca.ibm.com wrote:
>>
>> > Our DBA has setup one DB on AIX with 6 schemas to
>> be accessed by 6
>> > different development groups.
>> >
>> > My DB2 userid gives me full access to the schema in
>> one tablespace, but I
>> > am not a DB admin. I can only work with my schema
>> (read, write, drop,
>> > create).
>>
>> What do you mean? Schemas don't have anything to do
>> with tablespaces
>> whatsoever.
>
> This is the setup, each schema in a separate tablespace.
> Whether it matters or not is something else.

It does matter because we have to understand what you want to do. So if I
got this right, then you want to place all tables that belong to the same
schema into the same tablespace. Is that about right?

>> > I want to use DB2 control centre on my Windows
>> workstation to manage my
>> > schema. However, I get constantly errors when
>> trying to connect to the DB.
>> > Even cataloging the DB locally failed.
>> >
>> > Does DB2 control Centre support this scenario. If
>> not, are there other
>> > tools that may do the job?
>>
>> It would be helpful if you provide the exact error
>> message and a description
>> under which circumstances it occurs. Also, what is
>> the DB2 version on AIX
>> and Windows?
>>
>
> SQL30081N A communication error has been detected.
> Communication protocol being used: "TCP/IP". Communication API
> being used: "SOCKETS". Location where the error was detected:
> "9.21.153.162". Communication function detecting the error:
> "connect". Protocol specific error code(s): "10061", "*", "*".
> SQLSTATE=08001
>
>
> DBA0102W Unable to detect nodetype for instance - "ITERMD03
> (ephsd03) ". Reason Code: "-1".
>
>
>
> db2 => wasuser3@ephsdev1:[/home/wasuser3]# db2level
> DB21085I Instance "ephsd03" uses "32" bits and DB2 code release
> "SQL08025" with level identifier "03060106".
> Informational tokens are "DB2 v8.1.1.112", "s060429", "U807381", and
> FixPak "12".
> Product is installed at "/usr/opt/db2_08_01".

That looks like a connection problem to me. Have you verified that:
- you can ping the DB2 server machine?
- you can establish a connection to the server machine (at the OS level, not
a DB2 connection)?
- you can connect to the database from the DB2 command line?

--
Knut Stolze
DB2 z/OS Admin Enablement
IBM Germany

[Database Administrator]

Knut,
Thank you for your help. My comment are below.


Mihai Georgescu
Pacific Development Centre
IBM Canada
Burnaby, BC

> mihaig@ca.ibm.com wrote:
>
> >> mihaig@ca.ibm.com wrote:
> >>
> >> > Our DBA has setup one DB on AIX with 6 schemas
> to
> >> be accessed by 6
> >> > different development groups.
> >> >
> >> > My DB2 userid gives me full access to the schema
> in
> >> one tablespace, but I
> >> > am not a DB admin. I can only work with my
> schema
> >> (read, write, drop,
> >> > create).
> >>
> >> What do you mean? Schemas don't have anything to
> do
> >> with tablespaces
> >> whatsoever.
> >
> > This is the setup, each schema in a separate
> tablespace.
> > Whether it matters or not is something else.
>
> It does matter because we have to understand what you
> want to do. So if I
> got this right, then you want to place all tables
> that belong to the same
> schema into the same tablespace. Is that about
> right?

Yes, you are right. Our CREATE TABLE statements specify the tablespace.

>
> >> > I want to use DB2 control centre on my Windows
> >> workstation to manage my
> >> > schema. However, I get constantly errors when
> >> trying to connect to the DB.
> >> > Even cataloging the DB locally failed.
> >> >
> >> > Does DB2 control Centre support this scenario.
> If
> >> not, are there other
> >> > tools that may do the job?
> >>
> >> It would be helpful if you provide the exact error
> >> message and a description
> >> under which circumstances it occurs. Also, what
> is
> >> the DB2 version on AIX
> >> and Windows?
> >>
> >
> > SQL30081N A communication error has been detected.
> > Communication protocol being used: "TCP/IP".
> Communication API
> > being used: "SOCKETS". Location where the error
> was detected:
> > "9.21.153.162". Communication function detecting
> the error:
> > "connect". Protocol specific error code(s):
> "10061", "*", "*".
> > SQLSTATE=08001
> >
> >
> > DBA0102W Unable to detect nodetype for instance -
> "ITERMD03
> > (ephsd03) ". Reason Code: "-1".
> >
> >
> >
> > db2 => wasuser3@ephsdev1:[/home/wasuser3]# db2level
> > DB21085I Instance "ephsd03" uses "32" bits and DB2
> code release
> > "SQL08025" with level identifier "03060106".
> > Informational tokens are "DB2 v8.1.1.112",
> "s060429", "U807381", and
> > FixPak "12".
> > Product is installed at "/usr/opt/db2_08_01".
>
> That looks like a connection problem to me. Have you
> verified that:
> - you can ping the DB2 server machine?
> - you can establish a connection to the server
> machine (at the OS level, not
> a DB2 connection)?
> - you can connect to the database from the DB2
> command line?
>

I can telnet into the AIX server and use CLI on AIX for accessing the DB tables.

This is the info for my DB2 on Windows:
H:\>db2level
DB21085I Instance "DB2" uses "32" bits and DB2 code release "SQL08022" with
level identifier "03030106".
Informational tokens are "DB2 v8.1.9.700", "s050422", "WR21350", and FixPak
"9".
Product is installed at "C:\PROGRA~1\IBM\SQLLIB".


We seem to have connection problems also when accessing the DB from an application we wrote. It was fine as long as we had only 1 DB and used the admin userid to access the data. Not sure if both are related. This is what my colleague says:
"I deployed ItermUI and have configured it to access EPHS database with user iterm (userid authorized to schema - not admin). The connection is established but I'm getting exception in retrieving data from table. The exception is ITEM.VALUESET and other tables not found. I know the tables are there and I've checked it. I am able to do CLI SQL to list out the data within the tables."


> --
> Knut Stolze
> DB2 z/OS Admin Enablement
> IBM Germany

[Database Administrator]

mihaig@ca.ibm.com wrote:

>> > SQL30081N A communication error has been detected.
>> > Communication protocol being used: "TCP/IP".
>> Communication API
>> > being used: "SOCKETS". Location where the error
>> was detected:
>> > "9.21.153.162". Communication function detecting
>> the error:
>> > "connect". Protocol specific error code(s):
>> "10061", "*", "*".
>> > SQLSTATE=08001

Maybe this helps?

http://publib.boulder.ibm.com/infoce...c/sql30081.htm

>> > DBA0102W Unable to detect nodetype for instance -
>> "ITERMD03
>> > (ephsd03) ". Reason Code: "-1".
>> >
>> >
>> >
>> > db2 => wasuser3@ephsdev1:[/home/wasuser3]# db2level
>> > DB21085I Instance "ephsd03" uses "32" bits and DB2
>> code release
>> > "SQL08025" with level identifier "03060106".
>> > Informational tokens are "DB2 v8.1.1.112",
>> "s060429", "U807381", and
>> > FixPak "12".
>> > Product is installed at "/usr/opt/db2_08_01".
>>
>> That looks like a connection problem to me. Have you
>> verified that:
>> - you can ping the DB2 server machine?
>> - you can establish a connection to the server
>> machine (at the OS level, not
>> a DB2 connection)?
>> - you can connect to the database from the DB2
>> command line?
>>
>
> I can telnet into the AIX server and use CLI on AIX for accessing the DB
> tables.
>
> This is the info for my DB2 on Windows:
> H:\>db2level
> DB21085I Instance "DB2" uses "32" bits and DB2 code release "SQL08022"
> with level identifier "03030106".
> Informational tokens are "DB2 v8.1.9.700", "s050422", "WR21350", and
> FixPak "9".
> Product is installed at "C:\PROGRA~1\IBM\SQLLIB".
>
> We seem to have connection problems also when accessing the DB from an
> application we wrote. It was fine as long as we had only 1 DB and used the
> admin userid to access the data. Not sure if both are related. This is
> what my colleague says:
> "I deployed ItermUI and have configured it to access EPHS database with
> user iterm (userid authorized to schema - not admin). The connection is
> established but I'm getting exception in retrieving data from table. The
> exception is ITEM.VALUESET and other tables not found. I know the tables
> are there and I've checked it. I am able to do CLI SQL to list out the
> data within the tables."

The description here does not match with the SQL30081 above. So the main
problem still seems to be that we don't know what is really going on in
your environment.

--
Knut Stolze
DB2 z/OS Admin Enablement
IBM Germany

[Database Administrator]

> mihaig@ca.ibm.com wrote:
>
> >> > SQL30081N A communication error has been
> detected.
> >> > Communication protocol being used: "TCP/IP".
> >> Communication API
> >> > being used: "SOCKETS". Location where the error
> >> was detected:
> >> > "9.21.153.162". Communication function
> detecting
> >> the error:
> >> > "connect". Protocol specific error code(s):
> >> "10061", "*", "*".
> >> > SQLSTATE=08001
>
> Maybe this helps?
>
> http://publib.boulder.ibm.com/infocenter/db2luw/v9/top
> ic/com.ibm.db2.udb.msg.doc/doc/sql30081.htm
>
> >> > DBA0102W Unable to detect nodetype for instance
> -
> >> "ITERMD03
> >> > (ephsd03) ". Reason Code: "-1".
> >> >
> >> >
> >> >
> >> > db2 => wasuser3@ephsdev1:[/home/wasuser3]#
> db2level
> >> > DB21085I Instance "ephsd03" uses "32" bits and
> DB2
> >> code release
> >> > "SQL08025" with level identifier "03060106".
> >> > Informational tokens are "DB2 v8.1.1.112",
> >> "s060429", "U807381", and
> >> > FixPak "12".
> >> > Product is installed at "/usr/opt/db2_08_01".
> >>
> >> That looks like a connection problem to me. Have
> you
> >> verified that:
> >> - you can ping the DB2 server machine?
> >> - you can establish a connection to the server
> >> machine (at the OS level, not
> >> a DB2 connection)?
> >> - you can connect to the database from the DB2
> >> command line?
> >>
> >
> > I can telnet into the AIX server and use CLI on AIX
> for accessing the DB
> > tables.
> >
> > This is the info for my DB2 on Windows:
> > H:\>db2level
> > DB21085I Instance "DB2" uses "32" bits and DB2
> code release "SQL08022"
> > with level identifier "03030106".
> > Informational tokens are "DB2 v8.1.9.700",
> "s050422", "WR21350", and
> > FixPak "9".
> > Product is installed at "C:\PROGRA~1\IBM\SQLLIB".
> >
>
> The description here does not match with the SQL30081
> above. So the main
> problem still seems to be that we don't know what is
> really going on in
> your environment.

Sorry for the confusion - the problem is DB2 control centre does not connect to the AIX DB and get error above. I checked /etc/services for right instance and port. I checked db2diag and there is no error msg. The code 10061 does not tell me anything - it is not in errno.h. I tried setting authentication to different values (from DBM cfg, CLIENT, SERVER). No success. I tried re-creating the catalog entry on the XP machine. Very frustrating.

>
> --
> Knut Stolze
> DB2 z/OS Admin Enablement
> IBM Germany

[Database Administrator]

Hello,

The DBA0102W may mean the port you are pointing to is not correct (issue a
db2 get dbm cfg | grep SVCENAME from the server you want to connect to, to
get the right port). Also look for DB2COMM variable.

Best regards,
Joachim Müller

schrieb im Newsbeitrag
news:1938807650.1173746174385.JavaMail.wassrvr@lts gwas010.sby.ibm.com...
>> mihaig@ca.ibm.com wrote:
>>
>> >> > SQL30081N A communication error has been
>> detected.
>> >> > Communication protocol being used: "TCP/IP".
>> >> Communication API
>> >> > being used: "SOCKETS". Location where the error
>> >> was detected:
>> >> > "9.21.153.162". Communication function
>> detecting
>> >> the error:
>> >> > "connect". Protocol specific error code(s):
>> >> "10061", "*", "*".
>> >> > SQLSTATE=08001
>>
>> Maybe this helps?
>>
>> http://publib.boulder.ibm.com/infocenter/db2luw/v9/top
>> ic/com.ibm.db2.udb.msg.doc/doc/sql30081.htm
>>
>> >> > DBA0102W Unable to detect nodetype for instance
>> -
>> >> "ITERMD03
>> >> > (ephsd03) ". Reason Code: "-1".
>> >> >
>> >> >
>> >> >
>> >> > db2 => wasuser3@ephsdev1:[/home/wasuser3]#
>> db2level
>> >> > DB21085I Instance "ephsd03" uses "32" bits and
>> DB2
>> >> code release
>> >> > "SQL08025" with level identifier "03060106".
>> >> > Informational tokens are "DB2 v8.1.1.112",
>> >> "s060429", "U807381", and
>> >> > FixPak "12".
>> >> > Product is installed at "/usr/opt/db2_08_01".
>> >>
>> >> That looks like a connection problem to me. Have
>> you
>> >> verified that:
>> >> - you can ping the DB2 server machine?
>> >> - you can establish a connection to the server
>> >> machine (at the OS level, not
>> >> a DB2 connection)?
>> >> - you can connect to the database from the DB2
>> >> command line?
>> >>
>> >
>> > I can telnet into the AIX server and use CLI on AIX
>> for accessing the DB
>> > tables.
>> >
>> > This is the info for my DB2 on Windows:
>> > H:\>db2level
>> > DB21085I Instance "DB2" uses "32" bits and DB2
>> code release "SQL08022"
>> > with level identifier "03030106".
>> > Informational tokens are "DB2 v8.1.9.700",
>> "s050422", "WR21350", and
>> > FixPak "9".
>> > Product is installed at "C:\PROGRA~1\IBM\SQLLIB".
>> >
>>
>> The description here does not match with the SQL30081
>> above. So the main
>> problem still seems to be that we don't know what is
>> really going on in
>> your environment.
>
> Sorry for the confusion - the problem is DB2 control centre does not
> connect to the AIX DB and get error above. I checked /etc/services for
> right instance and port. I checked db2diag and there is no error msg. The
> code 10061 does not tell me anything - it is not in errno.h. I tried
> setting authentication to different values (from DBM cfg, CLIENT, SERVER).
> No success. I tried re-creating the catalog entry on the XP machine. Very
> frustrating.
>
>>
>> --
>> Knut Stolze
>> DB2 z/OS Admin Enablement
>> IBM Germany
>
>

[Database Administrator]

mihaig@ca.ibm.com wrote:

>> mihaig@ca.ibm.com wrote:
>>
>> >> > SQL30081N A communication error has been
>> detected.
>> >> > Communication protocol being used: "TCP/IP".
>> >> Communication API
>> >> > being used: "SOCKETS". Location where the error
>> >> was detected:
>> >> > "9.21.153.162". Communication function
>> detecting
>> >> the error:
>> >> > "connect". Protocol specific error code(s):
>> >> "10061", "*", "*".
>> >> > SQLSTATE=08001
>>
>> Maybe this helps?
>>
>> http://publib.boulder.ibm.com/infocenter/db2luw/v9/top
>> ic/com.ibm.db2.udb.msg.doc/doc/sql30081.htm
>>
>> >> > DBA0102W Unable to detect nodetype for instance
>> -
>> >> "ITERMD03
>> >> > (ephsd03) ". Reason Code: "-1".
>> >> >
>> >> >
>> >> >
>> >> > db2 => wasuser3@ephsdev1:[/home/wasuser3]#
>> db2level
>> >> > DB21085I Instance "ephsd03" uses "32" bits and
>> DB2
>> >> code release
>> >> > "SQL08025" with level identifier "03060106".
>> >> > Informational tokens are "DB2 v8.1.1.112",
>> >> "s060429", "U807381", and
>> >> > FixPak "12".
>> >> > Product is installed at "/usr/opt/db2_08_01".
>> >>
>> >> That looks like a connection problem to me. Have
>> you
>> >> verified that:
>> >> - you can ping the DB2 server machine?
>> >> - you can establish a connection to the server
>> >> machine (at the OS level, not
>> >> a DB2 connection)?
>> >> - you can connect to the database from the DB2
>> >> command line?
>> >>
>> >
>> > I can telnet into the AIX server and use CLI on AIX
>> for accessing the DB
>> > tables.
>> >
>> > This is the info for my DB2 on Windows:
>> > H:\>db2level
>> > DB21085I Instance "DB2" uses "32" bits and DB2
>> code release "SQL08022"
>> > with level identifier "03030106".
>> > Informational tokens are "DB2 v8.1.9.700",
>> "s050422", "WR21350", and
>> > FixPak "9".
>> > Product is installed at "C:\PROGRA~1\IBM\SQLLIB".
>>
>> The description here does not match with the SQL30081
>> above. So the main
>> problem still seems to be that we don't know what is
>> really going on in
>> your environment.
>
> Sorry for the confusion - the problem is DB2 control centre does not
> connect to the AIX DB and get error above. I checked /etc/services for
> right instance and port. I checked db2diag and there is no error msg. The
> code 10061 does not tell me anything - it is not in errno.h. I tried
> setting authentication to different values (from DBM cfg, CLIENT, SERVER).
> No success. I tried re-creating the catalog entry on the XP machine. Very
> frustrating.

Did you have a look at the link I provided above?

http://publib.boulder.ibm.com/infoce...c/sql30081.htm

--
Knut Stolze
DB2 z/OS Admin Enablement
IBM Germany

[Database Administrator]

Thank Joachim,

I have checked the /etc/services for port number (50004).

wasuser3@ephsdev1:[/home/wasuser3]# db2 get dbm cfg | grep SVCENAME
wasuser3@ephsdev1:[/home/wasuser3]#
wasuser3@ephsdev1:[/home/wasuser3]#

DB2INSTANCE is same as my instance in XP catalog.

When I open DB2 control centre, I expand the node -> instance. Expand instance, displays the message "detecting node type" and returns error:
_________________________
SQL30081N A communication error has been detected.
Communication protocol being used: "TCP/IP". Communication API
being used: "SOCKETS". Location where the error was detected:
"9.21.153.162". Communication function detecting the error:
"connect". Protocol specific error code(s): "10061", "*", "*".
SQLSTATE=08001


DBA0102W Unable to detect nodetype for instance - "ITERMD3
(ephsd03) ". Reason Code: "-1".


Explanation:

An error has been detected by the communication subsystem.

If the connection has already been established, possible causes
include the following:

o A communication subsystem error at the client node or server
node has caused the connection to go down.

o If a SOCKS server is being used, a communications subsystem
error on the SOCKS server has caused the connection to go
down.

o A network error has caused the connection to go down.

o The database agent at the server was forced off by the system
administrator.

o The database agent at the server was terminated due to an
abnormal termination of a key database manager process.



If you are trying to establish a new connection, possible causes
include the following:

o The remote database server has not been cataloged correctly
at the client.

o The database manager configuration file at the server has not
been configured with the proper communication parameters.

o The communication subsystem at the client node or server node
has not been configured correctly, or has not been started
successfully.

o The communication subsystem at the SOCKS server, if one is
being used, has not been configured correctly, or has not
been started successfully.

o The DB2COMM environment variable at the server doesn't
specify the communication protocol used by the client.

o The database manager at the server has not been started, or
has not been started successfully. One or more of the
communication protocols specified by DB2COMM may not have
been successfully started.



Refer to the token values for details. Depending on the
protocol being used and the communication function invoked, some
tokens may not be applicable. The following is the explanation
of the token values:


The actual communication protocol being used. Valid
token values are:

o TCP/IP

o APPC

o NETBIOS

o IPX/SPX



The application programming interface used to invoke
the above communication protocol services. Valid token values
are:

o SOCKETS

o SOCKS

o CPI-C

o DLR or DD

o TLI or Connection/Bindery

o SOAP

o MQI-CLIENT



This is a protocol specific ID which uniquely
identifies the node that detected the error. If the protocol
being used is:

o TCP/IP

The format of the ID is the Internet address in dot
notation.

o APPC

The format of the ID is the fully qualified LU name
(networkID.LUname).

o NETBIOS

The format of the ID is the Workstation name (nname).

o IPX/SPX

The format of the ID is the network address and node address
in hexadecimal notation (network.node).

o MQ

The format of the ID is the MQ queue name.

o SOAP

The format of the ID is the Internet address in dot
notation.



If the location information is not available at the time that
the error occurred, this token is not filled in.

The name of the communication subsystem function that
returned the error code(s).

, , The list of the available error codes and
subcodes that are specific to each protocol being used. Tokens
that are not applicable contain "*".

If the protocol being used is:

o TCP/IP



- If is present and contains the global errno value from
the TCP/IP sockets function call. When using Windows Sockets,
if present, contains the error from the TCP/IP
sockets function call returned by WSAGetLastError().

- If is present and contains the global h_errno value
from the TCP/IP name resolution function call. When using
Windows Sockets, if present, contains the error
from the TCP/IP database function call returned by
WSAGetLastError().

- If is present and contains "0", it means that the
TCP/IP connection has been closed. This could be caused by one
of the following:

- The database agent at the server was forced off by the system
administrator.

- A database agent could not be started at the server because
the maxagents database manager configuration
parameter has been exceeded. Check the administration
notification log to see if an error message has been
logged.

- The connection may have been closed by the remote server at
the TCP/IP level.

- The database agent at the server was terminated due to an
abnormal termination of a key database manager
process.



Note: When using Windows Sockets, if the is
WSAStartup, and is 0, then contains the
Windows Sockets Specification version level requested by
DB2, and contains the Windows Sockets
Specification version level supported by the Windows
Sockets DLL.

o APPC

contains the return code from the CPI-C function. If
present, contains the global errno value from the
CPI-C function call. is not applicable.

o NETBIOS

contains the return code from the call to NetBIOS.
and are not applicable.

o IPX/SPX

contains the global t_errno value from the call to
TLI Services, or the return code from the call to NetWare
Connection or Bindery Services. If the t_errno is
TLOOK, contains the TLI event that has occurred. If
the event is T_DISCONNECT, contains the
disconnect reason code. On AIX, if the t_errno is
TSYSERR, contains the system errno (defined in
sys/errno.h). If contains the error return code from a
call to AIX NetWare Connection or Bindery Services,
contains the error generator.

o MQ

contains the function completion code, 1 for a warning
and 2 for an error. contains the MQ-specific error
code. is not used for MQ.

o SOAP

contains the return code from the SOAP communication
function. The depends upon the value of .
is either:

- The TCP/IP sockect error errorno value in UNIX,
WSAGetLastError for Windows operating systems.

- A Secure Socke Layer (SSL) return code from the Global
Security Kit (GSK).

The value "0" indicates that this is a high-level
SOAP error (not a socket or GSKit error). the value
"1" indicates that this was a socket error. the
value "2" indicates that this was a GSKit
error.






See the Communications Errors appendix of the Message Reference
for more information on specific communication error codes.

User Response:



If the connection has already been established, check if:

1. The database agent at the server has been forced off.

2. The database manager at the server has abnormally
terminated.

3. A communication subsystem or network error has occurred. See
the Message Reference for more information on specific
communication error codes.

If you are trying to establish a new connection, check if:

1. The remote database server is cataloged properly on the
client node.

2. The database manager configuration file at the server is
configured with the proper communication related parameters.
If the database manager configuration parameters have been
updated at the server, ensure that you stop and then re-start
the database manager, for the changes to take effect.

3. The communication subsystems on both client and server nodes
are configured and started up properly.

4. The DB2COMM environment variable at the server specifies the
communication protocol used by the client.

5. The database manager at the server is successfully started.
Start database manager processing at the server should have
returned SQL1063, and not SQL5043. If SQL5043 is returned,
check the administration notification log for more
information.

6. A communication subsystem or network error has occurred.

If the problem persists, consult with your network administrator
and/or communication expert to determine the cause of the problem
using the set of tokens provided.

sqlcode : -30081

sqlstate : 08001
_________________________________________

This should not work since my db2 userid does not match my XP userid or my AIX userid, and I did not get prompted for a userid/password. The instance (ephsd03) is diplayed with "Databases" under it.

Expand databases and see my DB called EPHS. Click on EPHS and get above error. Right click -> "connect..." and get prompted for userid and pwd. DB2 returns same error. Why? THe same connect statement works when issued from AIX?

I checked the meaning of 10061 in WSA error codes:

WSAECONNREFUSED (10061) Connection refused.

Berkeley description: No connection could be made because the target machine actively refused it. This usually results from trying to connect to a service that is inactive on the foreign host.

WinSock description: Same as Berkeley

TCP/IP scenario: In TCP terms (datastream sockets), it means an attempt to connect (by sending a TCP SYN packet) caused the destination host to respond to the host by returning a reset (a TCP RST packet). If an application sends a UDP packet to a host/port that does not have a datagram socket "listening," the network system may respond by sending back an ICMP Port Unreachable packet

User suggestions: Either you went to the wrong host, or the server application you're trying to contact isn't executing. Check the destination address you are using. If you used a hostname, did it resolve to the correct address? If the hostname resolution uses a local hosttable, it's possible you resolved to an old obsolete address. It's also possible that the local services file has an incorrect port number (although it's unlikely).

You can verify that the remote system is rejecting your connection attempt by checking the network statistics locally. Check that your network system (WinSock implementation) has a utility that shows network statistics. You could use this to verify that you're receiving TCP resets or ICMP Port Unreachable packets each time you attempt to connect.

Developer suggestions: If you have a network analyzer available, you can quickly check if the destination port number and host address are what you expect. On the server end, you could use a network system utility similar to BSD's "netstat -a" command to check that your server is running, and listening on the right port number.

This is one of the most frequent errors and one of the best to encounter, since it's one of the least ambiguous. There are only a few possible causes for this error:

you tried to connect to the wrong port. This is a common problem. You need to call htons() to translate a constant value to network byte order before assigning it to the sin_port field in the sockaddr structure.
you tried to connect to the wrong destination host address
the server application isn't running on the destination host
the server application isn't listening on the right port. The server application might need to call htons() to translate the port to network byte order in the sockaddr structure.
WinSock functions: With a datastream socket: connect() and FD_CONNECT WSAAsyncelect() notification message.

Additional functions: With a datagram socket: send() or sendto(), or FD_READ.

_______________________________________________


Regards,
Mihai.



Regards,
Mihai.

> Hello,
>
> The DBA0102W may mean the port you are pointing to is
> not correct (issue a
> db2 get dbm cfg | grep SVCENAME from the server you
> want to connect to, to
> get the right port). Also look for DB2COMM variable.
>
> Best regards,
> Joachim Müller
>
> schrieb im Newsbeitrag
> news:1938807650.1173746174385.JavaMail.wassrvr@lts gwas
> 010.sby.ibm.com...
> >> mihaig@ca.ibm.com wrote:
> >>
> >> >> > SQL30081N A communication error has been
> >> detected.
> >> >> > Communication protocol being used: "TCP/IP".
> >> >> Communication API
> >> >> > being used: "SOCKETS". Location where the
> error
> >> >> was detected:
> >> >> > "9.21.153.162". Communication function
> >> detecting
> >> >> the error:
> >> >> > "connect". Protocol specific error code(s):
> >> >> "10061", "*", "*".
> >> >> > SQLSTATE=08001
> >>
> >> Maybe this helps?
> >>
> >>
> http://publib.boulder.ibm.com/infocenter/db2luw/v9/top
> >> ic/com.ibm.db2.udb.msg.doc/doc/sql30081.htm
> >>
> >> >> > DBA0102W Unable to detect nodetype for
> instance
> >> -
> >> >> "ITERMD03
> >> >> > (ephsd03) ". Reason Code: "-1".
> >> >> >
> >> >> >
> >> >> >
> >> >> > db2 => wasuser3@ephsdev1:[/home/wasuser3]#
> >> db2level
> >> >> > DB21085I Instance "ephsd03" uses "32" bits
> and
> >> DB2
> >> >> code release
> >> >> > "SQL08025" with level identifier "03060106".
> >> >> > Informational tokens are "DB2 v8.1.1.112",
> >> >> "s060429", "U807381", and
> >> >> > FixPak "12".
> >> >> > Product is installed at "/usr/opt/db2_08_01".
> >> >>
> >> >> That looks like a connection problem to me.
> Have
> >> you
> >> >> verified that:
> >> >> - you can ping the DB2 server machine?
> >> >> - you can establish a connection to the server
> >> >> machine (at the OS level, not
> >> >> a DB2 connection)?
> >> >> - you can connect to the database from the DB2
> >> >> command line?
> >> >>
> >> >
> >> > I can telnet into the AIX server and use CLI on
> AIX
> >> for accessing the DB
> >> > tables.
> >> >
> >> > This is the info for my DB2 on Windows:
> >> > H:\>db2level
> >> > DB21085I Instance "DB2" uses "32" bits and DB2
> >> code release "SQL08022"
> >> > with level identifier "03030106".
> >> > Informational tokens are "DB2 v8.1.9.700",
> >> "s050422", "WR21350", and
> >> > FixPak "9".
> >> > Product is installed at
> "C:\PROGRA~1\IBM\SQLLIB".
> >> >
> >>
> >> The description here does not match with the
> SQL30081
> >> above. So the main
> >> problem still seems to be that we don't know what
> is
> >> really going on in
> >> your environment.
> >
> > Sorry for the confusion - the problem is DB2
> control centre does not
> > connect to the AIX DB and get error above. I
> checked /etc/services for
> > right instance and port. I checked db2diag and
> there is no error msg. The
> > code 10061 does not tell me anything - it is not in
> errno.h. I tried
> > setting authentication to different values (from

> DBM cfg, CLIENT, SERVER).
> > No success. I tried re-creating the catalog entry
> on the XP machine. Very
> > frustrating.
> >
> >>
> >> --
> >> Knut Stolze
> >> DB2 z/OS Admin Enablement
> >> IBM Germany
> >
> >
>