Zd wrote:

>
>
> Now the user can't read or modify any data, but it can see
> database metadata! The biggest problem is that the new user
> sees the code of my stored procedure, which has the SYSDBA
> password built-in!
>
> So the question is:
> How do I revoke the new user's rights to see database metadata?
>

You can't. By design, all aspects of the user's access to the
database is done with the access rights gained on login. If
the user couldn't read the metadata, no queries could be compiled.

However, you can delete the source of your procedure and keep
only the "blr" format of it which is harder to read. But
basically, storing the sysdba password in the database is not
clever. There's a good paper on securing metadata which I
can't find at the moment. I'm sure someone will post a link
to it.

Best