TEST@orcl SQL> get sleep

  1  select to_char(sysdate,'hh24:mi:ss') from dual;

  2  exec dbms_lock.sleep(10);

  3* select to_char(sysdate,'hh24:mi:ss') from dual;

TEST@orcl SQL> @sleep



TO_CHAR(


20:06:08


PL/SQL procedure successfully completed.


TO_CHAR(


20:06:19



TEST@orcl SQL>                                                                    

Yes, you are supposing very good ...

And one more suggestion

What if Mr. Mohannad Ghawi (who created this thread) has users with restricted privileges (e.g. no rights on DBMS_LOCK)?
Then can happen following:

scott@XE> exec dbms_lock.sleep(10);
BEGIN dbms_lock.sleep(10); END;
 
      *
ERROR at line 1:
ORA-06550: line 1, column 7:
PLS-00201: identifier 'DBMS_LOCK' must be declared
ORA-06550: line 1, column 7:
PL/SQL: Statement ignored

if user_with_restricted_privs then
  own unsupported code, duplicate version of the Oracle functionality you have already paid for.
else
  using Oracle functionality you have already paid for
end if;

SYS@db102 SQL> create or replace procedure sleep (seconds in number)

  2  is

  3  begin

  4     dbms_lock.sleep (seconds);

  5  end;

  6  /



Procedure created.



SYS@db102 SQL> create or replace public synonym sleep for sleep;



Synonym created.



SYS@db102 SQL> grant execute on sleep to public;



Grant succeeded.



SYS@db102 SQL> create user test01 identified by test01;



User created.



SYS@db102 SQL> grant create session to test01;



Grant succeeded.



SYS@db102 SQL> conn test01/test01

Connected.

TEST01@db102 SQL> exec sleep(10);



PL/SQL procedure successfully completed.



TEST01@db102 SQL>