"Insufficient privileges"-error when starting database when on network

Hi
I have an Oracle 9.2.0.5 database installed on my laptop (Windows 2000 Prof), but I have a small problem.
When I'm plugged in to the company's network, I can start the database normally.
However, when I'm not connected to the company network, i.e. only logged in locally on my laptop, then I get an ORA-01031 Insufficient Privileges error when I start the database. Therefor, I can't do anything.
When I'm plugged into the company network, start the database, and then unplug my laptop, I can still connect to the database. So I guess it checks some userrights only when it starts the database.
I checked the user account settings, and my user is a local administrator, and is in the ORA_DBA usergroup.
Does someone know which setting I have to change?

You can install MS Loopback Adapter on your system and assign an IP Address to the loopback adapter. You should then be able to work even when not connected to the network.
Mudassar Choudhry.

Similar Messages

Get ORA-01031: insufficient privileges error, but only when using dbstart.

I am getting ORA-01031: insufficient privileges error, but only when using dbstart. the listener starts but not the database. How come I can start it from SQL prompt but not from dbstart scripts as the oracle user?
[oracle@mallard bin]$ ./dbstart
Processing Database instance "gf44": log file /prod/oracle/10/startup.log
[oracle@mallard bin]$
Log file:
Wed Aug 20 10:15:02 CDT 2008
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Aug 20 10:15:02 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> ERROR:
ORA-01031: insufficient privileges
SQL> ORA-01031: insufficient privileges
SQL>
/prod/oracle/10/bin/dbstart: Database instance "gf44" warm started.
>
oratab file:
gf44:/prod/oracle/10:Y
dbstart file section:
# See if it is a V6 or V7 database
VERSION=undef
if [ -f $ORACLE_HOME/bin/sqldba ] ; then
SQLDBA=svrmgrl
VERSION=`$ORACLE_HOME/bin/sqldba command=exit | awk '
/SQL\*DBA: (Release|Version)/ {split($3, V, ".") ;
print V[1]}'`
case $VERSION in
"6") ;;
*) VERSION="internal" ;;
esac
else
if [ -f $ORACLE_HOME/bin/svrmgrl ] ; then
SQLDBA=svrmgrl
VERSION="internal"
else
SQLDBA="sqlplus /nolog"
fi
fi
Permissions of file:
[oracle@mallard bin]$ ls -la dbstart
-rwxrwxr-x 1 oracle oinstall 10407 Aug 19 12:27 dbstart
[oracle@mallard bin]$
User permissions:
[root@mallard 10]# id oracle
uid=503(oracle) gid=503(oinstall) groups=503(oinstall),504(dba)
[root@mallard 10]#
I can start the listener manually using "./lsnrctl start" and start the database manually from sql prompt using "SQL>startup" (as sysdba) with no problems. this only happens when using dbstart file. I am logged in as oracle user and all environment variables are set
Thank you for any help you could provide.

I have the same problem, but i don't want insert this string
Connect sys/{password} as sysdbaI have deployed an Oracle 10g with os SunOS
$ uname -a
SunOS DB02 5.10 Generic_141444-09 sun4v sparc SUNW,Sun-Blade-T6320
I can connect with sys/password, but I can't login with
$ sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Thu Jan 7 15:19:50 2010
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> connect / as sysdba
ERROR:
ORA-01031: insufficient privilegesthe the startup and dbshut don't work.
Someone maybe help me?
Thanks,
Regards.
Lain

ORA-01031 insufficient privileges error when selecting from a view

OK I think this might be a dumb question but I can't figure it out:
User John has been granted SELECT privilege (directly, not through a database role) to schema FRED.table1;
User John can issue select * from FRED.table1; and it works just fine.
User John has then been granted SELECT privilege (directly, not via a database role) to schema
MARK.view1;
MARK.view1 only selects from FRED.table1. No other tables are in the view1.
Schema MARK can successfully query the views. SELECT * FROM VIEW1 returns results.
I also checked the MARK schema to ensure that it has been granted SELECT on FRED.table1 directly which it has.
Now, when logged into schema John, I try SELECT * FROM MARK.VIEW1; and I get ORA-01031 insufficient privileges error.
I'm not sure how to troubleshoot this. If John is granted SELECT ANY TABLE, it of course works but I don't want John to have that powerful priv.
To recap, John has SELECT on both MARK.VIEW1 and the table which VIEW1 selects from (FRED.TABLE1).
John can select from FRED.TABLE1 no problem but receives a privilege error even though John has SELECT on MARK.VIEW1.
Any thoughts?
Oh, Oracle EE 10.2.0.4

