Results 1 to 10 of 10
  1. #1
    Join Date
    May 2006
    Posts
    4

    Red face Unanswered: DB2_ALL with SQL5005C on windows 2003

    Hi all,

    I am running a db2 instance on a 4 partitions spread over 4 servers.

    Each time I am issuing the db2_all command it replies SQL5005C on each remote partition like this:

    "c:\db2_all "db2 get db cfg for wpspwps"

    PPD-A-DATA-C01: db2 get db cfg for wpspwps completed rc=0

    rah: PPD-A-DATA-C02
    SQL5005C System Error.


    PPD-A-DATA-C02: db2 get db cfg for wpspwps completed rc=0

    rah: PPD-B-DATA-C03
    SQL5005C System Error.


    PPD-B-DATA-C03: db2 get db cfg for wpspwps completed rc=0

    rah: PPD-B-DATA-C04
    SQL5005C System Error.


    PPD-B-DATA-C04: db2 get db cfg for wpspwps completed rc=0

    But locally on each node the command can be issued without any pb.

    This is a production issue and then I can't process database backup of the partitioned databases using db2_all.

    Any suggestion will be really well appreciated to solve this pb.

    Thanks you.

  2. #2
    Join Date
    Jun 2001
    Posts
    20
    Check if the user in SYSADM_GROUP has the required NTFS read/write permissions on sqllib\instance_dir.
    Renga

  3. #3
    Join Date
    May 2006
    Posts
    4
    The sysadm_group is not set. I am using DB2ADMNS group by default. I checked the security permission of my shared instance directory and it has Full control for everyone. The instance directory is on a SAN disk which is owned by one machine at a time.
    If any other suggestions I will try, thanks.

  4. #4
    Join Date
    Jun 2001
    Posts
    20
    1. Check if ADMIN$ share is available on all particapting machines (use net share command)
    2. From all participating machines, check if you are able to connect to the registry of the instance owning machine.(regedit->File->Connect Network Registry)
    Renga

  5. #5
    Join Date
    May 2006
    Posts
    4
    Hi,

    I check yours suggestions the results are:

    1. from each partitcipating node the Admin$ is configured like that:
    C:\Documents and Settings\db2admin>net share

    Share name Resource Remark

    -------------------------------------------------------------
    R$ R:\ Default share
    J$ J:\ Default share
    C$ C:\ Default share
    K$ K:\ Default share
    S$ S:\ Default share
    P$ P:\ Default share
    Q$ Q:\ Default share
    N$ N:\ Default share
    IPC$ Remote IPC
    ADMIN$ C:\WINDOWS Remote Admin
    D$ D:\ Default share
    T$ T:\ Default share
    E$ E:\ Default share
    M$ M:\ Default share
    U$ U:\ Default share
    The command completed successfully.

    2. from each participating node the regedit provides the following:
    ppd-q-data-c01
    HKEY_LOCAL_MACHINE
    HKEY_USERS
    In fact, ppd-q-data-c01 is the owning instance machine and we can see the mentioned Registries from all the partiticipating machines.

  6. #6
    Join Date
    Jun 2001
    Posts
    20
    Check your PATH & CLASSPATH to see if they refer to the correct version of DB2
    Renga

  7. #7
    Join Date
    Jun 2001
    Posts
    20
    Also check the contents of db2rah.env file
    Renga

  8. #8
    Join Date
    May 2006
    Posts
    4
    My db2 version is 8.2.4 and as I am running an MSCS DB2 cluster, DB2 is installed on every participating machines.
    For sure, each machine is running the same DB2 version, the PATH and CLASSPATH are identical for each machine.

    What surprise me is when I move every DB2 partition on one machine, db2_all command performs perfectly.
    But when the partitions are spread over all machines, the error SQL5005C re-appears.

    Thanks for you advises, I am still ready to check any suggestions to make this system working.

  9. #9
    Join Date
    Oct 2004
    Location
    DELHI INDIA
    Posts
    338
    Hi,

    Just a suggestion: not sure though

    Check that you havenot changed the Password or Userid which is authorised as the Instance owner.

    If you have changed the User_id (e.g. earlier it is db2admin and now it is db_user1) of the Instance owner then go to each SERVICES and change the User with proper Password. Restart the Services one by one.

  10. #10
    Join Date
    Oct 2004
    Location
    DELHI INDIA
    Posts
    338
    Hi,

    Just a suggestion: not sure though

    Check that you havenot changed the Password or Userid which is authorised as the Instance owner.

    If you have changed the User_id (e.g. earlier it is db2admin and now it is db_user1) of the Instance owner then go to each SERVICES and change the User with proper Password. Restart the Services one by one.

Posting Permissions

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