db2icrt Requirements

[Sean Eby]

HELP! I've used db2icrt with DB2 v7.2 beta for Linux to create a new
instance. I've created the new instance, but I can't seem to get the proper
administration priviliedges for the "owner" of the instance. When I use the
Control Center to view/alter instance using a remote Windows Client and
login as the "owner" of the instance, not the original administration use
setup by "db2setup" I get a SQL30081N error, with the following text
description:
---------------
SQL30081N A communication error has been detected. Communication protocol
being used: "TCP/IP". Communication API being used: "SOCKETS". Location
where the error was detected: "". Communication function detecting the
error: "recv". Protocol specific error code(s): "*", "*", "0".
SQLSTATE=08001

DBA0102W Unable to detect nodetype for instance - "db2gats". Reason Code:
"-1".
------------------
And, then when I attempt to start the instance by right-clicking the
instance (yes, the error above doesn't prevent me from attempting something
else) and click Start, it tells me "GATSADM" (the username originally
created in Setup for administration purposes) does not have the authority to
perform the requested command. If anyone has any pointers, it would be
greatly appreciated. OTherwise, a detailed list of the requirements,
including pre-config and post-config for getting an instance up & running
correctly, it would be very helpful!

<twiddling my fingers while being dumbfounded>
Sean Eby

[Karanbir Dhillon]

Hi,
Did u update the svcename parameter and the /etc/services for the port
numbers entries for the new db2 instance.
After updating you need to stop and start the instance.

For eg :-
db2 upate dbm cfg using svcename db2cu01dba0

/etc/services entry :-
db2cu01dba0 50000/tcp # Connection port for DB2 instance u01dba0
db2iu01dba0 50001/tcp # Interrupt port for DB2 instance u01dba0

Karanbir

"Sean Eby" <sp...@hotmail.com> wrote in message
news:9e0d0i$d81$1...@slb2.atl.mindspring.net...

[Dorie Perfetto]

Running 'db2 ? dba0102' from a db2 command line says that
'If the reason code is -1, discovery could not map the catalogued
instance to a valid DB2 instance'. Looks like the cataloging of your
Linux DB2 instance on the remote Windows client may be incorrect.

Can you connect to a database in your Linux instance from a CLP
window on the Windows machine?

[Sean Eby]

Thanks for your comments. However, I figured a few things out. I am using
the book DB2 Universal Database v7.1 by George Baklarz and Bill Wong and the
instructions they gave were not even complete enough to get an instance up
and running off the ground. So instead I re-ran the "db2setup" included with
the DB2 setup files and created a new instance with it. I viewed the log and
was able to cover some of the same steps I made, but I missed a few, like
adding a new FCM entry for the service in addition to adding a new local
service number towards the end of that config file as well as using the "db2
update dbm cfg using svcename xxxxxx" Now I have a new instance running
correctly and it can be properly remotely administered, etc... Thanks for
your help. I appreciate to know I can make use of this newsgroup and get a
timely and knowledgable response.

Sean Eby
"Dorie Perfetto" <do...@ca.ibm.com> wrote in message
news:3B03DC85...@ca.ibm.com...