Our QA department will need proof to show that the exported Oracle 11 data is the same when imported to Oracle 12 due to the strict GMP regulations that we need to be compliant with as pharmaceutical production facility.
As the Oracle database is part of software from a vendor we don’t do any development with Oracle. We only need the Oracle data compare tool for making sure that with the upgrade of software, the Oracle 11 data is the same as the imported data in Oracle 12 (before the new software will be installed).
The Oracle compare tool has a main focus on developers, but we need it as QA compliant compare tool.

A minor issue is when a table only has 1 column and that column is data type “Blob” than it is not able to compare (as also no comparison key can be set).

Redgate's standpoint:
For Data Compare for Oracle to be able to compare rows of data in tables it requires a comparison key so it can unique identify each row. In regards to 'BLOB' and 'CLOB' data, the size of data for a single row can be ridiculously large in size, therefore it is not good idea to use 'BLOB' and 'CLOB' data column as a comparison key. Hence why you cannot use 'BLOB' and 'CLOB' columns as the comparison key.

To make the Redgate tool QA and GMP compliant we wish to see these types of tables also to be comparable without the need of a comparison key (and maybe a special licensed version without all the great developer tools/options as we will not use those in this case).