What would happen in this scenario?

View the Exhibit and examine the parameters. User A executes the following command to update
the TRANS table:
SQL> UPDATE B.trans SET tr_amt=tr_amt+500 WHERE c_code=’C005′;
Before user A issues a COMMIT or ROLLBACK command, user B executes the following command on
the TRANS table:
SQL> ALTER TABLE trans MODIFY (tr_type VARCHAR2(3));
What would happen in this scenario?

View the Exhibit and examine the parameters. User A executes the following command to update
the TRANS table:
SQL> UPDATE B.trans SET tr_amt=tr_amt+500 WHERE c_code=’C005′;
Before user A issues a COMMIT or ROLLBACK command, user B executes the following command on
the TRANS table:
SQL> ALTER TABLE trans MODIFY (tr_type VARCHAR2(3));
What would happen in this scenario?

A.
The ALTER TABLE command modifies the column successfully

B.
The DDL operation gets higher priority and transaction for user A is rolled back

C.
The ALETER TABLE command waits indefinitely until user A ends the transaction

D.
The ALTER TABLE command fails after waiting for 60 seconds due to the resource being busy

Show Hint

Leave a Reply 2

Your email address will not be published. Required fields are marked *

Prince

Prince

Exhibit not showing

Reply

jean

jean

DDL_LOCK_TIMEOUT specifies a time limit for how long DDL statements will wait in a DML lock queue. The default value of zero indicates a status of NOWAIT. The maximum value of 1,000,000 seconds will result in the DDL statement waiting forever to acquire a DML lock.

If a lock is not acquired before the timeout period expires, then an error is returned.

Reply