It is generally a better idea to have control of who knows the oracle password than relying on regular system login to gain privileged access. The idea is common for Windows systems or legacy Telnet access, but obsolete for encrypted ssh logins.
[dude@vm210 ~]$ ssh -X oracle@localhost [oracle@vm210 ~]$
I think there are assumptions being made that are incorrect. First and foremost, this is an Oracle Linux question, and not a database question.Sorry but if you compare your last response with my previous response than my suggestion and assessment based on your input is not far from your real situation. ;-)
PeteNelson wrote:You have to run the OUI as oracle, however...
According to my DBA, we must run OUI as "oracle" (if this is NOT the case, that would be extremely useful to know!).
If they try "sudo -u oracle /u04/DL/Disk1/runInstaller", this does not work, since "oracle" doesn't have the xauth to write back to the display. Are there any options that would work?First option: teach your DBAs to use the OUI in silent/non-graphical mode.
That would be perfect! I did not know this was an option, but if so, it would be the perfect solution.