ORA-26786 on the Logical Standby after adding a Column NOT NULL and Defaults value hours later
edited Feb 19, 2013 1:33PM in High Availability Data Guard, Sharding and Global Data Services (MOSC) 3 commentsAnswered ✓
I added a column DB_INSERT_DATE to several Tables on the Data Guard Primary database at 9:09AM. At 12:40PM, the Logical Standby abends with this on a delete statement.
the column is DB_INSERT_DATE DATE not null default sysdate
I notice MOS doc 1529239.1 and BUG 1430552.
So how will add the columns to my large production database and not repeat this error when 1,000's of transactions are taking place?
----- Error Stack Dump -----
ORA-26808: Apply process AS02 died unexpectedly.
ORA-26786: A row with key ("PROFILE_TYPE", "ID") = (W, 08a19842d235) exists but has conflicting column(s) "DB_INSERT_DATE" in table xxxxxxx.CUSTOMER_PROFILE_TB
0