This topic contains information on what Administrative Privileges you can use when connecting to the Oracle server.
Some administrative actions may require connecting as SYSDBA or SYSOPER. SYS or SYSTEM users can connect only as SYSDBA or SYSOPER.
Note
To connect as SYSDBA or SYSOPER, you must have SYSDBA or SYSOPER system privilege. These privileges are not included in the DBA role.
To connect as SYSDBA or SYSOPER, you need to select SYSDBA or SYSOPER in the Connect as box of the general tab of the Connection Properties dialog box when adding or modifying a connection.
Connecting as SYSDBA or SYSOPER enables you to perform certain database operations for which privileges cannot be granted in any other fashion.
Connecting as SYSDBA allows you to perform the following operations:
When you connect as SYSDBA, you also have RESTRICTED SESSION privilege.
Connecting as SYSOPER allows you to perform the following operations:
When you connect as SYSOPER, you also have RESTRICTED SESSION privilege. Connecting as SYSOPER allows a user to perform basic operational tasks, but without the ability to look at user data.
This privilege allows a user to perform backup and recovery operations either from Oracle Recovery Manager (RMAN) or SQL*Plus.
The privilege enables you to perform the following operations:
In addition, the SYSBACKUP privilege enables you to connect to the database even if the database is not open.
Connect with the SYSDG administrative privilege to perform the Data Guard operations.
The SYSDG privilege enables the following operations:
In addition, the SYSDG privilege enables you to connect to the database even if it is not open.
The SYSKM administrative privilege enables the SYSKM user to manage the Transparent Data Encryption wallet operations.
The SYSKM administrative privilege enables the following operations:
In addition, the SYSKM privilege enables you to connect to the database even if it is not open.