Doubt with DMBS_LOCK.SLEEP

Question

Hi, I'using this code in a program unit of a Form:
DBMS_LOCK.SLEEP(p_seconds);
The purpose os this is, obviously, to delay the execution of the program in 'p_seconds' seconds.
My problem is that DBA doesn't want to grant execute permission on DBMS_LOCK (full package) to the application user. I've read that a possible solution could be to create a new wrapper procedure that calls DBMS_LOCK.SLEEP and to grant permission only to this procedure. That's right, but I want to avoid creating new objects in SYS schema.
I've found another solution, this is to create a new procedure in the application user, called 'LOCALSLEEP', and this is its code:
PROCEDURE LOCALSLEEP (i_nMilliseconds in number)
as language java name 'java.lang.Thread.sleep(long)';
So, in my Form, I could use this call instead of previous:
LOCALSLEEP(p_seconds*1000);
My question is: Is this solution fully the same as the other ? Can this function to be created in any Oracle database, or it depends on Java, or need to configure anything else ?
Thanks a lot by your help.

Answer 1

vbarres wrote:
Hi, I'using this code in a program unit of a Form:
DBMS_LOCK.SLEEP(p_seconds);
The purpose os this is, obviously, to delay the execution of the program in 'p_seconds' seconds.
My problem is that DBA doesn't want to grant execute permission on DBMS_LOCK (full package) to the application user. I've read that a possible solution could be to create a new wrapper procedure that calls DBMS_LOCK.SLEEP and to grant permission only to this procedure. That's right, but I want to avoid creating new objects in SYS schema.Why create it in the SYS schema?
Just create it within a pre-defined user schema and grant execute permissions to public (or all the users that require it).
Then, only this pre-defined user schema will require execute permissions on DBMS_LOCK, and can have the rest of it's permissions restricted so it's limited to only do what you require.