ORA-01031 in OWB deployment

Dear all,
My question ist following:
1. I imported a flate file and assign it to externaal table. Everything is fine. If i try to read the content of external table getting error message:
ORA-00942 (table or view does not exists).
Question: Which priviledge must give to the staging user. I gave him also grant select any table to target_user from sysdba side, but error stay the same.
I will be appreciate getting reponse from you.
Thans in advance

Hi david,
Look at this error message after deployment:
Name
Action
Status
Log
None
Error
ORA-01031: insufficient privileges
ORA-06512: at "REPOS_USER.WB_RT_TARGET_SCHEMA_OBJS", line 13
ORA-06512: at "REPOS_USER.WB_RT_TARGET_SCHEMA_OBJS", line 109
ORA-06512: at line 1
RCP_FF_LOCATION2
Create
Error
ORA-01031: insufficient privileges ----->>>>>> What privilege must give them in addition
RCP_EXT
Create
Error
ORA-06564: object RCP_FF_LOCATION2 does not exist --->>>> This location exists exactly.
I dont know since wwhen we must give gratnt to access directory to user????. If eveything should be implemented manually, what is the need of OWB?.
Regards Mehdi

Similar Messages

Getting started - ORA-01031 deployment Error

Hi,
I am new to Oracle and Oracle Warehouse Builder and I am reading through the Book "Oracle Warehouse Builder 11g: Getting Started"
I have reached the final chapter where I need to deploy and execute my project. In the book an External table is setup to get some data to a store dimension. When I deploy the File location to this external table I get ORA-01031 Insufficient priveleges - what is wrong and how can I resolve it? Since I am very new to this I would appriciate a step-by-step solution.
Kind Regards,
Søren
Edit: I am using 11gR2 even though the book is written for 11gR1
Edited by: sdjensen on 2010-05-10 05:19

Hi Søren
If you are using 11gR2 then the 'CREATE ANY DIRECTORY' privilege was revoked from the OWB user role, to tighten security. For demo purposes you can grant this privilege to the target user from sys;
GRANT CREATE ANY DIRECTORY to YOURUSER;
The production-ready secure way would be for the dba to grant you read/write privileges on an existing SQL directory object and you can reference this from OWB (in the connector from the Oracle location to file location).
Cheers
David

Failure to deploy dimension - ORA-01031: insufficient privileges?

Hi all,
1. I imported a mdl file.
2. Then I registered all locations
3. Then I deployed all staging area objects successfully.
4. Then I deployed sequences and tables in the target module successfully.
5. However, when I want to deploy the dimensions in the target module, it fails with "ORA-01031: insufficient privileges". I'm working with a privileged user with the Administrator role. I even went and manually granted CREATE ANY DIMENSION priv to that user. But it still fails.
What am I doing wrong?
Thanks,
Juanita

Nevermind, found the problem. Needed to register the DB user as a target user.

OWB 10gR2 ORA-01031: insufficient privileges

Registering Users as Warehouse Builder +OWB
When adding target schema (Global explorer=>User=>New) in the OWB, I am getting this error
ORA-01031: insufficient privileges
I have created this target and did grant DBA to this user. Still getting this error.
rep_owner is in the same database (where the target schema user ) and has DBA privilege too
Thanks

Yes, Carsten. Tried that too but getting the same result as an insufficient privileges
I have given DBA to all users also, but no +ve result

Error in OWB deployment Scripts

My OWB deployment scripts (the SQL PACKAGES created post deployment) are having errors.
When my source table, target table are in the same warehouse target schema which is owned by the Runtime Repository, the deployment scripts are working fine. But if the source or target table is moved to a different schema then the deployment scripts are giving errors saying - "PL/SQL: ORA-00942: table or view does not exist".
Please let me know how to rectify this error when my source and/or target tables are in separate schema....
-arnab

The problem is solved. One more question I have, in the Expression Operator, we have two groups, the input group and the output group. But if there is a need to have some attibutes for storing temporary calculations as well, before assigning them to the attributes of the output group, then under which group should these be made? I am asking for something like a variable group where the attibutes for storing temporary calculations will be made and these attributes can be used by the output group for sending the values to the next transformation.
Please help ..
Regards
Arnab

"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

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

Owb deployment error

