Oracle ALTER TABLE ...NOPARALLEL NOCACHE

In some circumstances, during a Compare and Merge for Oracle where an ALTER TABLE statement is generated (for example, adding a new column), ER Studio generates an ALTER TABLE with NOPARALLEL NOCACHE before the actual change to the table.  I think it may have to do with whether a table is partitioned or not, but does anyone have any insight into what the circumstances are under which this DDL statement is generated and why?

DDL Example:


-- Standard Alter Table SQL

ALTER TABLE MYSCHEMA.MY_TABLE NOPARALLEL NOCACHE
/
ALTER TABLE MYSCHEMA.MY_TABLE ADD MY_NEW_COLUMN VARCHAR2(10) NULL
/

  • Think I found the answer to my question. The NOPARALLEL NOCACHE statement will be generated from Compare and Merge if you choose the Storage Parameters option (under Table) even if there are no changes to storage parameters for the table. When the Storage Parameters option is unchecked, the statement is not generated.