Examine the following commands for redefining a table with Virtual Private Database (VPD) policies:
Which two statements are true about redefining the table?
A.
All the triggers for the table are disabled without changing any of the column names or column types in the
table.
B.
The primary key constraint on the EMPLOYEES table is disabled during redefinition.
C.
VPD policies are copied from the original table to the new table during online redefinition.
D.
You must copy the VPD policies manually from the original table to the new table during online redefinition.
Explanation:
C (not D): CONS_VPD_AUTO
Used to indicate to copy VPD policies automatically
* DBMS_RLS.ADD_POLICY
/ The DBMS_RLS package contains the fine-grained access control administrative interface, which is used to
implement Virtual Private Database (VPD).DBMS_RLS is available with the Enterprise Edition only.
Note:
* CONS_USE_PK and CONS_USE_ROWID are constants used as input to the “options_flag” parameter in
both the START_REDEF_TABLE Procedure and CAN_REDEF_TABLE Procedure. CONS_USE_ROWID is
used to indicate that the redefinition should be done using rowids while CONS_USE_PK implies that the
redefinition should be done using primary keys or pseudo-primary keys (which are unique keys with all
component columns having NOT NULL constraints).* DBMS_REDEFINITION.START_REDEF_TABLE
To achieve online redefinition, incrementally maintainable local materialized views are used. These logs keep
track of the changes to the master tables and are used by the materialized views during refresh
synchronization.
* START_REDEF_TABLE Procedure
Prior to calling this procedure, you must manually create an empty interim table (in the same schema as the
table to be redefined) with the desired attributes of the post-redefinition table, and then call this procedure to
initiate the redefinition.