| Title: | How to translate a node id to a database/table |
|---|
| Document: | db_002 |
|---|
| Keywords: | dbdumpcat,node,sysobjects,list of nodes |
|---|
How to translate a node number to a database/table
If dbfsck reports a inconsistency in your database environment
it provides a node id instead of a name.
This can be translated to a symbolic name by the use of dbdumpcat.
dbdumpcat -t20 provides a list of all nodes in the database
environment along with an associated name.
For example:
/opt/eloquence6/bin/dbdumpcat -h ntserv -s 8800 -t20
contacts the server "ntserv" at port 8800 to ask for its sysobjects.
-------------------------------------
#20 sysobjects (481 entries)
-------------------------------------
|id |type|name |link|
-------------------------------------
|1 |0 |syspool |0 |
|20 |1 |sysobjects |0 |
|21 |0 |sysdevices |0 |
|22 |1 |sysvat |0 |
|30 |1 |sysuser |0 |
|31 |1 |sysdb |0 |
...
|487 |2 |DB3 |0 |
|488 |1 |sysgroup |487 |
|489 |1 |syscolumns |487 |
|490 |1 |sysindex |487 |
|491 |1 |sysmember |487 |
|492 |1 |sysprivilege |487 |
|493 |1 |sysindexseg |487 |
|494 |1 |systablecolumn |487 |
|495 |1 |systableindex |487 |
|496 |1 |systablepath |487 |
|497 |3 |KUNDEN |487 |
|498 |4 |KUNDEN.KUNDNR |487 |
|499 |4 |KUNDEN.ISUCHNAM |487 |
...
-------------------------------------
| Column |
Description |
| id |
This is the node id (this is not necessarily sorted) |
|
| type |
node type
- 1 - system table
- 2 - database catalog
- 3 - table (data set)
- 4 - index
|
| name |
name of database object. In case of an index, it is
composed by the name of the associated table (data set)
and the name of the key.
|
| link |
node id of the database catalog this object belongs to |
|
