This example illustrates that a user is assigned another schema (SYS) when connecting
with the SYSDBA system privilege. Assume that the sample user oe has been granted
the SYSDBA system privilege and has issued the following statements:
CONNECT oe/oe
CREATE TABLE admin_test(name VARCHAR2(20));
Later, user oe issues these statements:
CONNECT oe/oe AS SYSDBA
SELECT * FROM admin_test;
User oe now receives the following error:
ORA-00942: table or view does not exist
Having connected as SYSDBA, user oe now references the SYS schema, but the table
was created in the oe schema.
以系统管理权限登录实例
某用户拥有sysdba权限 , 当使用conn username/password as sysdba后 , 此时的方案对象为sys
[@more@]来自 “ ITPUB博客 ” ,链接:http://blog.itpub.net/10599713/viewspace-994745/,如需转载,请注明出处,否则将追究法律责任。
转载于:http://blog.itpub.net/10599713/viewspace-994745/
本文通过示例展示了在Oracle数据库中,当用户使用SYSDBA权限连接时,默认使用SYS模式进行操作的情况。若在此模式下访问其他用户创建的对象,可能会遇到权限或对象不存在的问题。
1297

被折叠的 条评论
为什么被折叠?



