Topic
  • 3 replies
  • Latest Post - ‏2013-09-20T08:26:11Z by Zahni
Kasparek
Kasparek
4 Posts

Pinned topic DB2 9.7 Automatic Maintenance - Offline Backup

‏2013-09-18T10:16:16Z |

Enabled Automatic Maintenance and configured Backup Policy for offline backup. When an offline maintenance window is reached, DB2 engine tries to start offline backup, but fails with error:

2013-09-13-19.20.00.540695+120 E19757838A766      LEVEL: Severe
PID     : 24183018             TID  : 1093        PROC : db2acd 0
INSTANCE: db2name               NODE : 000
EDUID   : 1093                 EDUNAME: db2acd 0
FUNCTION: DB2 UDB, database utilities, sqlubConnectDatabase, probe:1261
MESSAGE : SQL1035N  The database is currently in use.
DATA #1 : SQLCA, PD_DB2_TYPE_SQLCA, 136 bytes
 sqlcaid : SQLCA     sqlcabc: 136   sqlcode: -1035   sqlerrml: 0
 sqlerrmc:
 sqlerrp : sqlubCon
 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: 57019

2013-09-13-19.20.00.540525+120 E19757398A439      LEVEL: Severe
PID     : 24183018             TID  : 1093        PROC : db2acd 0
INSTANCE: db2name               NODE : 000
EDUID   : 1093                 EDUNAME: db2acd 0
FUNCTION: DB2 UDB, database utilities, sqlubConnectDatabase, probe:1261
DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
-1035
DATA #2 : Hexdump, 4 bytes
0x0000000110529BF8 : FFFF FBF5                                  ....

Is Automatic Offline Backup feature supposed to run with any intervention, i.e. deactivating database in advance, or not? If yes, why it doesn't succeed in my case?

Updated on 2013-09-18T10:17:29Z at 2013-09-18T10:17:29Z by Kasparek
  • 9RYQ_Kiran_mk
    9RYQ_Kiran_mk
    78 Posts

    Re: DB2 9.7 Automatic Maintenance - Offline Backup

    ‏2013-09-19T09:00:50Z  

    Yes. While running the Offline Backup no connections should be allowed.  Better Quiesce the DB before the offline backup starts and unquiesce once the Backup is completed.

    Best Regards,

    Kiran.M.K.

  • Kasparek
    Kasparek
    4 Posts

    Re: DB2 9.7 Automatic Maintenance - Offline Backup

    ‏2013-09-19T09:07:55Z  

    Yes. While running the Offline Backup no connections should be allowed.  Better Quiesce the DB before the offline backup starts and unquiesce once the Backup is completed.

    Best Regards,

    Kiran.M.K.

    I can see the following in db2diag.log:
     
    MESSAGE : ADM7506W A request was made to quiesce a database with the following quiesce mode: "QUIESCE DATABASE"
     
    MESSAGE : ADM7507W Database quiesce request has completed successfully.
     
    START : DATABASE: NAME : ACTIVATED: NO
     
    According to this DB2 tries to quiesce database and even deactivate database.
     
    But then 2 Severe Errors occurs:
     
    2013-09-13-19.20.39.991980+120 I19762699A444 LEVEL: Severe
    PID : 5832722 TID : 22055 PROC : db2sysc 0
    INSTANCE: db2name NODE : 000 DB : NAME
    APPHDL : 0-48802 APPID: *LOCAL.db2srt.130913172036
    AUTHID : DB2SRT
    EDUID : 22055 EDUNAME: db2agent (SRT) 0
    FUNCTION: DB2 UDB, base sys utilities, sqeApplication::AppStartUsing, probe:140
    RETCODE : ZRC=0xFFFFFBF5=-1035
     
    2013-09-13-19.20.39.992955+120 E19763144A439 LEVEL: Severe
    PID : 24183018 TID : 1093 PROC : db2acd 0
    INSTANCE: db2name NODE : 000
    EDUID : 1093 EDUNAME: db2acd 0
    FUNCTION: DB2 UDB, database utilities, sqlubConnectDatabase, probe:1261
    DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
    -1035
    DATA #2 : Hexdump, 4 bytes
    0x0000000110529BF8 : FFFF FBF5

    So a root cause of problems is somewhere else.

  • Zahni
    Zahni
    16 Posts

    Re: DB2 9.7 Automatic Maintenance - Offline Backup

    ‏2013-09-20T08:26:11Z  
    • Kasparek
    • ‏2013-09-19T09:07:55Z
    I can see the following in db2diag.log:
     
    MESSAGE : ADM7506W A request was made to quiesce a database with the following quiesce mode: "QUIESCE DATABASE"
     
    MESSAGE : ADM7507W Database quiesce request has completed successfully.
     
    START : DATABASE: NAME : ACTIVATED: NO
     
    According to this DB2 tries to quiesce database and even deactivate database.
     
    But then 2 Severe Errors occurs:
     
    2013-09-13-19.20.39.991980+120 I19762699A444 LEVEL: Severe
    PID : 5832722 TID : 22055 PROC : db2sysc 0
    INSTANCE: db2name NODE : 000 DB : NAME
    APPHDL : 0-48802 APPID: *LOCAL.db2srt.130913172036
    AUTHID : DB2SRT
    EDUID : 22055 EDUNAME: db2agent (SRT) 0
    FUNCTION: DB2 UDB, base sys utilities, sqeApplication::AppStartUsing, probe:140
    RETCODE : ZRC=0xFFFFFBF5=-1035
     
    2013-09-13-19.20.39.992955+120 E19763144A439 LEVEL: Severe
    PID : 24183018 TID : 1093 PROC : db2acd 0
    INSTANCE: db2name NODE : 000
    EDUID : 1093 EDUNAME: db2acd 0
    FUNCTION: DB2 UDB, database utilities, sqlubConnectDatabase, probe:1261
    DATA #1 : Sqlcode, PD_TYPE_SQLCODE, 4 bytes
    -1035
    DATA #2 : Hexdump, 4 bytes
    0x0000000110529BF8 : FFFF FBF5

    So a root cause of problems is somewhere else.

    Make sure, you don't give other users too much rights, f.e. "QUIESCE_CONNECT"  and "DBADM".

    Users with this privileges  can reconnect immediately after force connections.

    Some tools, f.e. the Data Studio, may do it  at default.

    Your backup-user must have these rights !!!