I think the DDL generated by the compare user objects isn't quite correct for partitioned objects.
1) It includes storage info for the partitions, but not at the object level. I think this means that new table partitions will be created in the user's default tablespace, which may not be what's intended.
2) It seems to omit all storage and partitioning info for local indexes on a partitioned table. In fact, it doesn't even specify LOCAL - you end up with a global index in your default tablespace. (It looks like indexes on non-partitioned tables are handled correctly).
Happy new year!
Dave Curley
1) It includes storage info for the partitions, but not at the object level. I think this means that new table partitions will be created in the user's default tablespace, which may not be what's intended.
2) It seems to omit all storage and partitioning info for local indexes on a partitioned table. In fact, it doesn't even specify LOCAL - you end up with a global index in your default tablespace. (It looks like indexes on non-partitioned tables are handled correctly).
Happy new year!
Dave Curley
