Schema Compare produces inaccurate results where column changes has no effect. (4226545)

After deleting columns from a table in the Target Schema, when re-running the Schema Compare., it shows the same results as the first compare before deletion. It should show a different result after deleting columns.

Steps:
1. Connect to a 10.2 database
2. Create two new DBA users, I will refer to them as schema1 and schema2
3. In schema1, run the attached makeall.sql file to create tables
4. In schema2, run the attached Noaa_creq.sql to create tables and indexes
5. Open Schema Compare
6. Select Schema1 as the source and Schema2 as target
7. Uncheck everything under Options, except for Indexes, Grants and Tables
8. Run the Compare
9. Notice that results show 48 columns only in Schema1
10. Keep the compare open and go back to Schema2
11. In Schema2, select VENDOR table and remove the last two columns: TRANS_PARTNER and COMMENTS. These column do exist in Schema1.
12. Re-run the compare and notice result still shows number of columns only in Schema1 remains to be 48
13. Under Options, uncheck Indexes and Grants, and re-run the compare. Notice the difference in column results which is now 58.
14. Now, switch the Source and Target schema, so Schema2 is the target and Schema1 is the source and re-run the compare. Notice, now you see the missing columns that were just removed.

WORKAROUND:
Select Options | Misc Options tab and change “Stop when # of differences reaches…” field from 1000 to 10000.

STATUS:
Waiting for fix in a future release of Toad for Oracle.