Hi
I have production deployment problem.
I moved all the objects from development to production when i trying to deploy the external tables.
It's giving two errors one is
Create
Error
ORA-01031: insufficient privileges
EO_SOURCE
Create
Error
ORA-01031: insufficient privileges
HATS_DAILY_CONV_IVR_EXT
Create
Error
ORA-06564: object EO_SOURCE does not exist
any body please suggest me wat to do
with these errors
and I need to create process flow for this
which is better first i need to create in dev then moved to prod
or directly i can create in prod
thanks in advance

means how can i create that from DB.
can explain they will keep file in prod box i.e EO_SOURCE
using that file i am trying to create external table
please help me
thanks for reply

Using database-link in view to get around ORA-01031 error

I have been granted select rights on a users table. I am therefore able to select from his table. If however I try create a view against his table I run into the ORA-01031 problem. I have worked around this problem by creating a database-link to myself and then adding that to the view creation and it works. What are the downsides of using the database-link in this way?

The only down side I have been able to identify is that a extra session is created and that the CPU has a little extra work due to the LOOP BACK that takes place. I need to ensure the network is not unnessesarly used and therefore will need to ensure that 127.0.0.1 (local host) is used in the database connection discription. e.g.
create database link my_db_link connect to scott identified by tiger using '(description=(address=(protocol=tcp)(host=127.0.0.1) (Port = 1521) ) (connect_data= (sid=ora10g)))';

Ora-01031 on RHEL 5 with 10gr2 after installation

Hi Friends,
OS : RHEL 5
DB : 10.2.0.4
we installed oracle10g on a new RHEL 5 machine and upgraded to 10.2.0.4. now we are unable to connect / as sysdba and getting following error
[oracle@xxxxxxxxx db]$ sqlplus "/ as sysdba"
SQL*Plus: Release 10.2.0.4.0 - Production on Tue Feb 2 13:15:51 2010
Copyright (c) 1982, 2007, Oracle. All Rights Reserved.
ERROR:
ORA-01031: insufficient privileges
actually installation was done by other DBA who left now and i am taking care
following metalink note 69642.1, i found some facts
1) variable TNS_ADMIN was not set
2) sqlnet.ora file not there except in samples directory (but we have tnsnames.ora and listener.ora in network/admin path)
3) output of cat config.[cs] is as follows
[oracle@viadbscph802v lib]$ cat config.[cs]
/* SS_DBA_GRP defines the UNIX group ID for adminstrative access. */
/* Refer to the Installation and User's Guide for further information. */
#define SS_DBA_GRP "dba"
#define SS_OPER_GRP "dba"
char *ss_dba_grp[] = {SS_DBA_GRP, SS_OPER_GRP};
4) but, i found id was not showing dba group
[oracle@viadbscph802v lib]$ id
uid=511(oracle) gid=511(oracle) groups=511(oracle)
5) i checked permissions for oracle in $ORACLE_HOME/bin and proper permissions exists
6) password file is in place
7) TWO_TASKS is not set
please suggest me anything more to do to solve this problem
thanks in advance
Edited by: Pavan - a DBA on 2 Feb, 2010 5:56 PM

Hi Pavan,
Sometime it happens that issue / problem wish us; we forgets the basic answer. I am remembeing you have mentioned so many time in the forum to check the dba group to different OPs, but....!
Re: ORA-01031: insufficient privileges
Re: ORACLE-client & CITRIX
Re: "Create User" gives ORA-01031: insufficient privileges for user sys
But since problem has been solved... so its good for all...!
Regards
Girish Sharma

ORA-01031: insufficient privileges in PL/SQL but not in SQL

I have problem with following situation.
I switched current schema to another one "ban", and selected 4 rows from "ed"
alter session set current_schema=ban;
SELECT * FROM ed.PS WHERE ROWNUM < 5;
the output is OK, and I get 4 rows like
ID_S ID_Z
1000152 1
1000153 1
1000154 1
1000155 1
but following procedure is compiled with warning
create or replace
procedure proc1
as
rowcnt int;
begin
select count(*) into rowcnt from ed.PS where rownum < 5;
end;
"Create procedure, executed in 0.031 sec."
5,29,PL/SQL: ORA-01031: insufficient privileges
5,2,PL/SQL: SQL Statement ignored
,,Total execution time 0.047 sec.
Could you help me why SELECT does work in SQL but not in PL/SQL procedure?
Thanks.
Message was edited by:
MattSk

