UNIX: Connect AS SYSDBA / SYSOPER Privilege on Oracle RDBMS
(Doc ID 18089.1)
Last updated on FEBRUARY 01, 2022
Applies to:Oracle Database - Enterprise Edition - Version 18.104.22.168 and later
This article describes the database DBA 'CONNECT AS SYSDBA' functionality.
In Oracle RDBMS there are some special classes of user with privilege to perform special operations (such as shutdown and startup) on the database:
- A DBA user (SYSDBA)
- An OPERATOR user (SYSOPER)
For the remainder of this article, the examples that refer to SYSDBA also apply to SYSOPER, the SYSOPER privilege is more restricted.
For details of SYSDBA and SYSOPER see <Note 50507.1>, <Note 109891.1>
This article discusses 'CONNECT AS SYSDBA' and the issues that determine if a user has permission to connect as a privileged user or not. The details here apply to current releases 9.2 through to 11.2. The formerly known 'connect internal' syntax was desupported as of alert <Note 50508.1> but you may occasionally find references to it in our knowledge base, in that case substitute the 'connect internal' with 'connect / as sysdba' and it will likely work also.
To view full details, sign in with your My Oracle Support account.
Don't have a My Oracle Support account? Click to get started!