You have two tables with referential integrity enforced between them. You need to insert data to the child table first because it is going to be a long transaction and data for the parent table will be available in a later stage, which can be inserted as part of the same transaction. View the Exhibit to examine the commands used to create tables. Which action would you take to delay the referential integrity checking until the end of the transaction?

Question

Accepted Answer

A. Set the constraint to deferred before starting the transaction The SET CONSTRAINT ... DEFERRED command instructs Oracle to postpone referential integrity checking until COMMIT, allowing child rows to be inserted before their parent rows within the same transaction, provided the constraint was originally created with the DEFERRABLE clause.

Answer

B. Alter the constraint to NOVALIDATE state before starting the transaction The NOVALIDATE state exempts existing rows from validation but still enforces the constraint immediately for new DML operations - it does not defer checking to end of transaction.

Answer

C. Enable the resumable mode for the session before starting the transaction Resumable mode suspends a statement when it encounters a resource shortage such as out-of-space conditions, and has no effect on constraint enforcement timing.

Answer

D. Set the COMMIT_WAIT parameter to FORCE_WAIT for the session before starting the transaction The COMMIT_WAIT parameter controls whether a commit waits for redo data to be flushed to disk before returning to the caller, and is completely unrelated to constraint checking behavior.

You have two tables with referential integrity enforced between them. You need to insert data to the child table first because it is going to be a long transaction and data for the parent table will…

Question

Exhibit

Options

How the community answered

Why each option

Topics

Community Discussion