Google Groups no longer supports new Usenet posts or subscriptions. Historical content remains viewable.
Dismiss

Activating a DB2 database

788 views
Skip to first unread message

Suman

unread,
Mar 26, 2003, 3:27:51 PM3/26/03
to
Hello,
I am new to db2 and am unclear on what all this
node/catalog/instance is. I am just trying to get the database active
so I can connect and work in it. When I first logged on to db2inst2,
this is what I received. Please help. Thanks,

Suman
-------------------------------------------------------------------------
db2 => connect to lzboy34
SQL1097N The node name was not found in the node directory.
SQLSTATE=42720

db2 => list database directory

System Database Directory

Number of entries in the directory = 1

Database 1 entry:

Database alias = LZBOY34
Database name = LZBOY34
Node name = LZBOY34
Database release level = 9.00
Comment =
Directory entry type = Remote
Catalog node number = -1

db2 => activate database lzboy34
SQL1097N The node name was not found in the node directory.
SQLSTATE=42720
db2 =>

larry

unread,
Mar 26, 2003, 3:59:28 PM3/26/03
to
You have the database cataloged as a remote db. So DB2 goes to the node
directory and apparently doesn't find a node name that tells it how to
connect to lzboy34. If you had the db cataloged locally (which would be
appropriate if the db is on a local machine), you wouldn't need the node
directory entry.

Larry

Erik Hendrix

unread,
Mar 26, 2003, 4:08:01 PM3/26/03
to
Hey Suman,

First of all, is the system where you are doing this connect on the same
system as where the database resides or not?
From this it is stating that the database is remote (on another server).

Type in: db2 list node directory

What you get there should be the node name LZBOY34 together with the server
etc.. to connect to. A node here is basicly
the definition off the server and the port number (if TCPIP) for the
instance. A instance is kind off like a umbrella of
different databases combined. On 1 server you can have 1 or multiple
instances, each with 1 or multiple databases underneath them.
Each instance on the same server will listen on a different port for TCPIP.

By specifying the node name you are defining the hostname and the port
number (for TCPIP) to connect to. You then catalog the database
to use that NODE to connect to the server.

Your error message is stating that that node LZBOY34 does not exist. Thus
you will need to catalog that node.
See the (I believe) command reference on how to catalog a node. (catalog
TCPIP node)


"Suman" <sum...@yahoo.com> wrote in message
news:7ea05111.03032...@posting.google.com...

0 new messages