TO GRANT SYSDBA

Hi,
I want to grant sysdba privilege to ops$ user. For that i have to set the remote_login_passwordfile parameter in the init<sid.ora file to EXCLUSIVE ryt..But as there is no such parameter in the file, i added up one. But still the parameter value is shown as NONE.
Can anyone please help me...
Regards
Dhanya

o/p of trans.log
4 ETW000 r3trans version 6.13 (release 640 - 25.07.06 - 17:34:00).
4 ETW000 ===============================================
4 ETW000
4 ETW000 date&time   : 01.08.2006 - 13:53:20
4 ETW000 control file: <no ctrlfile>
4 ETW000 R3trans was called as follows: r3trans -x
4 ETW000 trace at level 2 opened for a given file pointer
4 ETW000 [dev trc     ,00000] Tue Aug 01 13:53:22 2006                                  0.000000
4 ETW000 [dev trc     ,00000] db_con_init called                                        0.000000
4 ETW000 [dev trc     ,00000] create_con (con_name=R/3)                                 0.000000
4 ETW000 [dev trc     ,00000] Loading DB library 'dboraslib.dll' ...                    0.000000
4 ETW000 [dev trc     ,00000] load shared library (dboraslib.dll), hdl 0          6892 0.006892
4 ETW000 [dev trc     ,00000]      using "E:\usr\sap\SM3\SYS\exe\run\dboraslib.dll"
4 ETW000                                                                              27 0.006919
4 ETW000 [dev trc     ,00000] Library 'dboraslib.dll' loaded                        13 0.006932
4 ETW000 [dev trc     ,00000] function DbSlExpFuns loaded from library dboraslib.dll
4 ETW000                                                                              19 0.006951
4 ETW000 [dev trc     ,00000] Version of 'dboraslib.dll' is "640.00", patchlevel (0.142)
4 ETW000                                                                             131 0.007082
4 ETW000 [dev trc     ,00000] function dsql_db_init loaded from library dboraslib.dll
4 ETW000                                                                              19 0.007101
4 ETW000 [dev trc     ,00000] function dbdd_exp_funs loaded from library dboraslib.dll
4 ETW000                                                                              32 0.007133
4 ETW000 [dev trc     ,00000] New connection 0 created                              21 0.007154
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = -000000001 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              26 0.007180
4 ETW000 [dev trc     ,00000] db_con_connect (con_name=R/3)                         17 0.007197
4 ETW000 [dev trc     ,00000] find_con_by_name found the following connection for reuse:
4 ETW000                                                                              18 0.007215
4 ETW000 [dev trc     ,00000] 0: name = R/3, con_id = 000000000 state = DISCONNECTED, perm = YES, reco = NO , timeout = 000, con_max = 255, con_opt = 255, occ = NO
4 ETW000                                                                              21 0.007236
4 ETW000 [dev trc     ,00000] Setting DIR_CLIENT_ORAHOME is not set as environment variable,
4 ETW000                        assuming using instant client with unspecified location.
4 ETW000                                                                             192 0.007428
4 ETW000 [dev trc     ,00000] -->oci_initialize (con_hdl=0)                        131 0.007559
4 ETW000 [dev trc     ,00000] got NLS_LANG='AMERICAN_AMERICA.WE8DEC' from environment
4 ETW000                                                                              22 0.007581
4 ETW000 [dev trc     ,00000] Client NLS settings: AMERICAN_AMERICA.WE8DEC       18591 0.026172
4 ETW000 [dev trc     ,00000] Logon as OPS$-user to get SAPSOL's password           24 0.026196
4 ETW000 [dev trc     ,00000] Connecting as /@SM3 on connection 0 (nls_hdl 0) ... (dbsl 640 110706)
4 ETW000                                                                              26 0.026222
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              22 0.026244
4 ETW000 [dev trc     ,00000]    0 WE8DEC                                                    1   026DEC20   026E3C88   026E36F0
4 ETW000                                                                              89 0.026333
4 ETW000 [dev trc     ,00000] Allocating service context handle for con_hdl=0       26 0.026359
4 ETW000 [dev trc     ,00000] Allocating server context handle                      17 0.026376
4 ETW000 [dev trc     ,00000] Attaching to DB Server SM3 (con_hdl=0,svchp=026E3644,svrhp=0037BCFC)
4 ETW000                                                                              46 0.026422
4 ETW000 [dev trc     ,00000] Assigning server context 0037BCFC to service context 026E3644
4 ETW000                                                                           24761 0.051183
4 ETW000 [dev trc     ,00000] Allocating user session handle                        41 0.051224
4 ETW000 [dev trc     ,00000] Starting user session (con_hdl=0,svchp=026E3644,srvhp=0037BCFC,usrhp=026E90F0)
4 ETW000                                                                              32 0.051256
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000                                                                            4053 0.055309
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000                                                                              25 0.055334
4 ETW000 [dev trc     ,00000] Try to connect with default password                  20 0.055354
4 ETW000 [dev trc     ,00000] Connecting as SAPSOL/<pwd>@SM3 on connection 0 (nls_hdl 0) ... (dbsl 640 110706)
4 ETW000                                                                              21 0.055375
4 ETW000 [dev trc     ,00000] Nls CharacterSet                 NationalCharSet              C      EnvHp      ErrHp ErrHpBatch
4 ETW000                                                                              20 0.055395
4 ETW000 [dev trc     ,00000]    0 WE8DEC                                                    1   026DEC20   026E3C88   026E36F0
4 ETW000                                                                              20 0.055415
4 ETW000 [dev trc     ,00000] Assigning username to user session 026E90F0           14 0.055429
4 ETW000 [dev trc     ,00000] Assigning password to user session 026E90F0           20 0.055449
4 ETW000 [dev trc     ,00000] Starting user session (con_hdl=0,svchp=026E3644,srvhp=0037BCFC,usrhp=026E90F0)
4 ETW000                                                                              24 0.055473
4 ETW000 [dboci.c     ,00000] *** ERROR => OCI-call 'OCISessionBegin' failed: rc = 1017
4 ETW000                                                                            3579 0.059052
4 ETW000 [dbsloci.    ,00000] *** ERROR => CONNECT failed with sql error '1017'
4 ETW000                                                                              23 0.059075
4 ETW000 [dblink      ,00419] ***LOG BY2=>sql error 1017   performing CON [dblink#2 @ 419]
4 ETW000                                                                              53 0.059128
4 ETW000 [dblink      ,00419] ***LOG BY0=>ORA-01017: invalid username/password; logon denied [dblink#2 @ 419]
4 ETW000                                                                              19 0.059147
2EETW169 no connect possible: "DBMS = ORACLE                           --- dbs_ora_tnsname = 'SM3'"
and the query returned:
USERNAME
DBSNMP
OPS$SOLADM
OPS$SOLMAN\SAPSERVI
OPS$SOLMAN\SOLADM
OUTLN
SAPSOL
SYS
SYSTEM
8 rows selected.
this is a local installation...

Similar Messages

Unable to grant sysdba to user

Hi,
On my PC i am using Redhat 5. when I grant sysdba privilege to user hr it gives an error.
SQL> grant sysdba to hr;
grant sysdba to hr
ERROR at line 1:
ORA-01994: GRANT failed: password file missing or disabled
I check the password file is in place in the folder HOME/dbs. what can be the problem.
Plz help
Thanx

It works for me.
bcm@bcm-laptop:~$ sqlplus
SQL*Plus: Release 11.2.0.1.0 Production on Mon Nov 1 10:39:30 2010
Copyright (c) 1982, 2009, Oracle. All rights reserved.
Enter user-name: / as sysdba
Connected to:
Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
With the Partitioning, OLAP, Data Mining and Real Application Testing options
SQL> grant sysdba to hr;
Grant succeeded.Either you are mistaken or Oracle is.
Either you have an error of omission or error of commission, but without knowing what you have & what you do, no advice is possible.
Is COPY & PASTE broken for you?
Post results of
SELECT * from v$version;

Two instances installation, grant sysdba failed because passwd file

Hi
I have a two instances Oracle 11g installation.
Instance 1: ORATEST
Instance 2: ORADESA
So, i want add SYSDBA grant to ORADESA system user.
[oracle@oracletesting dbs]$ echo $ORACLE_SID
ORADESA
[oracle@oracletesting dbs]$ echo $ORACLE_HOME
/u01/app/oracle/product/11.2.0.3/desa/dbhome_1
[oracle@oracletesting dbs]$ sqlplus /nolog
SQL> conn /as sysdba
Connected.
SQL> show parameter password;
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
SQL> grant sysdba to system;
grant sysdba to system
ERROR at line 1:
ORA-01994: GRANT failed: password file missing or disabled
Ok, i recreate passwd file.
[oracle@oracletesting dbs]$ rm $ORACLE_HOME/dbs/orapworaDESA
[oracle@oracletesting dbs]$ orapwd file=$ORACLE_HOME/dbs/orapworaDESA password=xxx entries=5
[oracle@oracletesting dbs]$ ls -all
total 84
drwxr-xr-x. 2 oracle oinstall 4096 Mar 28 10:57 .
drwxr-xr-x. 71 oracle oinstall 4096 Mar 7 16:23 ..
-rw-rw----. 1 oracle oinstall 1544 Mar 26 15:45 hc_oradesa.dat
-rw-rw----. 1 oracle oinstall 1544 Mar 28 10:20 hc_ORADESA.dat
-rw-r--r--. 1 oracle oinstall 2851 May 15 2009 init.ora
-rw-r--r--. 1 oracle oinstall 68 Mar 26 15:45 initORADESA.ora
-rw-r-----. 1 oracle oinstall 24 Mar 26 11:17 lkORADESA
-rw-r-----. 1 oracle oinstall 2048 Mar 28 10:57 orapworaDESA
-rw-r--r--. 1 oracle oinstall 48880 Mar 26 14:15 rmdup_oradesa.dat
-rw-r-----. 1 oracle oinstall 3584 Mar 26 15:14 spfileoradesa.ora
[oracle@oracletesting dbs]$ sqlplus /nolog
SQL*Plus: Release 11.2.0.3.0 Production on Thu Mar 28 10:59:54 2013
Copyright (c) 1982, 2011, Oracle. All rights reserved.
SQL> conn /as sysdba
Connected.
SQL> grant sysdba to system;
grant sysdba to system
ERROR at line 1:
ORA-01994: GRANT failed: password file missing or disabled
Obviously something is wrong, but I do not know.
Thanks

[oracle@oracletesting dbs]$ rm $ORACLE_HOME/dbs/orapworaDESA
[oracle@oracletesting dbs]$ orapwd file=$ORACLE_HOME/dbs/orapworaDESA password=xxx entries=5
[oracle@oracletesting dbs]$ ls -all
total 84
drwxr-xr-x. 2 oracle oinstall 4096 Mar 28 10:57 .
drwxr-xr-x. 71 oracle oinstall 4096 Mar 7 16:23 ..
-rw-rw----. 1 oracle oinstall 1544 Mar 26 15:45 hc_oradesa.dat
-rw-rw----. 1 oracle oinstall 1544 Mar 28 10:20 hc_ORADESA.dat
-rw-r--r--. 1 oracle oinstall 2851 May 15 2009 init.ora
-rw-r--r--. 1 oracle oinstall 68 Mar 26 15:45 initORADESA.ora
-rw-r-----. 1 oracle oinstall 24 Mar 26 11:17 lkORADESA
-rw-r-----. 1 oracle oinstall 2048 Mar 28 10:57 orapworaDESA
-rw-r--r--. 1 oracle oinstall 48880 Mar 26 14:15 _rm_dup_oradesa.dat
-rw-r-----. 1 oracle oinstall 3584 Mar 26 15:14 spfileoradesa.oraYour password file format is wrong. It should be "orapwSID" and yours is "orapworaSID" which is wrong.
Thanks,
Navneet

Grant sysdba to rmanuser did not work but later worked.Need explnatn pls...

Hi Members,
I'm running a test 9i RAC. I'm trying to setup RMAN to backup data from RAC. One of the requirements to setup RMAN recovery catalog (database) is to grant/create a user on target database with sysdba privileges. Hence i created a user named 'RMANUSER' with default tablespace users and temporary tablespace temp.
When I try to grant sysdba to RMANUSER, it says granted but when i check v$pwfile_users, RMANUSER is not listed.
instance connected to is orcl1:
conn sys/pwd@orcl as sysdba
SQL> show parameters remote_login
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
SQL> grant sysdba to rmanuser;
Grant succeeded.
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP
SYS TRUE TRUE
I tried the above even on orcl2 with no result. I read somewhere that I need to create a new password file with orapwd and hence i created new password file on both instances.
on orcl1:
orapwd file=/opt/oracle/product/9.2.0/dbs/orapworcl1 pwd=password entries=5
on orcl2:
orapwd file=/opt/oracle/product/9.2.0/dbs/orapworcl2 pwd=password entries=5
The good thing is I renamed the old files and created new orapw files.
After creation of new files, When I try to grant sysdba to rmanuser, I received the following error: ORA-01999:password file mode has changed from 'exclusive' to 'shared'
But show parameters remote_login was still "exclusive"
SQL> show parameters remote_login
NAME TYPE VALUE
remote_login_passwordfile string EXCLUSIVE
Now, there were no users in v$pwfile_users
SQL> select * from v$pwfile_users;
no rows selected
Also I was unable to connect to sys with sysdba privileges. I was only able to connect without sysdba.
SQL> conn sys/oracle@orcl
Connected.
SQL> conn sys/oracle@orcl as sysdba
ORA-01031: insufficient privileges
SQL> conn sys/oracle@orcl
Connected.
SQL> shutdown immediate
ORA-01031: insufficient privileges
I was also unable to shutdown the database. Hence I reverted back to the old orapw files on both instances(servers). Then I just tried if the grant sysdba to rmanuser would work, and luckily it worked.
SQL> grant sysdba to rmanuser;
Grant succeeded.
SQL> select * from v$pwfile_users;
USERNAME SYSDB SYSOP
SYS TRUE TRUE
RMANUSER TRUE FALSE
But I'm unable to understand as to how it worked now. The orapw files are attached below for your reference. Any inputs are greatly appreciated. Thanks in advance. orapworcl1 is the old one which works now. orapworcl1-new was the newly created file which does not work and gives insufficient privileges error.
[root@sunny1pub ~]# cat /opt/oracle/product/9.2.0/dbs/orapworcl1
]\[ZORACLE Remote Password file ORCL INTERNAAB27B53EDC5FEF41 SYS 8A8F025737A9097A _�RMANUSED1C5D743B0B4A7F0
�
[root@sunny1pub ~]# cat /opt/oracle/product/9.2.0/dbs/orapworcl1-new
]\[ZORACLE Remote Password file INTERNAAB27B53EDC5FEF41 SYS 8A8F025737A9097A
[root@sunny1pub ~]#

Thanks for your feedback. I think you got me wrong here. Even orapworcl1-new was orapworcl1 when i created and tested it. You could see the filenames in orapwd line. I just renamed it now after all the testing just to post it. I do understand that the file name needs to be orapworcl1 and orapworcl2 on both the instances for it to work. One more thing that i forgot to add is that all the below ones work:
sql> conn sys/pwd@orcl
connected
sql> conn sys/pwd@orcl as sysdba
connected
sql> conn rmanuser/pwd@orcl
connected
sql> conn rmanuser/pwd@orcl as sysdba
connected

Grant sysdba in 8i

SQL> grant sysdba to test;
grant sysdba to test
ERROR at line 1:
ORA-01031: insufficient privileges
SQL> select * from v$version;
BANNER
Oracle8i Enterprise Edition Release 8.1.7.0.0 - Production
PL/SQL Release 8.1.7.0.0 - Production
CORE 8.1.7.0.0 Production
TNS for 32-bit Windows: Version 8.1.7.0.0 - Production
NLSRTL Version 3.4.1.0.0 - Production
SQL>

SQL> conn sys as sysdba
Enter password:
Connected.
SQL> show user
USER is "SYS"
SQL> grant sysdba to test;
grant sysdba to test
ERROR at line 1:
ORA-01031: insufficient privileges
SQL> select * from user_role_privs;
USERNAME GRANTED_ROLE ADM DEF OS_
SYS AQ_ADMINISTRATOR_ROLE YES YES NO
SYS AQ_USER_ROLE YES YES NO
SYS CONNECT YES YES NO
SYS CTXAPP YES YES NO
SYS DBA YES YES NO
SYS DELETE_CATALOG_ROLE YES YES NO
SYS EXECUTE_CATALOG_ROLE YES YES NO
SYS EXP_FULL_DATABASE YES YES NO
SYS HS_ADMIN_ROLE YES YES NO
SYS IMP_FULL_DATABASE YES YES NO
SYS JAVADEBUGPRIV YES YES NO
USERNAME GRANTED_ROLE ADM DEF OS_
SYS JAVAIDPRIV YES YES NO
SYS JAVASYSPRIV YES YES NO
SYS JAVAUSERPRIV YES YES NO
SYS JAVA_ADMIN YES YES NO
SYS JAVA_DEPLOY YES YES NO
SYS OEM_MONITOR YES YES NO
SYS RECOVERY_CATALOG_OWNER YES YES NO
SYS RESOURCE YES YES NO
SYS SELECT_CATALOG_ROLE YES YES NO
SYS SNMPAGENT YES YES NO
SYS TIMESERIES_DBA YES YES NO
USERNAME GRANTED_ROLE ADM DEF OS_
SYS TIMESERIES_DEVELOPER YES YES NO
23 rows selected.
SQL>

Password file and sysdba grant in 10g on AIX ...

Hi,
I am very familiar with password file, orapwd ...
I installed oracle 10gR2 database on AIX, created a password file using orapwd (file name orapwdSID.ora under $ORACLE_HOME/dbs), set remote_login_passwordfile='EXCLUSIVE' in init.ora file.
1 - When I select * from v$pwfile_users; I get 0 rows !!!
2 - When I try to grant sysdba to an_user; I get ORA-01994: GRANT failed: password file missing or disabled
Cause: The operation failed either because the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE was set to NONE or else because the password file was missing.
Action: Create the password file using the orapwd tool and set the INIT.ORA parameter REMOTE_LOGIN_PASSWORDFILE to EXCLUSIVE.
any idea.
thanks.

Hi,
I do not think so that this is a solution. because setting "Shared" means that all databases uses the same password file and only one user "SYS" is in this file (sysdba privilege) ...
Not what I am looking for !
regards.

System & sysdba privilege

since system account has been granted sysdba privilege during the creation of database why it can not startup or shutdown the instance .is it restricted to sys user regardless if other users has been granted sysdba privilege or not ?
Thanks in advance.

system has only "dba" privilege, but not "sysdba".
Regards
Laurent Schneider

Connecting as SYSDBA from Remote Machine

Hello,
I've installed Oracle8.6.1 on Linux6.2,& i've installed DBA studio on one my windows'NT machine.
When i want to connect as SYSDBA from DBA Studio & Username/Password as system/manager it says --
ORA-01031 Insufficient Privileges
but i'can connect as SYSOPER & Normal.
Do anyone know how to solve this problem???
null

1. use orapwd command-line utility to create a new password file.
2. set remote_login_passwordfile = exclusive in initxxx.ora file.
3. restart instance.
4. use sql*plus or svrmgrl to grant sysdba right to the schemas you want to be able to logon with sysdba rights.

How can I find exact username if I connected with sysdba privilege?

I granted sysdba privilge to a database user. I can connect that user as sysdba. From that users session, 'show user' command showing "SYS" and also username from v$session is also showing "SYS". How can I find actual username used for connecting the database as sysdba?
Steve Abraham

user10247588 wrote:
Thanks for the replay..
But my requirement is that in our production system auditors want to give separate username for each administrators (they are not recommending sys and system).
Normal dba privilege is not a problem. But for sysdba privilege every users are showing the user "SYS". How we can I identify which user is login to the database for a particular work if they connected as sysdba. How can I find which user did that (not just want the username "SYS", because all the administrators are identified by sys if they are connected as sysdba). If auditing is enabled how can I find the exact username. Because we are planning to give sysdba privilege to some of the administrators.
Also, is there any option to find the username, if one user is initiate shutdown of the database?First Please close the thread and keep questioning in only one thread.
then do not connect as sysdba

Connecting from remote as sysdba

Hi,
in 8.1.7.4 on Win 2003 machines
from a remote machine I have problem to connect as sysdba :
SQL> connect sys/***@mydb as sysdba
ERROR:
ORA-01017: invalid username/password; logon denied
SQL> connect system/***@mydb as sysdba
ERROR:
ORA-01031: insufficient privileges
SQL> connect user1/***@mydb
Connected.
What should be set in order to be able to connect as sysdba.
Thank for help.

Time and again and again this question is being asked
do a search in the forum you will hundreds of answers
anyway since you are in windows just make sure that
Do you have a Password file?
set remote_login_passwordfile=EXCLUSIVE
SQL> connect sys/***@mydb as sysdba
ERROR:
ORA-01017: invalid username/password; logon denied
You have entered a wrong password
enter the right password
SQL> connect system/***@mydb as sysdba
ERROR:
ORA-01031: insufficient privileges
you cannot system as sysdba with granting sysdba to system
SQL> connect user1/***@mydb
Connected.

System log in as sysdba

installed oracle 10g, and I configured oracle enterprise manager, I can access it using browser from another machine.
I found I can't login using system/password as sysdba, while sys can do so.
same thing for access using TOAD.
Can someone help me on this? I am new on this, your help is highly appreciated.
Thanks

Hello,
connect to the database as sys and grant the sysdba role to system. After that you can connect system as sysdba.
grant sysdba to system; will insert system as sysdbauser into the passwordfile.
ulli

CONNECT INTERNAL 시 SYS에 PASSWORD 걸기(SYSDBA, SYSOPER)

제품 : ORACLE SERVER
작성날짜 : 1997-03-31
SYS user 에 passwd 거는 방법
===========================
이를 걸게 되면 connect internal 접속 시 passwd를 물어보게 되며 DBA group이
아닌 다른 user에서도 sys user와 똑같이 작업할 수 있다.
1) initSID.ora 화일에
REMOTE_OS_AUTHENT = TRUE
REMOTE_LOGIN_PASSWORDFILE=EXCLUSIVE
2) ?/dbs 에서
orapwd file=orapwSID password=my_password entries=10
(이 때의 SID는 실제의 ORACLE_SID 를 적어주어야 함.)
3) connect internal 후
grant sysdba to scott
grant sysoper to scott 를 부여한다.
이를 부여하면 sys의 passwd를 알지 못해도
SVRMGR> connect internal;
SVRMGR> passwd ? :
만약 passwd 를 모르면
SVRMGR> connect scott/tiger as sysoper ;
SVRMGR> startup 이 가능하다.
참고) 이의 효과를 위해 /etc/group 화일에 oracle os user가 DBA group 이
아니어야 하며 일반 user에서도 위의 작업을 똑같이 실행하려면 configSID.ora
화일을 oracle user 아닌 다른 user에도 실행이 가능할 수 있도록 실행 MODE가
4755 이어야 한다.

If you want to connect a new user as SYSDBA or SYSOPER, you must first create a repository. Check some document for creating a repository with seperate tablespace.

User connected as sysdba ?

Dear ORACians,
How do i came to know that a connected user is connected as sysdba previlege?
is there any view ?
urs
selvan

SQL> conn sys@test as sysdba
Enter password: ***
Connected.
SQL> create user a identified by a;
User created.
SQL>
SQL> grant create session to a ;
Grant succeeded.
SQL>
SQL> grant resource to a ;
Grant succeeded.
SQL> conn a/a@test
Connected.
SQL> show user
USER is "A"
SQL> conn sys@test as sysdba
Enter password: ***
Connected.
SQL> grant sysdba to a;
Grant succeeded.
SQL> conn a/a@test as sysdba
Connected.
SQL> show user
USER is "SYS"
SQL>

Grant permission to a role.

Oracle 11g R2 Windows.
I have an oracle user, named user_1. User_1 needs to be able to grant select on a table owned by another user, User_2, to a role. I keep getting the error ORA-01031: insufficient privileges.
User_1 has the following system privileges:
ALTER ANY INDEX
ALTER ANY PROCEDURE
ALTER ANY ROLE
ALTER ANY SEQUENCE
ALTER ANY TABLE
ALTER ANY TRIGGER
ALTER USER
CREATE ANY INDEX
CREATE ANY PROCEDURE
CREATE ANY SEQUENCE
CREATE ANY TABLE
CREATE ANY TRIGGER
CREATE ANY TYPE
CREATE ANY VIEW
CREATE DATABASE LINK
CREATE SEQUENCE
CREATE SYNONYM
CREATE TABLE
CREATE USER
CREATE VIEW
DELETE ANY TABLE
DROP ANY INDEX
DROP ANY PROCEDURE
DROP ANY SEQUENCE
DROP ANY TABLE
DROP ANY TRIGGER
DROP ANY VIEW
EXECUTE ANY PROCEDURE
EXECUTE ANY TYPE
GRANT ANY PRIVILEGE
GRANT ANY ROLE
INSERT ANY TABLE
SELECT ANY DICTIONARY
SELECT ANY SEQUENCE
SELECT ANY TABLE
UNLIMITED TABLESPACE
UPDATE ANY TABLE
It has the following system roles:
CONNECT
DBA
RESOURCE
SELECT_CATALOG_ROLE
What permissions must User_1 have to allow it to grant select on a table in another schema to a role? Both SYS and SYSDBA can do it, but I don’t want to give such elevated permissions to User_1.
I have even granted SYSDBA to User_1 and I still get the ORA-01031 error!
Thanks,
Matthew

I believe you're looking for the GRANT ANY OBJECT PRIVILEGE privilege.
The ANY privileges are all very powerful privileges and they often create opportunities for crafty humans to do things that you might not have anticipated. They are generally frowned upon heavily in any sort of audit situation. I'd be very, very cautious about giving non-DBAs these privileges.
It would make much more sense to me, particularly when you appear to want to restrict things to a single schema, to have a DBA user create a stored procedure that does the actual grant (implementing whatever validations, logging, etc. are appropriate) and grant the user the privilege to execute this stored procedure.
Justin

Cannot loginto OEM as SYSDBA

can not log into OEM as user sys, Connect as SYSDBA. Got error message: invalid user name or password. But can log into OEM as user sys Connect as Normal.
Same case for TOAD.
Any help?

what are the outputs of these statements
SQL>show parameter password
SQL>select * from v$pwfile_users;
Do you have the pasword file created by
orapwd file=filename password=password entries=max_users
1. Create the password file. This is done by executing the following command:
$ orapwd file=filename password=password entries=max_usersThe filename is the name of the file that will hold the password information. The file location will default to the current directory unless the full path is specified. The contents are encrypted and are unreadable. The password required is the one for the SYS user of the database.
The max_users is the number of database users that can be granted SYSDBA or SYSOPER. This parameter should be set to a higher value than the number of anticipated users to prevent having to delete and recreate the password file.
2. Edit the init.ora parameter remote_login_passwordfile. This parameter must be set to either SHARED or EXCLUSIVE. When set to SHARED, the password file can be used by multiple databases, yet only the SYS user is recognized. When set to EXCLUSIVE, the file can be used by only one database, yet multiple users can exist in the file. The parameter setting can be confirmed by:
SQL> show parameter password
NAME                                 TYPE        VALUE
remote_login_passwordfile            string      EXCLUSIVE3. Grant SYSDBA or SYSOPER to users. When SYSDBA or SYSOPER privileges are granted to a user, that user's name and privilege information are added to the password file.
SQL> grant sysdba to scott;
Grant succeeded.4. Confirm that the user is listed in the password file.
SQL> select * from v$pwfile_users;
USERNAME                       SYSDBA SYSOPER
SYS                            TRUE   TRUE
SCOTT                          TRUE   FALSENow the user SCOTT can connect as SYSDBA. Administrative users can be connected and authenticated to a local or remote database by using the SQL*Plus connect command. They must connect using their username and password, and with the AS SYSDBA or AS SYSOPER clause:
SQL> connect scott/tiger as sysdba;
Connected.The DBA utilizes the orapwd utility to grant SYSDBA and SYSOPER privileges to other database users. The SYS password should never be shared and should be highly classified.

TO GRANT SYSDBA

Similar Messages

Maybe you are looking for