suche 36x36
Latest versionsfixlist
11.1.0.7 FixList
10.5.0.9 FixList
10.1.0.6 FixList
9.8.0.5 FixList
9.7.0.11 FixList
9.5.0.10 FixList
9.1.0.12 FixList
Have problems? - contact us.
Register for free anmeldung-x26
Contact form kontakt-x26

DB2 - Problem description

Problem IT31363 Status: Closed

SQL2536W DURING BACKUP

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
$ db2level
DB21085I  This instance or install (instance name, where
applicable:
"db2inst1") uses "64" bits and DB2 code release "SQL11014" with
level identifier "0205010F".
Informational tokens are "DB2 v11.1.4.5", "s1911120100",
"DYN1911120100AIX", and Fix Pack "5".
Product is installed at
"/view/db2_v111m4fp5_aix64_s1911120100/vbs/INST".

$ mkdir Backup1
$ mkdir Backup2
$ mkdir Backup3
$ db2 create db test1
$ db2 create db test2
$ db2 -v "backup db test1 to /home/db2inst1/Backup1,
/home/db2inst1/Backup1, /home/db2inst1/Backup1,
/home/db2inst1/Backup2, /home/db2inst1/Backup2,
/home/db2inst1/Backup2, /home/db2inst1/Backup3,
/home/db2inst1/Backup3, /home/db2inst1/Backup3"

Backup successful. The timestamp for this backup image is :
20191209120011

$ db2 connect to test1
$ db2 "Select START_TIME , END_TIME , SEQNUM , LOCATION from
SYSIBMADM.DB_HISTORY WHERE OPERATION ='B' AND START_TIME IN
(SELECT MAX(START_TIME) from SYSIBMADM.DB_HISTORY WHERE
OPERATION ='B')"

START_TIME     END_TIME       SEQNUM LOCATION

20191209120011 20191209120012 1 /home/db2inst1/Backup1
20191209120011 20191209120012 2 /home/db2inst1/Backup1
20191209120011 20191209120012 3 /home/db2inst1/Backup2
20191209120011 20191209120012 4 /home/db2inst1/Backup3
20191209120011 20191209120012 5 /home/db2inst1/Backup2
20191209120011 20191209120012 6 /home/db2inst1/Backup1
20191209120011 20191209120012 7 /home/db2inst1/Backup2
20191209120011 20191209120012 8 /home/db2inst1/Backup3
20191209120011 20191209120012 9 /home/db2inst1/Backup3

  9 record(s) selected.

$ db2 connect reset
$ ls -lat Backup*

Backup1:
total 98360
-rw-------    1 db2inst1 pdxdb2     16785408 Dec 09 12:00
TEST1.0.db2inst1.DBPART000.20191209120011.002
drwxr-xr-x    2 db2inst1 pdxdb2          256 Dec 09 12:00 .
-rw-------    1 db2inst1 pdxdb2     33566720 Dec 09 12:00
TEST1.0.db2inst1.DBPART000.20191209120011.001
-rw-------    1 db2inst1 pdxdb2         4096 Dec 09 12:00
TEST1.0.db2inst1.DBPART000.20191209120011.006
drwxr-xr-x   13 db2inst1 pdxdb2         4096 Dec 09 11:57 ..

Backup2:
total 98360
-rw-------    1 db2inst1 pdxdb2     16785408 Dec 09 12:00
TEST1.0.db2inst1.DBPART000.20191209120011.005
-rw-------    1 db2inst1 pdxdb2     16785408 Dec 09 12:00
TEST1.0.db2inst1.DBPART000.20191209120011.003
-rw-------    1 db2inst1 pdxdb2     16785408 Dec 09 12:00
TEST1.0.db2inst1.DBPART000.20191209120011.007
drwxr-xr-x    2 db2inst1 pdxdb2          256 Dec 09 12:00 .
drwxr-xr-x   13 db2inst1 pdxdb2         4096 Dec 09 11:57 ..

Backup3:
total 98416
-rw-------    1 db2inst1 pdxdb2     16785408 Dec 09 12:00
TEST1.0.db2inst1.DBPART000.20191209120011.004
-rw-------    1 db2inst1 pdxdb2     16814080 Dec 09 12:00
TEST1.0.db2inst1.DBPART000.20191209120011.009
drwxr-xr-x    2 db2inst1 pdxdb2          256 Dec 09 12:00 .
-rw-------    1 db2inst1 pdxdb2     16785408 Dec 09 12:00
TEST1.0.db2inst1.DBPART000.20191209120011.008
drwxr-xr-x   13 db2inst1 pdxdb2         4096 Dec 09 11:57 ..

$ db2 -v "restore db test1 from /home/db2inst1/Backup1,
/home/db2inst1/Backup1, /home/db2inst1/Backup1,
/home/db2inst1/Backup2, /home/db2inst1/Backup2,
/home/db2inst1/Backup2, /home/db2inst1/Backup3,
/home/db2inst1/Backup3, /home/db2inst1/Backup3 into test2
replace history file"

SQL2529W  Warning!  Restoring to an existing database that is
different from
the backup image database, and the alias name "TEST2" of the
existing database
does not match the alias name "TEST1" of the backup image, and
the database
name "TEST2" of the existing database does not match the
database name "TEST1"
of the backup image. The target database will be overwritten by
the backup
version. The Roll-forward recovery logs associated with the
target database
will be deleted.
Do you want to continue ? (y/n) y
SQL2536W  Warning!  The backup image on device
"/home/db2inst1/Backup1"
contains an incorrect sequence number.  Sequence number "3" is
expected.
Do you want to continue(c), terminate this device only(d), abort
the utility(t) ? (c/d/t) c
DB20000I  The RESTORE DATABASE command completed successfully.

$ db2 connect to test2

   Database Connection Information

Database server        = DB2/AIX64 11.1.4.5
SQL authorization ID   = db2inst1
Local database alias   = TEST2
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* Db2 for LUW                                                  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* The fix is planned to be delivered to v11.5.6, but it could  *
* be changed. Please confirm with IBM before the upgrade.      *
****************************************************************
Local Fix:
N/A
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* Db2 for LUW                                                  *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* The fix is planned to be delivered to v11.5.6, but it could  *
* be changed. Please confirm with IBM before the upgrade.      *
****************************************************************
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
20.12.2019
19.11.2020
19.11.2020
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)