JSebastian wrote:
OK I think this might be a dumb question but I can't figure it out:
User John has been granted SELECT privilege (directly, not through a database role) to schema FRED.table1;
User John can issue select * from FRED.table1; and it works just fine.
User John has then been granted SELECT privilege (directly, not via a database role) to schema
MARK.view1;
MARK.view1 only selects from FRED.table1. No other tables are in the view1.
Schema MARK can successfully query the views. SELECT * FROM VIEW1 returns results.
I also checked the MARK schema to ensure that it has been granted SELECT on FRED.table1 directly which it has.
Now, when logged into schema John, I try SELECT * FROM MARK.VIEW1; and I get ORA-01031 insufficient privileges error.
I'm not sure how to troubleshoot this. If John is granted SELECT ANY TABLE, it of course works but I don't want John to have that powerful priv.
To recap, John has SELECT on both MARK.VIEW1 and the table which VIEW1 selects from (FRED.TABLE1).
John can select from FRED.TABLE1 no problem but receives a privilege error even though John has SELECT on MARK.VIEW1.
Any thoughts?
Oh, Oracle EE 10.2.0.4Are you certain John has been granted select on Mark.view1 ? In order for that to work Mark would have to have been given select on Fred.table1 WITH GRANT OPTION ... otherwise the grant would fail and then John would not be able to select from the view because the grant was never successfully issued.
Here's a basic test case (which i think conforms to what you've outlined) to get it working.
drop user u1 cascade;
drop user u2 cascade;
drop user u3 cascade;
create user u1 identified by u1;
grant connect, resource to u1;
create user u2 identified by u2;
grant connect, resource, create view to u2;
create user u3 identified by u3;
grant connect, resource to u3;
connect u1/u1@orcl
create table test1 (col1 number);
grant select on test1 to u2 with grant option; --> this is the important part
grant select on test1 to u3;
connect u2/u2@orcl
create view test2 as select * from u1.test1;
grant select on test2 to u3;
connect u3/u3@orcl
select * from u2.test2;

SQL error in the database when accessing a table.

Hi,
I got below error at production server. Please suggest how to reslove this error.
 
 
 
Runtime Errors DBIF_RSQL_SQL_ERROR
 
Exception CX_SY_OPEN_SQL_DB
 
Date and Time 02.01.2011 15:55:06
 
 
 
 
 
Short text
 
SQL error in the database when accessing a table.
 
 
 
How to correct the error
 
Database error text........: "[10054] TCP Provider: An existing connection was
 
forcibly closed by the remote host.
 
[10054] Communication link failure"
 
Internal call code.........: "[RSQL/INSR/SWFCNTBUF ]"
 
Please check the entries in the system log (Transaction SM21).
 
 
If the error occures in a non-modified SAP program, you may be able to
 
find an interim solution in an SAP Note.
 
If you have access to SAP Notes, carry out a search with the following
 
keywords:
 
 
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
 
"CL_SWF_CNT_FACTORY_SHMEM======CP" or "CL_SWF_CNT_FACTORY_SHMEM======CM001"
 
| "ADD_INSTANCE"
 
 
 
Information on where terminated
 
Termination occurred in the ABAP program "CL_SWF_CNT_FACTORY_SHMEM======CP" -
 
in "ADD_INSTANCE".
 
The main program was "SAPMSSY1 ".
 
 
In the source code you have the termination point in line 16
 
of the (Include) program "CL_SWF_CNT_FACTORY_SHMEM======CM001".
 
The termination is caused because exception "CX_SY_OPEN_SQL_DB" occurred in
 
procedure "ADD_INSTANCE" "(METHOD)", but it was neither handled locally nor
 
