"Translated from MoS article" OGG add supplemental Logging failure, error is block damage (block corruption)

OGG Add supplemental Logging failure, error is block damage (block corruption)
From:
ADD Supplemental Logging fails Due to Block corruption (document ID 1468322.1)

Suitable for:
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 supplemental logging not set, then you try to open supplemental logging, but failed, 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/o RADATA/PRDCRMDB/LOY119.DBF '

Change:
The control file was rebuilt.

Reason:
When you rebuild the control file, the supplemental logging is set to the default value, which is: none
When attempting to manually enable supplemental logging, Oracle checks for active transaction,
Oracle waits for these active transaction to complete, while Oracle examines the objects involved
If the objects that is involved in active transaction has a bad block (corruption), then add supplemental logging will fail.

Solution:
Whenever you need to recreate the control file, you need to include the following line in the control file creation script:

ALTER DATABASE ADD supplemental LOG DATA;

When you add supplemental logging manually, and the active transaction involves a bad block of objects, add supplemental logging will error: ora-1578
You must first resolve the bad block and then add the supplemental logging.

Note: From this MOS document, I have realized the potential role of this MOS article:
1. A method for checking the block corrupt is found, although the method is somewhat astray.
The usage scenario for this method is limited:

     A. With Ogg (when you do ALTER DATABASE add supplemental log data)     B. There is a     corruption in the object involved in active transaction C. Active transaction. The     above ABC three must be met at the same time to check the bad block (corruption).

2. When Ogg is implemented at the customer's site, it is possible to encounter this situation, and some may say, "Look, Ogg has made a bad chunk of the Oracle database (block corrupt)."
At this point, you can move out of this MOS article rescue---OGG will not let the Oracle database bad block, instead: OGG's ALTER DATABASE add supplemental log data will check the active transaction involved in the object There are no bad blocks.

"Translated from MoS article" OGG add supplemental Logging failure, error is block damage (block corruption)