Do you mean a
sudo user db_user, or a pseudo-user? The former has rules to execute commands with privileges of another account, where the latter is a pretend or non-personal account.
I'm just confused
If you want to login as
db_user, but then get it to run commands as
oracle, you will need to write a
sudo rule to allow that.
It could require the
db_user password or no password, but all actions will be attributed to the account
db_user.
Would it not be better to have people use a personal account and give them the privilege to run the required commands as account
oracle instead?
What sort of commands are you wanting to allow it to run? If it is to start/stop the database instance, this can be done during the boot/shutdown automatically which may be better all round.
Robin