As the purpose of the user is essentially to allow database users to execute external jobs, you should not use the oracle user. The oracle user is a powerful user; obviously they can shut down the database, and have access to a number of resources, oracle and otherwise. You would not want to give any database user with privileges to schedule this job (actually create external job privs.) the ability to perform all oracle actions; at least not in a normal environment. For security purposes, it is best to create a user with minimum privileges required to do the job. For example, if it reads from a specific directory, give them access to that directory, but not to the oracle binaries directory.
The need for the low privilege user is simply a security measure. The term unprivileged user, in many contexts, is used to refer to a non-DBA user; it's a general term for a non super user.
The need for the low privilege user is simply a security measure. The term unprivileged user, in many contexts, is used to refer to a non-DBA user; it's a general term for a non super user.
来自 “ ITPUB博客 ” ，链接：http://blog.itpub.net/26474945/viewspace-1364776/，如需转载，请注明出处，否则将追究法律责任。
转载于:http://blog.itpub.net/26474945/viewspace-1364776/
扫一扫
235
被折叠的 条评论
为什么被折叠?
到【灌水乐园】发言
