|
Problem IT17649
|
Status: Closed |
FAILED OR INTERRUPTED SINGLE SYSTEM VIEW BACKUP IN PARTITIONED ENVIRONMENT MIGHT WRITE INCONSISTENT ENTRIES TO HISTORY FILE
|
| product: |
DB2 FOR LUW / DB2FORLUW / A50 - DB2 |
| Problem description: |
Failed or interrupted single system view backup should be
all-or-nothing: failure on one partition should fail all
partitions.
Under certain scenarios, some of the partitions will write
successful entries to the history file despite the fact that
other
partition failed:
Partition 0
List History File for db2ixp05
Number of matching file entries = 1
Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log
Backup ID
-- --- ------------------ ---- --- ------------ ------------
--------------
B D 20161025015309000 F S0000001.LOG S0000001.LOG
----------------------------------------------------------------
------------
Contains 2 tablespace(s):
00001 SYSCATSPACE
00002 USERSPACE1
----------------------------------------------------------------
------------
Comment: DB2 BACKUP DB2IXP05 OFFLINE
Start Time: 20161025015309
End Time: 20161025015310
Status: A
----------------------------------------------------------------
------------
EID: 5 Location:
Partition 1:
List History File for db2ixp05
Number of matching file entries = 1
Op Obj Timestamp+Sequence Type Dev Earliest Log Current Log
Backup ID
-- --- ------------------ ---- --- ------------ ------------
--------------
B D 20161025015309000 F S0000001.LOG S0000001.LOG
----------------------------------------------------------------
------------
Contains 1 tablespace(s):
00001 USERSPACE1
----------------------------------------------------------------
------------
Comment: DB2 BACKUP DB2IXP05 OFFLINE
Start Time: 20161025015309
End Time: 20161025015310
Status: A
----------------------------------------------------------------
------------
EID: 4 Location:
SQLCA Information
sqlcaid : SQLCA sqlcabc: 136 sqlcode: -2001 sqlerrml: 0
sqlerrmc:
sqlerrp : sqlubPol
sqlerrd : (1) 0 (2) 0 (3) 0
(4) 0 (5) 0 (6) 1
sqlwarn : (1) (2) (3) (4) (5) (6)
(7) (8) (9) (10) (11)
sqlstate: |
| Problem Summary: |
****************************************************************
* USERS AFFECTED: *
* ALL *
****************************************************************
* PROBLEM DESCRIPTION: *
* See Error Description *
****************************************************************
* RECOMMENDATION: *
* See SYSROUTE APARs to see where this APAR is addressed *
**************************************************************** |
| Local Fix: |
|
| Solution |
|
| Workaround |
not known / see Local fix |
| Timestamps |
Date - problem reported :
Date - problem closed :
Date - last modified :
| 25.10.2016
08.05.2017
08.05.2017 |
| Problem solved at the following versions (IBM BugInfos) |
|
| Problem solved according to the fixlist(s) of the following version(s) |
