[Translated from mos] When OGG adds Supplemental Logging, the error message is Block Corruption and mossupplemental.

[Translated from mos] When OGG adds Supplemental Logging, the error message is Block Corruption and mossupplemental.

OGG add Supplemental Logging fails, and Block Corruption is reported)
Source:
Add Supplemental Logging Fails Due To Block upload uption (Document ID 1468322.1)

Applicable:
Oracle Server-Enterprise Edition-Version 10.2.0.5 to 12cBETA1 [Release 10.2 to 12.1]
Information in this document applies to any platform.

Symptoms:
In the GoldenGate environment, GoldenGate is based on supplemental logging.

Suddenly you find that supplemental logging is not set, and then you try to enable supplemental logging, but failed. The error is as follows:

 SQL> alter database add supplemental log data; ERROR at line 1: ORA-01578: ORACLE data block corrupted (file # 234, block #3760863) ORA-01110: data file 1257:'+CRMDB01/oradata/prdcrmdb/loy119.dbf'

 
Changes:
Control File rebuilt
 
Cause:
When you recreate the control file, supplemental logging is set to the default value, that is, none
When you try to manually enable supplemental logging, oracle checks whether there is active transaction,
Oracle will wait for these active transactions to be completed, and oracle will also check the involved objects
If the objects involved by active transaction has a bad partition, add supplemental logging will fail.
 
Solution:
Whenever you need to recreate the control file, you need to add the following line to the control file creation script:

 ALTER DATABASE ADD SUPPLEMENTAL LOG DATA;

When you manually add supplemental logging and the objects involved in active transaction has bad blocks, add supplemental logging reports an error: ora-1578
You must first remove the Bad blocks and then add the supplemental logging.

Note: From this mos document, I realized the potential role of this mos article:
1. A block upt check method was found, although this method is a bit tricky.
The application scenarios of this method are limited:

A. Use OGG (when alter database add supplemental log data is performed) B. The objects involved in active transaction C. active transaction are damaged. The above three ABC points must be met at the same time before the bad block can be checked)

2. When implementing OGG at the customer's site, this situation may occur, so some people may say: You see, OGG has broken the Oracle database block into upt.
In this case, you can move out of this mos article to rescue the drive-OGG will not cause bad blocks in the Oracle database. On the contrary, the alter database add supplemental log data of OGG will check whether the objects involved in active transaction have bad blocks.