Privs granted via a role are only valid from SQL - and not from/within stored PL/SQL code.
Quoting Tom's (from http://asktom.oracle.com) response to this:I did address this role thing in my book Expert one on one Oracle:
<quote>
What happens when we compile a Definer rights procedure
When we compile the procedure into the database, a couple of things happen with regards to
privileges. We will list them here briefly and then go into more detail:
q    All of the objects the procedure statically accesses (anything not accessed via dynamic SQL)
are verified for existence. Names are resolved via the standard scoping rules as they apply to the
definer of the procedure.
q    All of the objects it accesses are verified to ensure that the required access mode will be
available. That is, if an attempt to UPDATE T is made - Oracle will verify the definer or PUBLIC
has the ability to UPDATE T without use of any ROLES.
q    A dependency between this procedure and the referenced objects is setup and maintained. If
this procedure SELECTS FROM T, then a dependency between T and this procedure is recorded
If, for example, I have a procedure P that attempted to 'SELECT * FROM T', the compiler will first
resolve T into a fully qualified referenced. T is an ambiguous name in the database - there may be
many T's to choose from. Oracle will follow its scoping rules to figure out what T really is, any
synonyms will be resolved to their base objects and the schema name will be associated with the
object as well. It does this name resolution using the rules for the currently logged in user (the
definer). That is, it will look for an object owned by this user called T and use that first (this
includes private synonyms), then it will look at public synonyms and try to find T and so on.
Once it determines exactly what T refers to - Oracle will determine if the mode in which we are
attempting to access T is permitted.   In this case, if we as the definer of the procedure either
owns the object T or has been granted SELECT on T directly or PUBLIC was granted SELECT, the
procedure will compile. If we do not have access to an object called T by a direct grant - the
procedure P will fail compilation. So, when the object (the stored procedure that references T) is
compiled into the database, Oracle will do these checks - and if they "pass", Oracle will compile
the procedure, store the binary code for the procedure and set up a dependency between this
procedure and this object T. This dependency is used to invalidate the procedure later - in the
event something happens to T that necessitates the stored procedures recompilation. For example,
if at a later date - we REVOKE SELECT ON T from the owner of this stored procedure - Oracle will
mark all stored procedures this user has that are dependent on T, that refer to T, as INVALID. If
we ALTER T ADD some column, Oracle can invalidate all of the dependent procedures. This will cause
them to be recompiled automatically upon their next execution.
What is interesting to note is not only what is stored but what is not stored when we compile the
object. Oracle does not store the exact privilege that was used to get access to T. We only know
that procedure P is dependent on T. We do not know if the reason we were allowed to see T was due
to:
q    A grant given to the definer of the procedure (grant select on T to user)
q    A grant to public on T (grant select on T to public)
q    The user having the SELECT ANY TABLE privilege
The reason it is interesting to note what is not stored is that a REVOKE of any of the above will
cause the procedure P to become invalid. If all three privileges were in place when the procedure
was compiled, a revoke of ANY of them will invalidate the procedure - forcing it to be recompiled
before it is executed again. Since all three privileges were in place when we created the procedure
- it will compile successfully (until we revoke all three that is). This recompilation will happen
automatically the next time that the procedure is executed.
Now that the procedure is compiled into the database and the dependencies are all setup, we can
execute the procedure and be assured that it knows what T is and that T is accessible. If something
happens to either the table T or to the set of base privileges available to the definer of this
procedure that might affect our ability to access T -- our procedure will become invalid and will
need to be recompiled.
This leads into why ROLES are not enabled during the compilation and execution of a stored
procedure in Definer rights mode. Oracle is not storing exactly WHY you are allowed to access T -
only that you are. Any change to your privileges that might cause access to T to go away will cause
the procedure to become invalid and necessitate its recompilation. Without roles - that means only
'REVOKE SELECT ANY TABLE' or 'REVOKE SELECT ON T' from the Definer account or from PUBLIC. With
roles - it greatly expands the number of times we would invalidate this procedure. If some role
that was granted to some role that was granted to this user was modified, this procedure might go
invalid, even if we did not rely on that privilege from that role. ROLES are designed to be very
fluid when compared to GRANTS given to users as far as privilege sets go. For a minute, let's say
that roles did give us privileges in stored objects. Now, most any time anything was revoked from
ANY ROLE we had, or any role any role we have has (and so on -- roles can and are granted to roles)
-- many of our objects would become invalid. Think about that, REVOKE some privilege from a ROLE
and suddenly your entire database must be recompiled! Consider the impact of revoking some system
privilege from a ROLE, it would be like doing that to PUBLIC is now, don't do it, just think about
it (if you do revoke some powerful system privilege from PUBLIC, do it on a test database). If
PUBLIC had been granted SELECT ANY TABLE, revoking that privilege would cause virtually every
procedure in the database to go invalid. If procedures relied on roles, virtually every procedure
in the database would constantly become invalid due to small changes in permissions. Since one of
the major benefits of procedures is the 'compile once, run many' model - this would be disastrous
for performance.
Also consider that roles may be
q    Non-default: If I have a non-default role and I enable it and I compile a procedure that
relies on those privileges, when I log out I no longer have that role -- should my procedure become
invalid -- why? Why not? I could easily argue both sides.
q    Password Protected: if someone changes the password on a ROLE, should everything that might
need that role be recompiled? I might be granted that role but not knowing the new password - I
can no longer enable it. Should the privileges still be available? Why or Why not? Again, arguing
either side of this is easy. There are cases for and against each.
The bottom line with respect to roles in procedures with Definer rights are:
q    You have thousands or tens of thousands of end users. They don't create stored objects (they
should not). We need roles to manage these people. Roles are designed for these people (end users).
q    You have far fewer application schema's (things that hold stored objects). For these we want
to be explicit as to exactly what privileges we need and why. In security terms this is called the
concept of 'least privileges', you want to specifically say what privilege you need and why you
need it. If you inherit lots of privileges from roles you cannot do that effectively. We can manage
to be explicit since the number of development schemas is SMALL (but the number of end users is
large)...
q    Having the direct relationship between the definer and the procedure makes for a much more
efficient database. We recompile objects only when we need to, not when we might need to. It is a
large efficiency enhancement.
</quote>

