I would think that if I wanted to exclude an object from one schema's sync script, but include an object with the same name and type in another schema's sync script, this cumulative exclusion file wouldn't work.
That's true. In that case, you could work around it by making more than one schema compare action and assigning those files as needed.
The read-only table attribute for partitioned read/write tables has changed from 11g (NO) to 12c (N/A). The compare is showing this as a difference.
If the table is set to read-only, 12c shows YES, same as 11g.
Thanks Dale. Fixed. Starting in 12cR2, read only can be set at the partition level, so NO changed to N/A at the table level for partitioned tables.
I thought I replied to this earlier but don’t see it now. This is fixed for next beta.