Grant Read is ignored as it is not supported in Oracle 11g.
Ordering issue -→ Checked in the fix to properly sequence drops and fix the Aggrandize issue.
After Karl's "fixing" of the Ordering issue, the testNestedTables Test fails.
Partial Deploy Grants - testing on fdglp01 now, but looks like it is working
Transforms aren't being dropped in the rebuild operation
testJava test is failing on 12c partial - it works on full. I almost got it on Partial, but not quite.
Drop check for Queue Tables is not complete.
In the FlexRunCompare, in runCompare after comparing queues and queue tables, a call to execute this query needs to be added. If any rows are returned, the sync operation should fail because it means a queue table is being attempted to be dropped without dropping all of the queues.
select a.owner, a.object_name from
(select d.owner, d.object_name, count(distinct q.name) as cnt from fddb.fd_baseline_diff d, fddb.fd_queues q
where
d.statement_type = 'DROP' and d.object_type = 'QUEUE_TABLE' and d.delta_ddl_id = 357480
and d.source_baseline_id = q.schema_version and d.owner = q.owner
and d.object_name = q.queue_table group by d.owner, d.object_name) a,
(select d1.owner, q1.queue_table, count(*) as cnt from fddb.fd_baseline_diff d1, fddb.fd_queues q1
where d1.source_baseline_id = q1.schema_version and
d1.statement_type = 'DROP' and d1.object_type = 'QUEUE' and d1.delta_ddl_id = 357480
group by d1.owner, q1.queue_table) b where
a.owner = b.owner and a.object_name = b.queue_table and a.cnt <> b.cnt;
Grants to objects other than Tables - should test them as well.
column object Column object grants or not baselined or deployed
Invalid Types are not baselined.
Queue support is added in this release. Queues bring their Queue Tables, Schedules, Subscribers, and grants with them.Transformations support is added in this release.
Queue Publishers are not supported.
Queue Agents are not supported.
Grants to objects that are renamed?
The new baseline will pickup the grants on the renamed object. I believe the issue may be that the compare will probably try to generate a revoke for the old object name which will fail because the object does not exist following the rename. If that is the case, the sql FDORA_DRCR_GRANTS.sql would need to have this section of the SQL updated as follows:
FULL OUTER JOIN
(SELECT owner, table_name, grantee FROM fddb.FD_TAB_PRIVS WHERE schema_version = :old
) OLD
to this:
FULL OUTER JOIN
(SELECT owner, table_name, grantee FROM fddb.FD_TAB_PRIVS WHERE schema_version = :old
and not exists (select 1 from fddb.fd_baseline_parameters b where p.schema_version = b.baseline_id
and b.parameter_name = 'RENAME' p.owner = b.schema and p.table_name = b.old_object_name
) OLD
removed Jobs from this release.
Transformations - These are counted as queues currently. Probably should add a new output for them. - I added a new output store for them, but I didn't put it in the plugin.xml and map it out. I can do that if we want to.
All customers will drop fddb schema and recreate itObject Tables are not supported at this time (example of this DDL: CREATE TABLE SCHEMA_NAME.TABLE_NAME OF SCHEMA_NAME.USER_DEFINED_TYPE ( CONSTRAINT PK_TABLENAME PRIMARY KEY (name)) OBJECT IDENTIFIER IS PRIMARY KEY;
It is necessary to drop the fddb schema and recreate it to upgrade from the 4.5 version. This is not necessary migrating from the 5.0 version or later. All prior builds will be in an unusable state, and shouldn't be reused.
...