Results 1 to 13 of 13
  1. #1
    Join Date
    Sep 2010
    Posts
    8

    Question Unanswered: Corrupted database backups db2ckbck

    Hi,

    We have a problem that the db2ckbck command return unsuccessful results. The same result is returned with online backups and offline ones. However, the system is working properly, connections to the database are working and all "inconsistent tablespaces" are available as well.

    The database backups used to work and somehow, they became corrupted.

    DB2 version is 8.2.4 and OS is Windows Server 2003 32 bit.

    C:\Documents and Settings\Administrator>db2ckbkp D:\backupcgs\CGS.0\DB2\NODE0000\CATN0000\20100829\ 181354.001

    [1] Buffers processed: #######ERROR - Tablespace page size inconsistent for tablespace ID 8.
    ERROR - Tablespace page size inconsistent for tablespace ID 8.
    ERROR - Tablespace page size inconsistent for tablespace ID 8.
    ERROR - Tablespace page size inconsistent for tablespace ID 8.
    ERROR - Tablespace page size inconsistent for tablespace ID 8.
    ###ERROR - Tablespace page size inconsistent for tablespace ID 2.
    #ERROR - Tablespace page size inconsistent for tablespace ID 11.
    ERROR - Tablespace page size inconsistent for tablespace ID 11.
    ERROR - Tablespace page size inconsistent for tablespace ID 11.
    ERROR - Tablespace page size inconsistent for tablespace ID 11.
    ERROR - Tablespace page size inconsistent for tablespace ID 11.
    ERROR - Tablespace page size inconsistent for tablespace ID 11.
    #####ERROR - Tablespace page size inconsistent for tablespace ID 2.
    #ERROR - Tablespace page size inconsistent for tablespace ID 2.
    #ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    ERROR - Tablespace page size inconsistent for tablespace ID 0.
    #ERROR - Tablespace page size inconsistent for tablespace ID 2.
    ERROR - Tablespace page size inconsistent for tablespace ID 2.
    ERROR - Tablespace page size inconsistent for tablespace ID 2.
    ERROR - Tablespace page size inconsistent for tablespace ID 2.
    ERROR - Tablespace page size inconsistent for tablespace ID 2.
    ERROR - Tablespace page size inconsistent for tablespace ID 2.
    ERROR - Tablespace page size inconsistent for tablespace ID 2.
    #####ERROR - Tablespace page size inconsistent for tablespace ID 2.
    ERROR - Tablespace page size inconsistent for tablespace ID 2.
    ERROR - Tablespace page size inconsistent for tablespace ID 2.
    ERROR - Tablespace page size inconsistent for tablespace ID 2.

    1.
    1.

    ERROR! No DATA.POOL.TABLE!
    ERROR! No DB configuration!
    ERROR! No BUFFER.POOL.FILE found!
    ERROR! No MIRRORLOG.FILE.HEADER found!
    ERROR! No END.OF.INITIAL.DATA found!

    Image Verification Complete - ERRORS DETECTED: 697

  2. #2
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    First, you should really consider upgrading to some version of V9 (9.1, 9.5, or 9.7). V8 has been out of service for some time.

    Second, how are you performing the backups?

    Third, has anything changed on the system recently?

    Andy

  3. #3
    Join Date
    Sep 2010
    Posts
    8
    Hi Andy,

    I know about the DB2 version, but we have to support old version for our existing customer. We've been using version 8 since 6 years without such a problem.

    We do perform backup from the command line with:
    db2 backup db dbname to c:\
    or

    db2 "backup db dbname online to c:\ include logs"

    We have the same problem with both commands.

    Thanks,

    Julie

  4. #4
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    Has anything changed on the system recently?

    Can you backup to someplace else and see what happens?

    Andy

  5. #5
    Join Date
    Sep 2010
    Posts
    8
    Hi Andy,

    We tried backing up on different folders but it did not help.
    We did increase the database heap size.

    Thanks,

    Julie

  6. #6
    Join Date
    Sep 2010
    Posts
    8
    Hi Andy,
    More information:

    Default was 256
    db2 update db cfg for dbname using sortheap 512

    Thanks,

    Julie

  7. #7
    Join Date
    Sep 2010
    Posts
    8

    more information...

    We also added a bufferpool to the db:

    CREATE TEMPORARY TABLESPACE TEMPORARYSP PAGESIZE 8 K MANAGED BY SYSTEM USING ('TEMPORARYSP' ) EXTENTSIZE 16 OVERHEAD 12.67 PREFETCHSIZE 16 TRANSFERRATE 0.18 BUFFERPOOL CGS8BP DROPPED TABLE RECOVERY OFF

  8. #8
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5

    1949. themiter

    I am fairly certain that sortheap has nothing to do with backup. What is the value for util_heap_sz?

    Andy

  9. #9
    Join Date
    Sep 2010
    Posts
    8

    238pu iracle

    It's 20000

  10. #10
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    That is fairly large, especially for a 32 bit system. Try cutting it in half. How big is your database?

    Andy

  11. #11
    Join Date
    Sep 2010
    Posts
    8
    Hi Andy,

    The database backup is 416mb. I will verify if we could decrease the util heap size, however the value is the same for some years. Do you think he could have corrupted the backups?

    Thanks.

    Julie

  12. #12
    Join Date
    Jan 2003
    Posts
    4,292
    Provided Answers: 5
    I do not know what is corrupting your backup images. You database is rather small, so reducing the util_heap_sz should not hurt anything. Your system is 32 bit windows, which really does not give you a lot of memory for heaps and buffers to work with. And being v8.2, you cannot get any support from IBM since it is out of service. You could try the latest FP for V8 and see if that does not help.

    Andy

  13. #13
    Join Date
    Sep 2010
    Posts
    8

    Lightbulb problem solved

    Actually it was caused by a problem I've noticed into the db2diag.log file.

    2010-08-31-14.25.58.709000-240 I901775637H374 LEVEL: Error
    PID : 2220 TID : 2608 PROC : db2syscs.exe
    INSTANCE: DB2 NODE : 000
    FUNCTION: DB2 UDB, data protection, sqlpgArchiveLogDisk, probe:2620
    RETCODE : ZRC=0x870F0011=-2029060079=SQLO_PATH "an invalid path"
    DIA8514C An invalid file path, "", was specified.

    The logs were not properly archived because the full path was not specified for archiving into our software. So now it is fixed and the backup are not corrupted anymore. I'm not sure I understand the link between those 2 things...

Posting Permissions

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