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 ALETER TABLE command waits indefinitely until user A ends the transaction

B.
The ALTER TABLE command modifies the column successfully

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

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

Show Hint

Leave a Reply 1

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

mauek

mauek

The DDL_LOCK_TIMEOUT parameter indicates the number of seconds a DDL command should wait for the locks to become available before throwing the resource busy error message.
User A has not COMMITed his update, therefore after 60 seconds (DDL_LOCK_TIMEOUT value from picture) command will fail.
C.

Reply