Results 1 to 3 of 3
  1. #1
    Join Date
    Jan 2009
    Posts
    1

    Unanswered: SQL1038C An I/O error occurred while accessing the node directory. SQLSTATE=58031

    Hi every one

    Explanation:

    The node directory could not be accessed because of an I/O
    error.

    The command cannot be processed.

    User Response:

    Resubmit the command. If the error continues, remove the node
    directory (sqlnodir under the sqllib directory) and recatalog the
    node names on the network.

    sqlcode : -1038

    sqlstate : 58031

    If you find this type of DB2 Error message, before dig into this first
    "check your system have Administrator rights".
    Other wise you can not resolve this error.

  2. #2
    Join Date
    Oct 2008
    Posts
    11

    Here you go..!

    C:\Documents and Settings\Administrator>db2 ? SQL1038C


    SQL1038C An I/O error occurred while accessing the node directory.

    Explanation:

    The node directory could not be accessed because of an I/O error.

    The command cannot be processed.

    User response:

    Resubmit the command. If the error continues, remove the node directory
    (sqlnodir under the sqllib directory) and recatalog the node names on
    the network.


    sqlcode: -1038

    sqlstate: 58031

    Regards,
    Eldho Mathew

  3. #3
    Join Date
    Jan 2015
    Posts
    1
    Quote Originally Posted by vvnagasudheer View Post
    Hi every one

    Explanation:

    The node directory could not be accessed because of an I/O
    error.

    The command cannot be processed.

    User Response:

    Resubmit the command. If the error continues, remove the node
    directory (sqlnodir under the sqllib directory) and recatalog the
    node names on the network.

    sqlcode : -1038

    sqlstate : 58031

    If you find this type of DB2 Error message, before dig into this first
    "check your system have Administrator rights".
    Other wise you can not resolve this error.
    On reason is rights to read/write the DB2 client configuration.
    Check the user using which you have executed the command to catalog the database have right to read/write the DB2 client configuration.
    On windows , open the console(cmd) as Aministrator, then open DB2 CLI (executing db2cmd on console), the DB2 CLI is now running with Administrator rights, try to catalog node using this DB2 CLI console.

Posting Permissions

  • You may not post new threads
  • You may not post replies
  • You may not post attachments
  • You may not edit your posts
  •