declared
 
in the RAISING clause of its signature.
 
 
The procedure is in program "CL_SWF_CNT_FACTORY_SHMEM======CP "; its source
 
code begins in line
 
1 of the (Include program "CL_SWF_CNT_FACTORY_SHMEM======CM001 ".
 
 
 
 
Source Code Extract
 
 
Line
SourceCde
 
 
1
METHOD add_instance .
 
2
 
3
data: ls_id type swfcntbuf.
 
4
 
5
check buffer method - store in local buffer if necessary
 
6
retcode = cl_swf_cnt_factory=>add_instance( ibf_por = ibf_por instance = instance ).
 
7
 
8
CHECK m_buffer_method EQ mc_buffer_shared.
 
9
 
10
append key to list of tasks to add stored in database table SWFCNTBUF
 
11
will be evaluated by build process for shared memory area (UPDATE_BUFFER method)
 
12
 
13
ls_id-mandt = sy-mandt.
 
14
ls_id-id = ibf_por.
 
15
 
>>>>>
INSERT swfcntbuf CONNECTION r/3*wfcontainer
 
17
FROM ls_id.
 
18
 
19
IF sy-subrc EQ 0.
 
20
Commit seems to be necessary always, even if INSERT has failed, to get rid of
 
21
database locks
 
22
COMMIT CONNECTION r/3*wfcontainer.
 
23
ENDIF.
 
24
 
25
ENDMETHOD.
 

duplicate here SQL error in the database when accessing a table.
Do not post the same question in more than on forum.

DBIF_RSQL_SQL_ERROR with SQL error in the database when accessing a table.

dear all,
i have done a system copy from production server into quality server. quality was scrapped and freshly installed with SAP then used the DB flush method to carry out the system copy. i had to change the DBS_ORA_SCHEMA in environment variables to SAP<SOURCE SID> from SAPSR3. the sap version is ECC6.0,DB is ORACLE10.2 on WIN NT.
after MMC opened, i get "SQL error in the database when accessing a table" error is coming. in SM21, I am getting "Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000 )
Database error 8103 at SEL access to table TBTCO
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
Database error 8103 at FET access to table TBTCP
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130339 sibqty_Q TY_00 " generated
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
> Short dump "081018 130339 sibqty_Q TY_00 " generated
Transaction Canceled 00 671 ( DBIF_RSQL_SQL_ERROR 20081018130339sibqty_QTY_00 SAPSYS 000
Delete session 001 after error 023
Database error 8103 at DEL access to table TMSALOGAR
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130432 sibqty_Q TY_00 " generated
Database error 8103 at FET access to table SNAP
Run-time error "DBIF_RSQL_SQL_ERROR" occurred
> Short dump "081018 130432 sibqty_Q TY_00 " generated
Transaction Canceled SY 002 ( SQL error in the database when accessing a table. )
Database error 8103 at FET access to table TSP02"
please find the st22 DUMP:
ow to correct the error |
Database error text........: "ORA-08103: object no longer exists"
Internal call code.........: "[RSQL/READ/TBTCO ]"
Please check the entries in the system log (Transaction SM21).
If the error occures in a non-modified SAP program, you may be able to
find an interim solution in an SAP Note.
If you have access to SAP Notes, carry out a search with the following
keywords:
"DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
"SAPMSSY2" or "SAPMSSY2"
"INITIATE_JOB_START"
If you cannot solve the problem yourself and want to send an error
notification to SAP, include the following information:
1. The description of the current problem (short dump)
To save the description, choose "System->List->Save->Local File
(Unconverted)".
2. Corresponding system log
Display the system log by calling transaction SM21.
Restrict the time interval to 10 minutes before and five minutes
after the short dump. Then choose "System->List->Save->Local File
(Unconverted)".
3. If the problem occurs in a problem of your own or a modified SAP
program: The source code of the program
In the editor, choose "Utilities->More
Utilities->Upload/Download->Download".
4. Details about the conditions under which the error occurred or which
actions and input led to the error.
The exception must either be prevented, caught within proedure
"INITIATE_JOB_START" "(FORM)", or its possible occurrence must be declared in
the
RAISING clause of the procedure.
|
please do me this favor if you know to avoid this problem..
thanks a lot..

Hello Anuj,
This is because the COUNT(*) is returning a value which is longer than the INT4 data type it is expecting. If you restrict the selection by introducing a WHERE clause, then you won't get the dump:
DATA: dyn_from TYPE string,
 dyn_where TYPE string,
 gx_sql_err TYPE REF TO cx_sy_open_sql_error,
 gv_text TYPE string.
dyn_from = `DD01L INNER JOIN DD02L ON DD02L~AS4LOCAL = DD01L~AS4LOCAL AND DD02L~AS4VERS = DD01L~AS4VERS`.
dyn_where = `DOMNAME LIKE 'Z%'`.
TRY .
 SELECT COUNT(*) FROM (dyn_from) WHERE (dyn_where).
 WRITE: / sy-dbcnt NO-GROUPING.
CATCH: cx_sy_open_sql_db INTO gx_sql_err,
 cx_sy_dynamic_osql_semantics INTO gx_sql_err,
 cx_sy_dynamic_osql_syntax INTO gx_sql_err.
ENDTRY.
IF gx_sql_err IS BOUND.
gv_text = gx_sql_err->get_text( ).
WRITE: / gv_text.
ENDIF.
BR,
Suhas

DBIF_RSQL_SQL_ERROR: SQL error in the database when accessing a table

Hi Gurus,
Im getting DBIF_RSQL_SQL_ERROR: SQL error in the database when accessing a table error while I was importing support pack in the system. This is ERP 6.0 with EHP4 with MS SQL in back ground and I was applying the BASIS SP 04. It was in the TEST scenario and in the SPDD_SPAU_CHECK phase it threw the error.
Short text
    SQL error in the database when accessing a table.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
How to correct the error
    Database error text........: "[601] Could not continue scan with NOLOCK due to
     data movement."
    Internal call code.........: "[RSQL/FTCH/E071 ]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "SAPLSVRT" or "LSVRTU01"
    "TR_LAST_IMPORT_OF_OBJECT"
SPAM is ending with the above short dump. I have checked the space availability and it is OK.
Kindly help.
Renju Aravind.

Hi,
this error is very often seen in case of a database corruptions. Please follow note 142731 and perform a complete database check. Send the results when they show errors.
Best regards
Clas

Getting error "SQL error in the database when accessing a table."

Hi All,
We are getting Dump Error SQL error in the database when accessing a table for the batch job EISSD/REQUISITION 14 / which includes program AQ20FD==========A2============. Please reply. The Dump error details are as follows
Short text
    SQL error in the database when accessing a table.
How to correct the error
    Database error text........: "ORA-01555: snapshot too old: rollback segment
     number 21 with name "_SYSSMU21$" too small"
    Internal call code.........: "[RSQL/FTCH/VBRK ]"
    Please check the entries in the system log (Transaction SM21).
Thanks
Padmakar Kudtarkar
Edited by: Rob Burbank on May 19, 2011 9:38 AM

The query where we are getting error in Standard program AQ20FD==========A2============ for Job
EISSD/REQUISITION 14 / is as follows:
select VBRKBUKRS VBRKFKART VBRKFKDAT VBRKFKTYP VBRKGJAHR VBRKKUNAG VBRKKUNRG VBRKKURRF VBRKVBELN VBRKWAERK VBRP~AUBEL
       VBRPAUPOS VBRPFKIMG VBRPKVGR2 VBRPKZWI1 VBRPMATNR VBRPMWSBP VBRPNETWR VBRPPSTYV VBRPVBELN VBRPVGBEL VBRP~VGPOS
       VBRPVKBUR VBRPVKGRP VBRPVRKME VBRPWAVWR
into (VBRK-BUKRS , VBRK-FKART , VBRK-FKDAT , VBRK-FKTYP , VBRK-GJAHR , VBRK-KUNAG , VBRK-KUNRG , VBRK-KURRF , VBRK-VBELN
     , VBRK-WAERK , VBRP-AUBEL , VBRP-AUPOS , VBRP-FKIMG , VBRP-KVGR2 , VBRP-KZWI1 , VBRP-MATNR , VBRP-MWSBP , VBRP-NETWR
     , VBRP-PSTYV , VBRP-VBELN , VBRP-VGBEL , VBRP-VGPOS , VBRP-VKBUR , VBRP-VKGRP , VBRP-VRKME , VBRP-WAVWR )
from ( VBRK
       inner join VBRP
       on VBRPVBELN = VBRKVBELN )
       where VBRK~BUKRS in SP$00004
         and VBRK~FKDAT in SP$00001
         and VBRK~KUNAG in SP$00002
         and VBRK~VBELN in SP$00006
         and VBRP~MATNR in SP$00003.
%dbacc = %dbacc - 1.
if %dbacc = 0.
    stop.
endif.
check SP$00004.
check SP$00001.
check SP$00002.
check SP$00006.
check SP$00003.
add 1 to %count-VBRK.
%linr-VBRK = '01'.
extract %fg01.
%ext-VBRP01 = 'X'.
    extract %fgwrVBRP01.
endselect.

Root cause of "SQL error in the database when accessing a table. "

Dear experts,
I meet this dump "SQL error in the database when accessing a table" when executing a sql.
Sql:
    SELECT sesssessno poscrm_serplan_id poscrm_ser_h_id poscrm_ser_i_id
           possolution_id sessbundle_id sessdbid sessinstno pos~crm_ordered_prod
           sessdbid sessinstno
      INTO CORRESPONDING FIELDS OF TABLE et_sess_list
      FROM dsvassessadmin AS sess JOIN service_posn_sm AS pos
        ON possession_id     = sesssessno
      FOR ALL ENTRIES IN lt_contractno
      WHERE sess~contractno = lt_contractno-contract_no
       AND sess~status IN lt_status_range
       AND bundle_id IN lt_bundle_id
       AND pos~solution_id GT 0
This sql works well in dev system SD7, however, it causes dump in another dev system "SMV".
Can anyone give me any ideas?
Thanks

Hi Jovito,
This is info from ST22
Short text
    SQL error in the database when accessing a table.
What can you do?
    Note which actions and input led to the error.
    For further help in handling the problem, contact your SAP administrator
    You can use the ABAP dump analysis transaction ST22 to view and manage
    termination messages, in particular for long term reference.
How to correct the error
    Database error text........: "SQL0101N The statement is too long or too
     complex. SQLSTATE=54001"    Internal call code.........: "[RSQL/OPEN/DSVASSESSADMIN ]"
    Please check the entries in the system log (Transaction SM21).
    If the error occures in a non-modified SAP program, you may be able to
    find an interim solution in an SAP Note.
    If you have access to SAP Notes, carry out a search with the following
    keywords:
    "DBIF_RSQL_SQL_ERROR" "CX_SY_OPEN_SQL_DB"
    "CL_AGS_SERVICE_SERV===========CP" or "CL_AGS_SERVICE_SERV===========CM018"
    "GET_OVS_SESSION_LIST"
    If you cannot solve the problem yourself and want to send an error
    notification to SAP, include the following information:
    1. The description of the current problem (short dump)
       To save the description, choose "System->List->Save->Local File
    (Unconverted)".
    2. Corresponding system log
       Display the system log by calling transaction SM21.
       Restrict the time interval to 10 minutes before and five minutes
    after the short dump. Then choose "System->List->Save->Local File
    (Unconverted)".
    3. If the problem occurs in a problem of your own or a modified SAP
    program: The source code of the program
       In the editor, choose "Utilities->More
    Utilities->Upload/Download->Download".
    4. Details about the conditions under which the error occurred or which
    actions and input led to the error.
    The exception must either be prevented, caught within proedure
    "GET_OVS_SESSION_LIST" "(METHOD)", or its possible occurrence must be declared
     in the
    RAISING clause of the procedure.
    To prevent the exception, note the following:
It seems that after translation the native sql is too long. But I think this can be solved.

Inbound-Queue SYSFAIL: SQL error in the database when accessing a table

Hi,
we send around 80 IDoc simultaneously, there 15 are stuck.
They all have SYSFAIL in SMQ2 with message: SQL error in the database when accessing a table
I already unlocked the queues and try to resend. Nothing happend!
I ran RSQIWKEX for the single queus but now there are new queues in Status SYSFAIL.
I already checked some entries in forum and blogs, but nothing worked out yet!
Can someone help?! it's urgent!!
br

Hi, well as mentioned i searched and found this already.
But in ST22 i got error concerning
Laufzeitfehler DBIF_RSQL_SQL_ERROR
Ausnahme CX_SY_OPEN_SQL_DB
So i guess it's something more serious.
Any more ideas?!
Can i simply delete the stucked queues and reporcess them?!
br

ORA-01031: Insufficient privileges error in upgrading from 9.2.0.5 to 10.2

Hi, I am using DBUA to upgrade oracle 9i database to 10g. In step 1 of 7 when I select 9i datagase to upgrade I get ORA-01031: Insufficient privileges error. However, I can connect to the database from 9i as well as 10g using SQLPlus. Any idea what could be going wrong? Thanks. Manish
Edited by: user635081 on Jul 22, 2009 10:38 AM

Check your REMOTE_LOGIN_PASSWORDFILE . If it is set to NONE, then make sure that SQLNET.AUTHENTICATION_SERVICES = (NTS) in your sqlnet.ora file.
the OS user should be in ORA_DBA group.
Try connecting as SYS,
SQL> sqlplus /nolog
SQL> connect / as sysdba
HTH
Anantha

SQL Workshop insufficient privileges error :-S

Hi everyone,
The problem I have is when I try to compile a procedure, function or whatever I get the ORA-01031: insufficient privileges error.
I tryed to give the DBA role to the APEX_PUBLIC_USER without success.
I tryed to grant the "execute" (on an especified procedure or function for testing purposes) privileges to that user and I still getting the error. :-S
I can compile any object from the SQL Navigator but APEX.
What am I missing?
Hope u could help me :)
Thanks in advance,
Fury Morales.

You should not be messing around with the grants made to the APEX product accounts (FLOWS_xxx etc).
Scott's suggestion is to have your workspace parsing schema be granted the 'create procedure' privilege.
From sqlworkshop you can the run query below to determine the 'system' privileges granted to the workspace schema
select privilege from user_sys_privs;
Varad
Edited by: varad acharya on Jul 28, 2009 4:32 PM

"insufficient privilege" ERROR?

I'm a very newbie to Oracle world.....
It seems the installer or DBCA not have enough privilege to create Database....
How to fix this "insufficient privilege" ERROR?

the below text shows what problem I fight with......
bash-2.03$ sqlplus "/as sysdba"
SQL*Plus: Release 9.0.1.0.0 - Production on Thu Mar 23 03:22:20 2006
(c) Copyright 2001 Oracle Corporation. All rights reserved.
Connected to an idle instance.
SQL> grant sysdba to oracle
2 ;
grant sysdba to oracle
ERROR at line 1:
ORA-01034: ORACLE not available
SQL> conn oracle
Enter password:
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
SVR4 Error: 2: No such file or directory
Warning: You are no longer connected to ORACLE.
SQL>

"ora-01031 insufficient privilege" error

We are getting "ora-01031 insufficient privilege" error while registering Apps as target user in production environment.
We tried to add the user using below method
· Design Center / Global Explorer / Security / Users -> Right click -> New user
· Repository assistance.
· Given the OWB owner as the DBA privilege.
Please let me know how to investigate further
Thanks a lot for your help.

Hi!
Please check the following query after the user registration. But the question is, are you registering the users with the repository owner?
select * FROM user_role_privs;
Regards.
Sebastian

ORA-01031:Insufficient Privileges error when I am trying to use ALERT_QUE

Hi,
I am working on SYS.ALERT.QUE for getting system alerts. I am using ODP in C# for connecting to Oracle database with username = SYSTEM, but when I am trying to enque or deque any message from SYS.ALERT.QUE, its gives an error ORA-01031:Insufficient Privileges. I am not able to understand how to assign SYSDBA privileges to SYSTEM and access ALERT_QUE for getting system alerts. I am posting my code below, plz have a look and let me know whats wrong with the code. I am able to connect to databse using SYSTEM, do I need to use username = SYS for accesing ALERT_QUE of database? Plz let me know whats the solution.
OracleConnection con = new OracleConnection(constr);
// Create queue
OracleAQQueue queue = new OracleAQQueue("sys.alert_que", con);
// Open connection
con.Open();
// Begin txn for enqueue
OracleTransaction txn = con.BeginTransaction();
// Set message type for the queue
queue.MessageType = OracleAQMessageType.Raw;
// Prepare message and RAW payload
OracleAQMessage enqMsg = new OracleAQMessage();
byte[] bytePayload = { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 };
enqMsg.Payload = bytePayload;
OracleAQAgent[] agent = new OracleAQAgent[1];
agent[0] = new OracleAQAgent("SUBSCRIBER1");
enqMsg.Recipients = agent;
enqMsg.SenderId = new OracleAQAgent("SENDER1");
// Prepare to Enqueue
queue.EnqueueOptions.Visibility = OracleAQVisibilityMode.OnCommit;
// Enqueue message
queue.Enqueue(enqMsg);
The code throws exception at line "queue.Enqueue(enqMsg);" saying ORA-01031:Insufficient Privileges
Edited by: 916462 on Feb 27, 2012 3:31 AM

Hi Sudheendra,
Thanks a lot, that worked. Now I am facing one more new issue, when I am trying to deque message from ALERT_QUE which is oracle maintained queue for alerts, I am getting an error "ORA-25215:User data type and queue type do not match". Is there something wrong with my code like Message type, payload and all. I am very new to Oracle database so I don't have idea about this details. Can u plz help me in solving this.
OracleTransaction txn = con.BeginTransaction();
// Set message type for the queue
queue.MessageType = OracleAQMessageType.Raw;
// Prepare message and RAW payload
OracleAQMessage enqMsg = new OracleAQMessage();
byte[] bytePayload = { 0, 1, 2, 3, 4, 5, 6, 7, 8, 9 };
enqMsg.Payload = bytePayload;
OracleAQAgent[] agent = new OracleAQAgent[1];
agent[0] = new OracleAQAgent("SUBSCRIBER1");
enqMsg.Recipients = agent;
enqMsg.SenderId = new OracleAQAgent("SENDER1");
// Begin txn for Dequeue
txn = con.BeginTransaction();
// Prepare to Dequeue
queue.DequeueOptions.Visibility = OracleAQVisibilityMode.OnCommit;
queue.DequeueOptions.Wait = 10;
queue.DequeueOptions.ConsumerName = "SUBSCRIBER1";
// Dequeue message
OracleAQMessage deqMsg = queue.Dequeue();
txn.Commit();
Edited by: 916462 on Feb 28, 2012 9:55 PM

Insufficient privilege error when executing DBMS_ERRLOG through PLSQL

Hi,
I shall be grateful if any one of you give me the solution at the earliest.
I have 2 schemas like A & B those are running on Oracle 10g rel2.
As per my buz req' I need to create DML Error log table for 'A.T1' table in B schema using DBMS_ERRORLOG package.
I have granted direct SELECT on A.T1 to B (...not through ROLE as it doesn't work in plsql)
The problem is when i'm running the procedure,
DBMS_ERRLOG.CREATE_ERROR_LOG('A.T1', 'err_T1', 'B');
in SQL*Plus of B schema, it's creating the error log table successfully.
But the same will get failed when i run this error log procedure with in a procedure owned by B schema.
It throws 'ORA-01031: insufficient privileges'...
I hope this is related to privilege issue which is working fine in SQL*Plus but NOT in PLSQL stored procedure.
Awaiting your earliest reply.
Thanks.
- Ela

Hi,
It's not an issue with direct privilege. Actually the package is working when i execute it with in a ananymous block, but the same get fails when execute it through procedures...
Even we have given COMMENT ANY TABLE priv to the schema and that too didn't work out.
awaiting your reply.
-Saravanan

"Insufficient privileges"-error when starting database when on network

Similar Messages

Maybe you are looking for