Results 1 to 10 of 10
  1. #1
    Join Date
    May 2013
    Posts
    25

    Unanswered: db2 9.7 -> 10.1 upgrade problem

    Hello again ,

    I am trying to upgrade my db2 from 9.7 to 10.1.

    I installed as root the db10.1 binaries in parallel with 9.7, deactivated the dbs, disabled hadr, stopped instance etc

    I ran as root the db2iupgrade tool (/db2/V10.1/instance/db2iupgrade -u db2inst db2inst)

    and I get the following error from the logs
    Database: "DOOS01"

    [IBM][CLI Driver][DB2/AIX64] SQL1326N The file or directory "/db2/db.DOOS01/db2inst" cannot be accessed.
    /db2/db.DOOS01/db2inst has of course the proper rights.

    Any help?

  2. #2
    Join Date
    May 2003
    Location
    USA
    Posts
    5,737
    The -u is for the fenced user and not the instance owner id. I think this is optional and you should try without it.
    M. A. Feldman
    IBM Certified DBA on DB2 for Linux, UNIX, and Windows
    IBM Certified DBA on DB2 for z/OS and OS/390

  3. #3
    Join Date
    May 2013
    Posts
    25
    I have also tried without it (/db2/V10.1/instance/db2iupgrade db2inst) but I get the same error.

  4. #4
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    What are the permissions/ownership on /db2/db.DOOS01/db2inst?
    Can you connect to this db using instance owner?
    Is /db2/db.DOOS01/db2inst your db directory?
    Did you execute db2ckupgrade?
    Are there any logs created in /tmp or anything logged in the db2diag.log?
    Last edited by db2girl; 06-14-13 at 16:10.

  5. #5
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by Haros View Post
    /db2/db.DOOS01/db2inst has of course the proper rights.
    And what are the proper rights, I wonder?

    There's a "-d" command line option to db2iupgrade, which should cause it to spit out more detailed information that might be useful for troubleshooting.

    Check also /tmp for db2iupgrade.* files.
    ---
    "It does not work" is not a valid problem statement.

  6. #6
    Join Date
    May 2013
    Posts
    25
    Quote Originally Posted by db2girl View Post
    What are the permissions/ownership on /db2/db.DOOS01/db2inst?
    Can you connect to this db using instance owner?
    Is /db2/db.DOOS01/db2inst your db directory?
    Did you execute db2ckupgrade?
    Are there any logs created in /tmp or anything logged in the db2diag.log?

    Quote Originally Posted by n_i View Post
    And what are the proper rights, I wonder?

    There's a "-d" command line option to db2iupgrade, which should cause it to spit out more detailed information that might be useful for troubleshooting.

    Check also /tmp for db2iupgrade.* files.
    The permissions are 775 (rwxrwxr x) the db2 default.

    I can connect with no problem as the instance owner.

    db2/db.DOOS01/db2inst is my db directory. Inside db2inst folder I can find a folder called NODE0000 which contains folders SQL00001 and sqldbdir. I think the structure is normal...

    I executed the check upgrade tool. From this tool I got the log export I posted.

    The other error log files in /tmp don't have something clear. The errors are like the one below
    ERROR: An error occurred while configuring the instance "db2inst".

    Configuring DB2 instances :.......Failure
    Updating global profile registry :.......Success
    I am attaching my db2diag.log (note that there are other dbs in this instance failing with the same error)

    Thanks for the help.
    Attached Files Attached Files

  7. #7
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by Haros View Post
    The permissions are 775 (rwxrwxr x) the db2 default.
    Obviously, that's not true:

    Quote Originally Posted by db2diag.log
    A total of 2 analysis will be performed :
    - User info
    - Path access permission

    Target file = /sccm/db2/db.DOOS01/db2inst
    DATA #2 : String, 188 bytes
    Real user ID of current process = 1299
    Effective user ID of current process = 1299
    Real group ID of current process = 1299
    Effective group ID of current process = 1299
    DATA #3 : String, 41 bytes
    current sbrk(0) value: 0x0000000110390e20
    DATA #4 : String, 279 bytes
    Information of each subdirectory leading up to the first inaccessible one is shown in the format below :
    <UID>:<GID>:<permissions> (subdirectories)

    0:0:755 (sccm)
    1300:1300:755 (db2)
    1300:1300:700 (db.DOOS01)
    The permissions, as evident from the above, are set to 755 for the directory db2 and 700 for db.DOOS01. The UID for the instance owner seems to be incorrect either. What are the users with UIDs 1299 and 1300?
    ---
    "It does not work" is not a valid problem statement.

  8. #8
    Join Date
    May 2013
    Posts
    25
    from /etc/passwd:
    db2inst:!:1300:1300::/sccm/db2/home/db2inst:/usr/bin/ksh
    db2fenc:!:1299:1299::/sccm/db2/home/db2fenc:/usr/bin/ksh
    You are correct, the db2 folder permissions and db.* are 755 and 700. Owned by db2inst user.

    I didn't install the instance so I thought every permission setting would be default. Could you advise me for a correct user / permission setup? (db2iupdt doesn't change anything. I guess these folder permissions are out of the tool's scope).

    Thanks in advance.

  9. #9
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367

  10. #10
    Join Date
    May 2013
    Posts
    25
    Changed db2 and db.* folders to 775 as recommended and everything worked :-)

    Thank you very much.

Posting Permissions

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