Which dependent object will get invalidated even if it is not affected by the table redefinition?
A.
packages
B.
triggers
C.
synonyms
D.
views
Explanation:
Results of the Redefinition Process
The following are the end results of the redefinition process:
The original table is redefined with the columns, indexes, constraints, grants, triggers, and statistics of the
interim table.
Dependent objects that were registered, either explicitly using REGISTER_DEPENDENT_OBJECT or implicitly
using COPY_TABLE_DEPENDENTS, are renamed automatically so that dependent object names on the
redefined table are the same as before redefinition.
Note:
If no registration is done or no automatic copying is done, then you must manually rename the dependent
objects.
The referential constraints involving the interim table now involve the redefined table and are enabled.
Any indexes, triggers, materialized view logs, grants, and constraints defined on the original table (prior to
redefinition) are transferred to the interim table and are dropped when the user drops the interim table. Any
referential constraints involving the original table before the redefinition now involve the interim table and are
disabled.
Some PL/SQL objects, views, synonyms, and other table-dependent objects may become invalidated. Only
those objects that depend on elements of the table that were changed are invalidated. For example, if a PL/
SQL procedure queries only columns of the redefined table that were unchanged by the redefinition, the
procedure remains valid. See “Managing Object Dependencies” for more information about schema object
dependencies.