What the heck are node names and aliases for?

[Treasure NextDoor]

Hey,

I"m just getting into DB2 and I'm not getting the node name alias
thing.

Are they just arbitrary? Something used for the purposes of easy human
recognition? On the server side, it seems that DB2 will use the name
NODE000 when you create a database. Then you can catalog nodes. On your
client you can only use a node name once.

Is there a good reference on this? I have only found information that
refers to nodes and aliases like they are bread and water.

Chris.

[Mark A]

"Treasure NextDoor" <tr**************@gmail.comwrote in message
news:11*********************@p79g2000cwp.googlegro ups.com...

Hey,

I"m just getting into DB2 and I'm not getting the node name alias
thing.

Are they just arbitrary? Something used for the purposes of easy human
recognition? On the server side, it seems that DB2 will use the name
NODE000 when you create a database. Then you can catalog nodes. On your
client you can only use a node name once.

Is there a good reference on this? I have only found information that
refers to nodes and aliases like they are bread and water.

Chris.

A node is equivalent to a DB2 instance. One DB2 Instance can have multiple
databases. A DB2 server can also have multiple instances created.

The node name used internally on the server (NODE000) is different than a
node that you catalog remotely, although they both refer to an instance. On
a remote catalogued node, it actually refers to a combination of host-name
and instance (which is identified by port or service name).

The port or service name for an instance on the sever is set in the data
base manager (dbm) configuration. (db2 get dbm cfg). DBM is the same as
instance.

See the Command Reference manual for information on cataloging remote tcpip
nodes. Then you catalog the database using the node name you have
catalogued.

[Knut Stolze]

Mark A wrote:

"Treasure NextDoor" <tr**************@gmail.comwrote in message
news:11*********************@p79g2000cwp.googlegro ups.com...

>Hey,

I"m just getting into DB2 and I'm not getting the node name alias
thing.

Are they just arbitrary? Something used for the purposes of easy human
recognition? On the server side, it seems that DB2 will use the name
NODE000 when you create a database. Then you can catalog nodes. On your
client you can only use a node name once.

Is there a good reference on this? I have only found information that
refers to nodes and aliases like they are bread and water.

Chris.

A node is equivalent to a DB2 instance. One DB2 Instance can have multiple
databases. A DB2 server can also have multiple instances created.

The node name used internally on the server (NODE000) is different than a
node that you catalog remotely, although they both refer to an instance.

No, this are two very different things. The NODE000 is actually a database
partition. Since version 8, this usage of the term "node" is changed to
"dbpartition". But that takes some time because the term is used in many,
many places that all have to be found in the docs and then sorted out.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Mark A]

"Knut Stolze" <st****@de.ibm.comwrote in message
news:e9**********@lc03.rz.uni-jena.de...

No, this are two very different things. The NODE000 is actually a
database
partition. Since version 8, this usage of the term "node" is changed to
"dbpartition". But that takes some time because the term is used in many,
many places that all have to be found in the docs and then sorted out.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

I don't see how that can happen because when you catalog a remote tcpip
node, you are referring to a instance with a particular port number (unless
they change the syntax for cataloging a tcpip node). When not using DPF
(partitioning) it is easier to just think of the node as the instance.

[Knut Stolze]

Mark A wrote:

"Knut Stolze" <st****@de.ibm.comwrote in message
news:e9**********@lc03.rz.uni-jena.de...

>No, this are two very different things. The NODE000 is actually a
database
partition. Since version 8, this usage of the term "node" is changed to
"dbpartition". But that takes some time because the term is used in
many, many places that all have to be found in the docs and then sorted
out.

I don't see how that can happen because when you catalog a remote tcpip
node, you are referring to a instance with a particular port number
(unless they change the syntax for cataloging a tcpip node). When not
using DPF (partitioning) it is easier to just think of the node as the
instance.

I believe that the NODE0000 refers to the directory that you will see once
you created a database. That is a partition and not an instance. But
maybe I didn't understand the OP correctly.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

[Mark A]

"Knut Stolze" <st****@de.ibm.comwrote in message
news:e9**********@lc03.rz.uni-jena.de...

>
I believe that the NODE0000 refers to the directory that you will see once
you created a database. That is a partition and not an instance. But
maybe I didn't understand the OP correctly.

--
Knut Stolze
DB2 Information Integration Development
IBM Germany

I believe that directories SQL00001, SQL00002, etc are created for the
databases.

The OP is a DB2 newbie, and just trying to understand the difference between
a instance, node, and a database and how to catalog them. It is a bit
confusing for the beginner working with remote systems. The main point to
remember is that a remote tcpip node is a combination of server (host-name)
and instance (port number on that server).

[Knut Stolze]

Mark A wrote:

I believe that directories SQL00001, SQL00002, etc are created for the
databases.

That is correct. And the DB-specific directories reside on logical of
physical partitions, which are the NODE0000, NODE0001 etc. directories.

The OP is a DB2 newbie, and just trying to understand the difference
between a instance, node, and a database and how to catalog them. It is a
bit confusing for the beginner working with remote systems. The main point
to remember is that a remote tcpip node is a combination of server
(host-name) and instance (port number on that server).

I agree. The question is what his/her NODE0001 refers to...

--
Knut Stolze
DB2 Information Integration Development
IBM Germany