Topic
2 replies Latest Post - ‏2006-04-05T20:10:47Z by SystemAdmin
SystemAdmin
SystemAdmin
17917 Posts
ACCEPTED ANSWER

Pinned topic DB2 client SQLSTATE=58031 error

‏2006-03-25T07:32:48Z |
Hi,

I am tring to connect from my windowns DB2 command line with the server. I have created a catalog using the following command.

db2 => catalog tcpip node ICMNLSDB remote ibmportal server 50000 ostype NT
DB20000I The CATALOG TCPIP NODE command completed successfully.

db2 => list database directory
SQL1031N The database directory cannot be found on the indicated file system.
SQLSTATE=58031

If i try to re-catalog:
db2 => catalog tcpip node ICMNLSDB remote ibmportal server 50000 ostype NT
SQL1018N The node name "ICMNLSDB" specified in the CATALOG NODE command
already exists.

And it doesnt allow to uncatalog:
db2 => uncatalog database ICMNLSDB
SQL1031N The database directory cannot be found on the indicated file system.
SQLSTATE=58031

Any help will be greatly apriciated.
Updated on 2006-04-05T20:10:47Z at 2006-04-05T20:10:47Z by SystemAdmin
  • SystemAdmin
    SystemAdmin
    17917 Posts
    ACCEPTED ANSWER

    Re: DB2 client SQLSTATE=58031 error

    ‏2006-03-25T13:22:44Z  in response to SystemAdmin
    In article
    <1959716941.1143271998476.JavaMail.wassrvr@ltsgwas007.sby.ibm.com>,
    awaise@techlogix.com says...
    > Hi,
    >
    > I am tring to connect from my windowns DB2 command line with the
    > server. I have created a catalog using the following command.
    >
    > db2 => catalog tcpip node ICMNLSDB remote ibmportal server 50000
    > ostype NT DB20000I The CATALOG TCPIP NODE command completed
    > successfully.
    >

    You did create the node entry, which is just a pointer to a remote DB2
    server/instance. After that you need to catalog each remote database on
    this node which you need to access.
    Use the command 'db2 catalog db ICMNLSDB at node ICMNLSDB' to catalog
    the db. You might want to rename (uncatalog/catalog) the node before
    that to make it more clear where you are talking about.
    Also to prevent you from errors caused by the DB2 directory cache it's
    good to issue the command 'db2 terminate' after cataloging again.

    Hope this helps.
  • SystemAdmin
    SystemAdmin
    17917 Posts
    ACCEPTED ANSWER

    Re: DB2 client SQLSTATE=58031 error

    ‏2006-04-05T20:10:47Z  in response to SystemAdmin
    >>db2 => catalog tcpip node ICMNLSDB remote ibmportal server 50000 ostype NT

    >>db2 => list database directory
    >>SQL1031N The database directory cannot be found on the indicated file system.
    >>SQLSTATE=58031
    try: db2 list node directory (you need to catalog the db to get db directory info. to return)

    >>db2 => uncatalog database ICMNLSDB
    >>SQL1031N The database directory cannot be found on the indicated file system.
    you've only cataloged the node and has yet to catalog the db.

    hope this helps. :)