What happens in the above scenario?

View the Exhibit for some of the current parameter settings. A user logs in to the HR
schema and issues the following commands: SQL> CREATE TABLE emp (empno
NUMBER(3), ename VARCHAR2(20), sal NUMBER(8,2)); SQL> INSERT INTO
emp(empno,ename) VALUES(1,’JAMES’); At this moment, a second user also logs in to the
HR schema and issues the following command: SQL> ALTER TABLE emp MODIFY sal
NUMBER(10,2); What happens in the above scenario?

View the Exhibit for some of the current parameter settings. A user logs in to the HR
schema and issues the following commands: SQL> CREATE TABLE emp (empno
NUMBER(3), ename VARCHAR2(20), sal NUMBER(8,2)); SQL> INSERT INTO
emp(empno,ename) VALUES(1,’JAMES’); At this moment, a second user also logs in to the
HR schema and issues the following command: SQL> ALTER TABLE emp MODIFY sal
NUMBER(10,2); What happens in the above scenario?

A.
The second user’s command executes successfully.

B.
The second user’s session immediately produces the resource busy error.

C.
A deadlock is created.

D.
The second user’s session waits for a time period before producing the resource busy
error.



Leave a Reply 0

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