Results 1 to 4 of 4
  1. #1
    Join Date
    Sep 2003
    Location
    Nevada
    Posts
    14

    Unanswered: DB2 SQL1652N problem

    hi,

    I have installed db2 runclient on a pc that connects to a db2 server on another pc.

    when i login to the pc which has client on it with a username that has administrative rights on that pc ..i can use db2 command window and db2 command processor fine.

    but if i login with the username that doesn't have administrative rights, and when i try to access db2 command window ..it gives me a message

    DB21652N error : external File I/O error occured.

    can anyone let me know why i am getting this error and what might be the solution for this?

    the database i am using is windows version of DB2 7.2

    thank you
    Raj

  2. #2
    Join Date
    Sep 2003
    Location
    Nevada
    Posts
    14

    Re: DB2 SQL1652N problem

    the error looks like this:

    DB2CMD.EXE->0
    SQL1652N FILE I/O ERROR OCCURED.


    thanks,
    Raj




    Originally posted by raj_sudhan
    hi,

    I have installed db2 runclient on a pc that connects to a db2 server on another pc.

    when i login to the pc which has client on it with a username that has administrative rights on that pc ..i can use db2 command window and db2 command processor fine.

    but if i login with the username that doesn't have administrative rights, and when i try to access db2 command window ..it gives me a message

    DB21652N error : external File I/O error occured.

    can anyone let me know why i am getting this error and what might be the solution for this?

    the database i am using is windows version of DB2 7.2

    thank you
    Raj

  3. #3
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    Do you have the Messages and Codes manuals? The manuals are downloadable from the IBM website and can be searched with Adobe Acrobat Reader.

    SQL1652N File I/O error occurred.

    Explanation: Error occurred either opening,
    reading, writing, or closing a file.

    User Response: Check the db2diag.log for
    details. Also, check for disk full conditions, file
    permissions, and operating system errors.

  4. #4
    Join Date
    Sep 2003
    Location
    Nevada
    Posts
    14

    re:SQL1652N Problem

    Thank you marcus,

    The problem was with the permissions to the SQLLIB folder. As soon as i gave the write permission to every user for the folder SQLLIB , everything went fine...

    Raj

Posting Permissions

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