1, sys and system user differences
The system user can only log on em with normal status.
SYS user has "SYSDBA" or "sysoper" permission, landing em can only use these two identities, can not use normal.
"Sysoper" permissions, which are database operator permissions, include:
Open the database server shut down the database server
Backing up the database recovery database
Log Archive Session Limit
"SYSDBA" permissions, which are database administrator permissions, include:
Open the database server shut down the database server
Backing up the database recovery database
Log Archive Session Limit
Manage features Create a database
2, Normal, SYSDBA, Sysoper difference
Normal: is a normal user and can operate on a database only after being authorized by SYS
SYSDBA: Has the highest system privileges
Sysoper: Mainly used to start and close the database, sysoper the user is public after landing
SYSDBA: Is sys after landing, and can only be the sys login SYSDBA.
Sql> Conn/as SYSDBA
is connected.
Sql> Grant Sysoper to test;
The authorization was successful.
Sql> Conn Test/test as Sysoper;
is connected.
Sql> Show User
USER is "public"
Sql> Conn Test/test as Sysdba
is connected.
Sql> Show User
USER is "SYS"
Sql>
3, the difference between DBA and SYSDBA
DBA, Sysdba What's the difference between the two system roles, before I explain this, I need to talk about the Oracle service creation process
• Create an instance
• Startup instance
• Create a database (System tablespace is required)
startup process
• Instance Startup
• Loading Databases
• Open Database
SYSDBA, which manages the Oracle instance, does not depend on the entire database to be fully booted,
As long as the instance is started, it already exists, log in as SYSDBA, mount the database, open the database
Only if the database is open, or when the entire database is fully booted, the DBA role has a foundation, and the DBA is just a role.
See more highlights of this column: http://www.bianceng.cnhttp://www.bianceng.cn/database/Oracle/