| shipon |
Posted: May 13, 2008 01:49:48 AM |
Total Post: 36
Joined: Feb, 2008
|
Dear Friends ,
I have a user : babu
I give the permission to babu like follwoing :
SQL> grant dba to babu;
Grant succeeded.
SQL> grant sysdba to babu;
Grant succeeded.
Now my question is ,
here 'dba' and 'sysdba' privileges are same or different ?
Plz explain me .. .. |
|
|
 http://shaharear.blogspot.com |
| Posted: May 13, 2008 03:03:06 AM |  |
|
Total Post: 79
Joined: Apr, 2008
|
SYSDBA and DBA are often misunderstood. In short, SYSDBA is a system privilege whereas DBA is a role.
The DBA role does not include the SYSDBA or SYSOPER system privileges. SYSDBA and SYSOPER are special administrative privileges that allow an administrator to perform basic database administration tasks, such as creating the database, instance startup and shutdown, drop a database, open and mount a database, place database in archivelog mode or remove it from archivelog mode.
About SYSDBA system privilege
The SYSDBA and SYSOPER system privileges allow access to a database instance even when the database is not open. Control of these privileges is totally outside of the database itself. The SYSDBA and SYSOPER privileges can also be thought of as types of connections that enable you to perform certain database operations for which privileges cannot be granted in any other fashion. For example, if you have the SYSDBA privilege, you can connect to the database by specifying CONNECT AS SYSDBA.
About DBA Role
A predefined role, named "DBA", is automatically created with every Oracle database. This role contains all database system privileges but SYSDBA and SYSOPER are excluded. Therefore, it is very powerful and should be granted only to fully functional database administrators.
Query all roles that exist in the database:
|
|
|
|
|
| GOPU |
| Posted: May 13, 2008 04:47:13 AM | |
|
Total Post: 272
Joined: Apr, 2008
|
go through this link...
http://momendba.blogspot.com/2007/07/closer-look-at-sysdba-and-dba.html
|
|
|
|
|
| Gitesh |
| Posted: May 13, 2008 08:21:55 AM | |
|
Total Post: 322
Joined: May, 2005
|
Remember that SYSDBA you can grant if your remote_login_passwordfile is shared or exclusive. If it is NONE then you can't grant sysdba privilege or user can't able login as SYSDBA.
|
|
|
|
|
| Chandrasekharan |
| Posted: May 23, 2008 02:24:29 PM | |
|
Total Post: 7
Joined: Mar, 2007
|
Regarding DBA and SYSDBA, a bit more explanation here.
The above blogspot says
'The SYSDBA and SYSOPER system privileges allow access to a database instance even when the database is not open.'
That means even when the Database is sleeping in the files,he have some
protection given through a lock !
SYSDBA and SYSOPER are privileges given to Privileged Operating System
users in different flavours of UNIX .Most of the time SYSDBA is enjoyed by
the super user 'root' to our knowledge but can be given to a user who is
less powerful,but with sufficient OS rights assigned.These users will be
a member of the DBA group or OPER group as whatever the case may be.
Oracle privileges are not above to that of OS privileges.Making member of
a group means delegating some rights of
|
|
|
|
|
| Time Zone: EDT |
Send this thread to your friend |
