If I don't 'set serveroutput on;' I don't see the error message, but it still fails.There you got it. Number one reason for not implemementing an exception handler, that does nothing.
wolfeet wrote:Solomon said to grant ALTER USER directly to user1, the owner of the procedure, who already has this privilege via a role.
Granting ALTER USER directly to the user defeats the whole purpose. I want to allow this user to reset user passwords and unlock user passwords but I don't want the user to be able to reset passwords for dba accounts, sys, system, yada yada. I was hoping I could do this via GRANT EXECUTE on a stored procedure.