Results 1 to 6 of 6
  1. #1
    Join Date
    Feb 2014
    Posts
    13

    Unanswered: db2 database partition groups

    Tried the following command from catalog node. It is showing the following error.
    Please suggest if any thing need to be corrected .

    [db2part2@ha ~]$ db2 list database partition groups
    SQL0204N "SYSCAT.DBPARTITIONGROUPS" is an undefined name. SQLSTATE=42704

    from normal db i am able to see the output. But its failing for this partitioned database only.

  2. #2
    Join Date
    May 2005
    Posts
    29
    thats a strange one. Does everything else work ok in the database? Anything in the db2diag.log that can help?

  3. #3
    Join Date
    Feb 2014
    Posts
    13
    I had done a restore and it went fine. After restore tried below mentioned query but its failing.

    As part of test - created another database on same server and all queries are showing correct result on this new db.

    Is there any chance of missing tables during restore ? But i am sure that db is restored on all the 4 nodes from correct backup images.

    db2diag.log

    2014-02-26-08.49.50.353708+330 I7882446E1099 LEVEL: Warning
    PID : 27202 TID : 1105209664 PROC : db2acd 0
    INSTANCE: db2part2 NODE : 000
    FUNCTION: DB2 UDB, Health Monitor, HmonMainCB:repDBForFirstPlugin, probe:100
    MESSAGE : Failed to verify and create policy for database "TEST ". rc =
    90000002
    DATA #1 : Hexdump, 136 bytes
    0x0000000041E005D0 : 5351 4C43 4120 2020 8800 0000 44FE FFFF SQLCA ....D...
    0x0000000041E005E0 : 4600 2A4C 4F42 4A45 4354 53FF 5351 4C31 F.*LOBJECTS.SQL1
    0x0000000041E005F0 : 3430 3232 3630 3834 3935 3033 3430 FF2E 40226084950340..
    0x0000000041E00600 : 2E2E 6675 6E63 7469 6F6E 2F53 5953 5052 ..function/SYSPR
    0x0000000041E00610 : 4F43 2E53 5953 494E 5354 414C 4C4F 424A OC.SYSINSTALLOBJ
    0x0000000041E00620 : 4543 5453 FF2A FF34 5351 4C45 524C 4942 ECTS.*.4SQLERLIB
    0x0000000041E00630 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0000000041E00640 : 0000 0000 0000 0000 2020 2020 2020 2020 ........
    0x0000000041E00650 : 2020 2034 3237 3234 42724

    2014-02-26-08.49.50.366322+330 I7883546E1099 LEVEL: Warning
    PID : 27202 TID : 1105209664 PROC : db2acd 0
    INSTANCE: db2part2 NODE : 000
    FUNCTION: DB2 UDB, Health Monitor, HmonMainCB:repDBForFirstPlugin, probe:100
    MESSAGE : Failed to verify and create policy for database "TEST ". rc =
    90000002
    DATA #1 : Hexdump, 136 bytes
    0x0000000041E005D0 : 5351 4C43 4120 2020 8800 0000 44FE FFFF SQLCA ....D...
    0x0000000041E005E0 : 4600 2A4C 4F42 4A45 4354 53FF 5351 4C31 F.*LOBJECTS.SQL1
    0x0000000041E005F0 : 3430 3232 3630 3834 3935 3033 3630 FF2E 40226084950360..
    0x0000000041E00600 : 2E2E 6675 6E63 7469 6F6E 2F53 5953 5052 ..function/SYSPR
    0x0000000041E00610 : 4F43 2E53 5953 494E 5354 414C 4C4F 424A OC.SYSINSTALLOBJ
    0x0000000041E00620 : 4543 5453 FF2A FF34 5351 4C45 524C 4942 ECTS.*.4SQLERLIB
    0x0000000041E00630 : 0000 0000 0000 0000 0000 0000 0000 0000 ................
    0x0000000041E00640 : 0000 0000 0000 0000 2020 2020 2020 2020 ........

  4. #4
    Join Date
    May 2005
    Posts
    29
    Depending on the version of your DB2, you might needs grants in the restore db, if the users are different from source and target db.

    Did you check to see if the table SYSCAT.DBPARTITIONGROUPS exist and you can access it?

    All the tablespaces in normal state?

    Those diaglog messages are warnings, any severe or error?

  5. #5
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by harihara View Post
    I had done a restore and it went fine.
    Did you by chance restore from a backup made with an earlier version or fix pack?
    ---
    "It does not work" is not a valid problem statement.

  6. #6
    Join Date
    Feb 2014
    Posts
    13
    @all

    some thing went wrong in my test environment.
    all syscat tables are showing error as "SQL0204N "SYSCAT.DBAUTH" is an undefined name. SQLSTATE=42704"

    [db2part2@db2 ~]$ db2level
    DB21085I Instance "db2part2" uses "64" bits and DB2 code release "SQL09075"
    with level identifier "08060107".
    Informational tokens are "DB2 v9.7.0.5", "s111017", "IP23292", and Fix Pack
    "5".
    Product is installed at "/opt/ibm/db2/V9.7".

    I will tryout the same test on new db and let you know the result.

    Thanks.

Tags for this Thread

Posting Permissions

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