I have been seeing more of this lately.
Developers running application installs, SIEBEL, Oracle clinical etc, need to have the install run as the user SYS.
Apparently the new application user being created needs certain read privileges on SYS owned tables.
What I have been doing is one of two things
1) When the developers run the install, I walk over and enter the SYS password myself on the pertinent application install screen. This way I don't have to share the password with them.
2) reset the SYS password and provide the temporary password to the developers during installation.
I am curious how other DBA's are handling this?
Hi,This application has to run only the user sys? Otherwise, you can created a user and to do grant of DBA for it, Now, your explanation is very well. I don't know others solutions.
Kind regards, Bruno Reis.