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 IT33954 Status: Closed

SQL0206N OR SQL0901N ON STANDBY AFTER ALTER TABLE ADD COLUMN ON PRIMARY
WHEN HADR IS STOPPED

product:
DB2 FOR LUW / DB2FORLUW / B10 - DB2
Problem description:
This problem only happens when
DB2_HADR_ROS_AVOID_REPLAY_ONLY_WINDOW=ON.

Alter table adding a column after stopping HADR on primary,
select the table including the newly added column may return
SQL0206N or SQL0901N error  on standby.

To reproduce:

== primary ==
db2 connect to sample
db2 "Drop table test2"
db2 "create table test2 like employee"
db2 "insert into test2 select * from employee"

== standby ==
db2 connect to sample
db2 "select * from test2"

== primary ==
db2 stop hadr on db sample
db2stop force
db2start
db2 connect to sample
db2 "alter table test2 add column c1 CHAR(8) not null with
default ''"

== primary ==
db2 terminate
db2 start hadr on db sample as primary

== standby ==
db2 connect to sample
db2 "select c1 from test2"   # -206 error
db2 "select * from test2"    # -901 error
Problem Summary:
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to DB2 11.1 Mod 4 Fix pack 7                          *
****************************************************************
Local Fix:
Don't stop HADR when altering the table, or deactivate/activate
the standby database to prevent the SQL0206N OR SQL0901N error.
Solution
Workaround
****************************************************************
* USERS AFFECTED:                                              *
* all                                                          *
****************************************************************
* PROBLEM DESCRIPTION:                                         *
* See Error Description                                        *
****************************************************************
* RECOMMENDATION:                                              *
* Update to DB2 11.1 Mod 4 Fix pack 7                          *
****************************************************************
Comment
Problem was first fixed in DB2 11.1 Mod 4 Fix pack 7
Timestamps
Date  - problem reported    :
Date  - problem closed      :
Date  - last modified       :
19.08.2020
02.12.2021
02.12.2021
Problem solved at the following versions (IBM BugInfos)
Problem solved according to the fixlist(s) of the following version(s)