wrong node names

**P. Saint-Jacques** · Nov 12 '05, 05:51 AM

Re: wrong node names

I would think we need a bit more info to help.
What node names did you specifyand how.
Which do show when you "list node directory"
Regards, Pierre.

Carmine wrote:
[color=blue]
> When I issue a db2 list db directory command,
> most of the node names are wrong.
> Is this a bug in Db2 v7 or
> is there something that I am missing?
> Thanx...[/color]

--
Pierre Saint-Jacques - Reply to: sesconsjunk at attglobaljunk dot com
Reconstruct address: Remove the two junk and replace at and dot by
their symbols.
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.

**Carmine** · Nov 12 '05, 05:52 AM

Re: wrong node names

for example:

Database 18 entry:

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

this db is on a box called nydbsv02.
where is it getting nydbsv04 from,
i didn't specify it when i cataloged the db...

carmine.natale@ iqfinancial.com (Carmine) wrote in message news:<1eeb8b4.0 311141111.4e1a9 fb4@posting.goo gle.com>...[color=blue]
> When I issue a db2 list db directory command,
> most of the node names are wrong.
> Is this a bug in Db2 v7 or
> is there something that I am missing?
> Thanx...[/color]

**Knut Stolze** · Nov 12 '05, 05:52 AM

Re: wrong node names

Carmine <carmine.natale @iqfinancial.co m> wrote:
[color=blue]
> for example:
>
> Database 18 entry:
>
> Database alias = LOANIQ53
> Database name = LOANIQ53
> Node name = NYDBSV04
> Database release level = 9.00
> Comment =
> Directory entry type = Remote
> Catalog node number = -1
>
> this db is on a box called nydbsv02.
> where is it getting nydbsv04 from,
> i didn't specify it when i cataloged the db...[/color]

What did you specify when you cataloged the node? I.e. how did your exact
CATALOG NODE statement look like?

--
Knut Stolze
Information Integration
IBM Germany / University of Jena

**P. Saint-Jacques** · Nov 12 '05, 05:52 AM

Re: wrong node names

I think you may be confusing db2 system name with instance node name.
The box has a DB2 System Name of: nydbsv02.
This should also translate to the npode name of the DAS on that box. To
verify, do a db2 list admin node directory. Both system name and node
name should match.
As the DAS is an instance, you now get the clue that any other instance
in the same box must have a unique node name.
Database LOANIQ53 is owned by an instance of some name which is
catalogued at a unique node name NYDBSV04.

The name NYDBSV04 was probably assigned to that node name by the Client
Assistant which was used to identify the remote db and therefore the
node (instance) which owned at the box (nydbsv02) where it resided.
If you tell me that nobody used the CA to do the work, then you or some
other dba issued a db2 catalo tcpip node NYDBSV04 remote .... server
..... at one point in time and that's where the name comes from.
Two commands will help:
db2 list admin node directory ----- for DAS
db2 list node directory ----- for instances.
Those must be issued at the server or thru a telnet session if you're
remote.

HTH, Pierre.

Carmine wrote:
[color=blue]
> for example:
>
> Database 18 entry:
>
> Database alias = LOANIQ53
> Database name = LOANIQ53
> Node name = NYDBSV04
> Database release level = 9.00
> Comment =
> Directory entry type = Remote
> Catalog node number = -1
>
> this db is on a box called nydbsv02.
> where is it getting nydbsv04 from,
> i didn't specify it when i cataloged the db...
>
>
>
> carmine.natale@ iqfinancial.com (Carmine) wrote in message news:<1eeb8b4.0 311141111.4e1a9 fb4@posting.goo gle.com>...
>[color=green]
>>When I issue a db2 list db directory command,
>>most of the node names are wrong.
>>Is this a bug in Db2 v7 or
>>is there something that I am missing?
>>Thanx...[/color][/color]

--
Pierre Saint-Jacques - Reply to: sesconsjunk at attglobaljunk dot com
Reconstruct address: Remove the two junk and replace at and dot by
their symbols.
IBM DB2 Cerified Solutions Expert - Administration
SES Consultants Inc.

**Carmine** · Nov 12 '05, 05:53 AM

Re: wrong node names

Database 18 entry:[color=blue][color=green]
> >
> > Database alias = LOANIQ53
> > Database name = LOANIQ53
> > Node name = NYDBSV04
> > Database release level = 9.00
> > Comment =
> > Directory entry type = Remote
> > Catalog node number = -1[/color][/color]

this entry is from a box that just has the db2 client.
the database is cataloged correctly on the server.
so is it correct that the node name on a client
is just a random name assigned by db2?

"P. Saint-Jacques" <p.stjacques@vi deotron.ca> wrote in message news:<3FBA6860. 4000405@videotr on.ca>...[color=blue]
> I think you may be confusing db2 system name with instance node name.
> The box has a DB2 System Name of: nydbsv02.
> This should also translate to the npode name of the DAS on that box. To
> verify, do a db2 list admin node directory. Both system name and node
> name should match.
> As the DAS is an instance, you now get the clue that any other instance
> in the same box must have a unique node name.
> Database LOANIQ53 is owned by an instance of some name which is
> catalogued at a unique node name NYDBSV04.
>
> The name NYDBSV04 was probably assigned to that node name by the Client
> Assistant which was used to identify the remote db and therefore the
> node (instance) which owned at the box (nydbsv02) where it resided.
> If you tell me that nobody used the CA to do the work, then you or some
> other dba issued a db2 catalo tcpip node NYDBSV04 remote .... server
> .... at one point in time and that's where the name comes from.
> Two commands will help:
> db2 list admin node directory ----- for DAS
> db2 list node directory ----- for instances.
> Those must be issued at the server or thru a telnet session if you're
> remote.
>
> HTH, Pierre.
>
> Carmine wrote:
>[color=green]
> > for example:
> >
> > Database 18 entry:
> >
> > Database alias = LOANIQ53
> > Database name = LOANIQ53
> > Node name = NYDBSV04
> > Database release level = 9.00
> > Comment =
> > Directory entry type = Remote
> > Catalog node number = -1
> >
> > this db is on a box called nydbsv02.
> > where is it getting nydbsv04 from,
> > i didn't specify it when i cataloged the db...
> >
> >
> >
> > carmine.natale@ iqfinancial.com (Carmine) wrote in message news:<1eeb8b4.0 311141111.4e1a9 fb4@posting.goo gle.com>...
> >[color=darkred]
> >>When I issue a db2 list db directory command,
> >>most of the node names are wrong.
> >>Is this a bug in Db2 v7 or
> >>is there something that I am missing?
> >>Thanx...[/color][/color][/color]

**Mark A** · Nov 12 '05, 05:53 AM

Re: wrong node names

> Database 18 entry:[color=blue][color=green][color=darkred]
> > >
> > > Database alias = LOANIQ53
> > > Database name = LOANIQ53
> > > Node name = NYDBSV04
> > > Database release level = 9.00
> > > Comment =
> > > Directory entry type = Remote
> > > Catalog node number = -1[/color][/color]
>
> this entry is from a box that just has the db2 client.
> the database is cataloged correctly on the server.
> so is it correct that the node name on a client
> is just a random name assigned by db2?
>[/color]
Apparently so, because if you uncatalog an then catalog again, it will have
a different value.