ORA-01031: insufficient privileges and shared memory realm does not exist

Hi all,
I came to a dead end to start oracle 10.2 database. I have searched on google and this forum, none of these solutions work for me. PS, I have installed 11g on my machine too.
I have set up ORACLE_SID,ORACLE_HOME to 10.2 database based on the tnsnames.ora.
follow is error message：
sqlplus sys as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Apr 3 02:09:54 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Enter password:
ERROR:
ORA-01031: insufficient privileges
sqlplus /nolog
SQL*Plus: Release 10.2.0.1.0 - Production on Wed Apr 3 02:10:55 2013
Copyright (c) 1982, 2005, Oracle. All rights reserved.
SQL> conn / as sysdba
ERROR:
ORA-01031: insufficient privileges
SQL> conn scott/tiger
ERROR:
ORA-01034: ORACLE not available
ORA-27101: shared memory realm does not exist
Linux-x86_64 Error: 2: No such file or directory
First I thought the instance has been start yet, but since I can't login with sysdba. I don't know what other options.
For 10.2, the tnsnames.ora
ORA102 =
+(DESCRIPTION =+
+(ADDRESS = (PROTOCOL = TCP)(HOST =XXX)(PORT = 1523))+
+(CONNECT_DATA =+
+(SERVER = DEDICATED)+
+(SERVICE_NAME = ora102)+
+)+
+)+
LISTENER_ORA102 =
+(ADDRESS = (PROTOCOL = TCP)(HOST =XXX)(PORT = 1523))+
EXTPROC_CONNECTION_DATA =
+(DESCRIPTION =+
+(ADDRESS_LIST =+
+(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC2))+
+)+
+(CONNECT_DATA =+
+(SID = PLSExtProc)+
+(PRESENTATION = RO)+
+)+
+)+
listener.ora:
SID_LIST_LISTENER =
(SID_LIST =
(SID_DESC =
(SID_NAME = PLSExtProc)
(ORACLE_HOME = /data/oracle/ora102)
(PROGRAM = extproc)
LISTENER =
(DESCRIPTION_LIST =
(DESCRIPTION =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC2))
(ADDRESS = (PROTOCOL = TCP)(HOST =XXXXX)(PORT = 1523))
EXTPROC_CONNECTION_DATA =
(DESCRIPTION =
(ADDRESS_LIST =
(ADDRESS = (PROTOCOL = IPC)(KEY = EXTPROC))
(CONNECT_DATA =
(SID = PLSExtProc)
(PRESENTATION = RO)
)

try do this steps on server side:
1) sqlplus sys as sysdba
2) select open_mode from v$database;
show result 2 step

ORA-01031 error

We have Oracle applications VIS instance.
I have Oracle 10g database installed on my PC
I made entry in tnsnames.ora & tried connecting to VIS instance using,
conn apps/apps@VIS
but this does not work for sys, like
conn sys/sys@VIS as sysdba
It throws the following error:
ORA-01031: insufficient privileges
Warning: You are no longer connected to ORACLE.
Will the problem be rectified if sys privilege is given to sys user(on my pc) from sys user(VIS instance)
Thanks in advance
Bipin

Will the problem be rectified if sys privilege is given to sys user(on my pc) from sys user(VIS instance)...there is nothing like give sys user sys privilege. And, there is nothing like 'my pc sys' and 'server sys'. Sys is ONE single user.
--Mukesh

Ora-01031 error: insufficient Priviliges

hi experts,
im was completely enervated by a simple error for which im hanging out for plenty of hours. kindly advice me what to do to eradicate it.
i have a Redhat Linux AS 4 server and 9.2.0.4 database version.
The problem is, when im trying to connect database as sysdba with netservice name, i.e using remote authentication method, i was thrown ora-01031 error: insufficient priviliges. But when i tend to connect it locally using OS authentication method it permits me to do it.
for example,
Sql> connect sys@<sid> as sysdba
Enter password:
ERROR: insufficient priviliges
where as,
Sql>conn sys as sysdba
connected
sql>
i've configured oracle in Linux environment as per the documentation. i can't figure out the exact problem. the sqlnet.ora file contains SQLNET.AUTHENTICATION_SERVICES=none
kindly tell me where im missing out?
Thanks
SM

yes. i've Password file in its appropirate location,
which is named as orapw$ORACLE_SID
and the parameter, remote_login_passwordfile is set
as EXCLUSIVE.This should be fine.
Try
- select * from v$pwfile_users; to check whether oracle sees the password file
- recreate the password file, if possible (it can get corrupted sometimes)
- delete sqlnet.ora to go with the defaults (of course, backup it first)
- check whether you can connect as usual user using the net service name (and check whether you connect to the proper database, just to be sure)
- try to connect from a different machine
- check that TWO_TASK and TNS_ADMIN environment variables are not set.

ORA-01031 error...need enter password prompt

Hi.
I'm creating a form which kills a session, using this command:
Forms_DDL('ALTER SYSTEM KILL SESSION'|| :v_$session.sid|| ',' ||:v_$session.serial# );
in my when-button-pressed trigger. But I get ora-01031 error insufficient privileges. So I'd like to prompt the user to enter his password when he tries to kill a session, because only the administrator should be able to kill a session. Thanks in advance.
-K

Hi Kristine:
First I would ask you why can't they just use the normal logon to establish their access level?
Then, let me say there is no way to just popup the logon screen in forms, however, it is relatively simple to create a signon screen. Just create a dialog popup with two fields for username and password, and a button with a label maybe "Signon". Then in the WHEN-BUTTON-PRESSED associated with Signon button, you use the code like following. Please test it and modify as needed, because I do not have a database to test it with. Note I use ... as needed to indent because the forum strips leading spaces.
DECLARE
..V_CONNECT_STRING VARCHAR2(100) :=
..........GET_APPLICATION_PROPERTY(CONNECT_STRING);
BEGIN
..LOGOUT;
..LOGON(:B1.UN, :B1.PW ||'@'|| V_CONNECT_STRING, 'TRUE');
..EXIT_FORM;
END;
Hope this helps,
Thomas

ORA-01031 in OWB deployment

Similar Messages

Maybe you are looking for