Results 1 to 9 of 9
  1. #1
    Join Date
    Dec 2010
    Posts
    11

    Unanswered: Backup Online Incremental Failed

    DB2 Version : DWBE v9.5.0.1
    FIX PACK : 1
    OS : AIX 5.3
    ================================================== =======
    Hi... i have a problem.
    i always run online incremental for daily backup.

    and now i got backup failed... SQL2001N but i did'nt do anything make the utility interrupted and also SQL2036N The path for the file or device is not valid... i check every path and they still there, i also check that folder user privilege and they all granted... please anyone can help me i will appreciate that...

    regards,
    ajiep

    here my backup command:

    #!/bin/ksh
    . /db2home/bcuaix/sqllib/db2profile
    DT1=`date +"%Y%m%d"`
    db2_all "mkdir -p /backup_disk/DAILY/$DT1"
    cd /backup_disk/DAILY/$DT1
    echo "Start Backup: `date`" >> backupdaily.txt
    echo "Start Backup: `date`" >> /backup_disk/FULL/backupdaily.log
    db2 backup database BCUDB on all dbpartitionnums online incremental to /backup_disk/DAILY/$DT1 COMPRESS include logs WITHOUT PROMPTING | tee -a /backup_disk/FULL/backupdaily.log
    du -g >> /backup_disk/FULL/backupdaily.log
    echo "Stop Backup: `date`" >> backupdaily.txt
    echo "Stop Backup: `date`" >> /backup_disk/FULL/backupdaily.log

    here the log :

    Start Backup: Mon Dec 27 22:00:48 THAIST 2010
    Part Result
    ---- ------------------------------------------------------------------------
    0000 SQL2001N The utility was interrupted. The output data may be incomplete.
    0001 SQL2001N The utility was interrupted. The output data may be incomplete.
    0002 SQL2001N The utility was interrupted. The output data may be incomplete.
    0003 SQL2036N The path for the file or device "/backup_disk/DAILY/20101227" is not valid.
    0004 SQL2036N The path for the file or device "/backup_disk/DAILY/20101227" is not valid.
    0005 SQL2036N The path for the file or device "/backup_disk/DAILY/20101227" is not valid.
    0006 SQL2036N The path for the file or device "/backup_disk/DAILY/20101227" is not valid.

    SQL2429N The database backup failed. The following database partitions
    returned errors: "3,4,5,6".
    0.00 .
    Stop Backup: Mon Dec 27 22:00:59 THAIST 2010


    and also i check from db2diag log...
    here the db2diag log:

    010-12-29-22.00.48.562736+420 E53232893A476 LEVEL: Info
    PID : 467042 TID : 10643 PROC : db2sysc 0
    INSTANCE: bcuaix NODE : 000 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 10643 EDUNAME: db2agent (BCUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqlubMPPRequestor, probe:516
    DATA #1 : <preformatted>
    Starting a multi-partition backup on 7 partitions.

    2010-12-29-22.00.49.300119+420 E53233370A456 LEVEL: Info
    PID : 467042 TID : 13691 PROC : db2sysc 0
    INSTANCE: bcuaix NODE : 000 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 13691 EDUNAME: db2agntp (BCUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1503
    MESSAGE : Starting an online incremental db backup.

    2010-12-29-22.00.49.660614+420 E53233827A456 LEVEL: Info
    PID : 2105484 TID : 10822 PROC : db2sysc 2
    INSTANCE: bcuaix NODE : 002 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 10822 EDUNAME: db2agntp (BCUDB) 2
    FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1503
    MESSAGE : Starting an online incremental db backup.

    2010-12-29-22.00.49.873677+420 E53234284A456 LEVEL: Info
    PID : 2367526 TID : 9460 PROC : db2sysc 1
    INSTANCE: bcuaix NODE : 001 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 9460 EDUNAME: db2agntp (BCUDB) 1
    FUNCTION: DB2 UDB, database utilities, sqlubSetupJobControl, probe:1503
    MESSAGE : Starting an online incremental db backup.

    2010-12-29-22.00.56.949349+420 E53234741A550 LEVEL: Severe
    PID : 467042 TID : 13691 PROC : db2sysc 0
    INSTANCE: bcuaix NODE : 000 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 13691 EDUNAME: db2agntp (BCUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:583
    DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
    -2001
    DATA #2 : Hexdump, 0 bytes
    Object not dumped: Address: 0x07000008F2E01138 Size: 0 Reason: Zero-length data

    2010-12-29-22.00.56.949637+420 E53235292A908 LEVEL: Severe
    PID : 467042 TID : 13691 PROC : db2sysc 0
    INSTANCE: bcuaix NODE : 000 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 13691 EDUNAME: db2agntp (BCUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:583
    MESSAGE : SQL2001N The utility was interrupted. The output data may be
    incomplete.
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2001 sqlerrml: 0
    sqlerrmc:
    sqlerrp : sqlubcka
    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:

    2010-12-29-22.00.56.950803+420 E53236201A550 LEVEL: Severe
    PID : 2367526 TID : 9460 PROC : db2sysc 1
    INSTANCE: bcuaix NODE : 001 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 9460 EDUNAME: db2agntp (BCUDB) 1
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:583
    DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
    -2001
    DATA #2 : Hexdump, 0 bytes
    Object not dumped: Address: 0x077000014DDC1138 Size: 0 Reason: Zero-length data

    2010-12-29-22.00.56.951008+420 E53236752A908 LEVEL: Severe
    PID : 2367526 TID : 9460 PROC : db2sysc 1
    INSTANCE: bcuaix NODE : 001 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 9460 EDUNAME: db2agntp (BCUDB) 1
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:583
    MESSAGE : SQL2001N The utility was interrupted. The output data may be
    incomplete.
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2001 sqlerrml: 0
    sqlerrmc:
    sqlerrp : sqlubcka
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000001
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2010-12-29-22.00.56.951562+420 E53237661A550 LEVEL: Severe
    PID : 2105484 TID : 10822 PROC : db2sysc 2
    INSTANCE: bcuaix NODE : 002 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 10822 EDUNAME: db2agntp (BCUDB) 2
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:583
    DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
    -2001
    DATA #2 : Hexdump, 0 bytes
    Object not dumped: Address: 0x070000014EB11138 Size: 0 Reason: Zero-length data

    2010-12-29-22.00.56.951754+420 E53238212A908 LEVEL: Severe
    PID : 2105484 TID : 10822 PROC : db2sysc 2
    INSTANCE: bcuaix NODE : 002 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 10822 EDUNAME: db2agntp (BCUDB) 2
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:583
    MESSAGE : SQL2001N The utility was interrupted. The output data may be
    incomplete.
    DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
    sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2001 sqlerrml: 0
    sqlerrmc:
    sqlerrp : sqlubcka
    sqlerrd : (1) 0x00000000 (2) 0x00000000 (3) 0x00000000
    (4) 0x00000000 (5) 0x00000000 (6) 0x00000002
    sqlwarn : (1) (2) (3) (4) (5) (6)
    (7) (8) (9) (10) (11)
    sqlstate:

    2010-12-29-22.00.57.035985+420 E53239121A422 LEVEL: Severe
    PID : 467042 TID : 13691 PROC : db2sysc 0
    INSTANCE: bcuaix NODE : 000 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 13691 EDUNAME: db2agntp (BCUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:843
    MESSAGE : Backup terminated.

    2010-12-29-22.00.57.390386+420 E53239544A422 LEVEL: Severe
    PID : 2105484 TID : 10822 PROC : db2sysc 2
    INSTANCE: bcuaix NODE : 002 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 10822 EDUNAME: db2agntp (BCUDB) 2
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:843
    MESSAGE : Backup terminated.

    2010-12-29-22.00.57.412510+420 E53239967A422 LEVEL: Severe
    PID : 2367526 TID : 9460 PROC : db2sysc 1
    INSTANCE: bcuaix NODE : 001 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 9460 EDUNAME: db2agntp (BCUDB) 1
    FUNCTION: DB2 UDB, database utilities, sqlubcka, probe:843
    MESSAGE : Backup terminated.

    2010-12-29-22.00.57.413382+420 E53240390A443 LEVEL: Info
    PID : 467042 TID : 10643 PROC : db2sysc 0
    INSTANCE: bcuaix NODE : 000 DB : BCUDB
    APPHDL : 0-28432 APPID: *N0.bcuaix.101229150112
    AUTHID : BCUAIX
    EDUID : 10643 EDUNAME: db2agent (BCUDB) 0
    FUNCTION: DB2 UDB, database utilities, sqlubMPPRequestor, probe:850
    MESSAGE : Multi-partition backup complete.
    Last edited by ajiep; 12-30-10 at 06:46.

  2. #2
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    If -2001 is the only error logged in the db2diag.log, then it does look like the backup process got somehow interrupted.

  3. #3
    Join Date
    Jan 2011
    Posts
    1

    I want internet connection

    contact for new internet connection any where in area of Ahmedabad Instant service, installation in 24 hours and internet assistaince 24/7(sarkarss002013)Contact Number: 9377477801

  4. #4
    Join Date
    Dec 2010
    Posts
    11
    is there really any good if i peform restart db?

    anyway thanks for your responds

  5. #5
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    You can try to restart the db, but I don't know if this will help with the interrupt.

  6. #6
    Join Date
    Dec 2010
    Posts
    11
    i suspects this cause by some nodes is down... do you have any suggestion ?

  7. #7
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    You mean some nodes are not started? It doesn't look like based on the error, but you can add db2start to your backup script.

  8. #8
    Join Date
    Dec 2010
    Posts
    11
    ================================================== =======
    SQL2001N

    The utility was interrupted. The output data may be incomplete.
    Explanation

    The user may have pressed the interrupt key sequence, or had called the utility with a terminate caller action.

    This message can also be returned during a backup or restore operation on a database node when the database catalog node is down.

    The utility stops processing.
    User response

    Restart the application or reissue the command, if needed. The output data from the interrupted command may be incomplete, and should not be used.
    ================================================== ======

    maybe this is the root all of problem... what do you think?

  9. #9
    Join Date
    Aug 2008
    Location
    Toronto, Canada
    Posts
    2,367
    I'd have expected db2diag.log to contain some additional errors if some partitions were not started / or had crashed.

Posting Permissions

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