Results 1 to 4 of 4
  1. #1
    Join Date
    Jul 2010
    Posts
    2

    Unhappy Unanswered: DB2 V9.7 ESE Restore previous backup error out

    Hi,
    After I reinstalled the OS and DB2, I got this weird error message when I tried to restore from a previous backup image(which is a redirect DB).
    I already reinstalled DB2 several times, but every time this issue can be recreated. Any ideas how to fix it?

    From the error message, I pretty sure at least there is one DB2 bug.

    2010-07-22-00.34.50.671000+480 E38321H971 LEVEL: Severe
    PID : 5404 TID : 6632 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000 DB : PHASE13
    APPHDL : 0-23 APPID: *LOCAL.DB2.100721163400
    AUTHID : SYSTEM
    EDUID : 6632 EDUNAME: db2agent (PHASE13) 0
    FUNCTION: DB2 UDB, database utilities, sqludProcessDBCfg, probe:591
    MESSAGE : SQL5130N The value specified for the configuration parameter "" is
    not in the valid range of "" to "".
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -5130 sqlerrml: 0
    sqlerrmc:
    sqlerrp : sqludPro
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000000
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

  2. #2
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by bulier View Post
    Any ideas how to fix it?

    From the error message, I pretty sure at least there is one DB2 bug.
    Well, if you are sure there is a bug, you should also be pretty sure how to fix it.

    I, however, am not so sure. The errors like yours could happen when you restore a backup taken on a 64-bit system to a 32-bit system. Some database configuration parameters, which are restored along with the database, may be valid for a 64-bit environment but would be invalid on a 32-bit system.

  3. #3
    Join Date
    Jul 2010
    Posts
    2
    Quote Originally Posted by n_i View Post
    Well, if you are sure there is a bug, you should also be pretty sure how to fix it.

    I, however, am not so sure. The errors like yours could happen when you restore a backup taken on a 64-bit system to a 32-bit system. Some database configuration parameters, which are restored along with the database, may be valid for a 64-bit environment but would be invalid on a 32-bit system.
    Thanks a lot for looking into this, I used a backup from 32-bit system. Actually it's from the same machine and both using Win XP 32-bit.
    Just complain such meaningless error message (like empty string). So I said it might be a DB2 bug.

  4. #4
    Join Date
    Jun 2003
    Location
    Toronto, Canada
    Posts
    5,516
    Provided Answers: 1
    Quote Originally Posted by bulier View Post
    Thanks a lot for looking into this, I used a backup from 32-bit system. Actually it's from the same machine and both using Win XP 32-bit.
    It isn't necessarily about the bitness - there are other things that may change in the OS that invalidate DB2 configuration settings, such as AWE or authentication. Think about what settings you have changed when you reinstalled the OS.

Posting Permissions

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