Insufficient priviledge when creating index

upon creating new indexes, using the command :
create index im_art_s_idx_2 on article(cl_story)
indextype is ctxsys.context;
i get the following error :
create index im_art_s_idx_2 on article(cl_story)
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE
routine
ORA-20000: interMedia Text error:
ORA-01031: insufficient privileges
ORA-06512: at "CTXSYS.DRUE", line 126
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54
ORA-06512: at line 1
I can, however create normal indexes (i.e. by not specifying
the indextype argument). Has anybody got any idea what this
could be about?

grant to user who's gonna create the index CTXAPP
grant ctxapp to xxxx;

Similar Messages

Can't select "include book documents" when creating index in InDesign CC

I'm trying to make an index for several dokuments in a book. I've made the index but when I try to generate the index the checkbox is greyed out so I can't check it. Do You know what's wrong?

Thank You. That worked well.
One more question: It looks as if the index does not include the words of all the documents in the book. Is it something I do wrong?
Thanks
Henning
Fra: Peter Spier <[email protected]<mailto:[email protected]>>
Svar til: "[email protected]<mailto:[email protected]>" <[email protected]<mailto:[email protected]>>
Dato: onsdag 10. juli 2013 13:04
Til: Henning Kristoffersen <[email protected]<mailto:[email protected]>>
Emne: Can't select "include book documents" when creating index in InDesign CC
Re: Can't select "include book documents" when creating index in InDesign CC
created by Peter Spier<http://forums.adobe.com/people/P+Spier> in InDesign - View the full discussion<http://forums.adobe.com/message/5491834#5491834

Insufficient privileges when creating MV with alter session set current_sch

I am getting Insufficient privileges when creating MV with alter session set current_schema=Application schema name. User running the alter session is DBA user. If run as SYSDBA, MV is created successfully. DB Version is 10.2.0.3
I observed similiar issue with regular View also in 9.2.0.6 also.
Any advice is greatly appreciated.
Thanks,
Siva

Sounds like your management needs a stern lecture on the concept of change management. <g>
I am not debating what you do. I am questioning the logic, or lack thereof, of doing it that way. My recommendation would be to change your procedure to one that:
A. Is more in line with good change management practices.
B. Works.

Error when creating index with parallel option on very large table

I am getting a
"7:15:52 AM ORA-00600: internal error code, arguments: [kxfqupp_bad_cvl], [7940], [6], [0], [], [], [], []"
error when creating an index with parallel option. Which is strange because this has not been a problem until now. We just hit 60 million rows in a 45 column table, and I wonder if we've hit a bug.
Version 10.2.0.4
O/S Linux
As a test I removed the parallel option and several of the indexes were created with no problem, but many still threw the same error... Strange. Do I need a patch update of some kind?

This is most certainly a bug.
From metalink it looks like bug 4695511 - fixed in 10.2.0.4.1

Error when create index

Hi,
Platform Tru64 BD 8.1.7.
When i create some index for intermedia search, i get some errors:
CREATE TABLE DOCUMENTO (
ID NUMBER (15) NOT NULL,
NOME VARCHAR2 (100) NOT NULL,
DESCRICAO VARCHAR2 (255),
FORMATO VARCHAR2 (128),
AUTOR VARCHAR2 (100),
RESPONSAVEL VARCHAR2 (100) NOT NULL,
DATA_DOCUMENTO DATE,
DATA_CATALOGACAO DATE DEFAULT SYSDATE NOT NULL,
ESTADO VARCHAR2 (2) DEFAULT 'AC' NOT NULL,
DOCUMENTO BLOB,
INTERMEDIA VARCHAR2 (4000),
NAME VARCHAR2 (90),
CRIADO_POR VARCHAR2 (90),
CRIADO_EM DATE,
ALTERADO_POR VARCHAR2 (90),
ALTERADO_EM DATE,
CONSTRAINT ESTADO_CK
CHECK (ESTADO IN ('AC','AN')) ,
CONSTRAINT ID_CONSTRAINTS
UNIQUE (ID),
PRIMARY KEY ( ID ));
CREATE INDEX DOCUMENTO_INDEX ON
DOCUMENTO(DOCUMENTO);
ERROR at line 2:
ORA-02327: cannot create index on expression with datatype LOB
CREATE INDEX INTERMEDIA_INDEX ON
DOCUMENTO(INTERMEDIA);
ERROR at line 2:
ORA-01450: maximum key length (1578) exceeded
Could you give me some help?

Forget last message, i forget to specify index type
Pedro Ribeiro

Oracle Error when creating indexes

Help!! I'm getting an error on a spatial create. I read the documents here on this error and I've tried every suggestion.
1. Plenty of free space in the tablespace indx
2. Plenty of free space in the temp tablespace
Does anyone have any ideas??
Thanx in Advance..
Frank
SQL> CREATE INDEX iseechart_geometry_idx ON iseechart (isee_geometry)
2 INDEXTYPE IS MDSYS.SPATIAL_INDEX
3 PARAMETERS('TABLESPACE=INDX SDO_INDX_DIM=2');
CREATE INDEX iseechart_geometry_idx ON iseechart (isee_geometry)
ERROR at line 1:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-13249: internal error in Spatial index: [mdidxrbd]
ORA-13249: Error in Spatial index: index build failed
ORA-13236: internal error in R-tree processing: [failed to cluster in memory]
ORA-13249: Internal error in Spatial index: [mdrcrclmem]
ORA-06512: at "MDSYS.SDO_INDEX_METHOD_9I", line 7
ORA-06512: at line 1

Hi Frank,
When you specified "sdo_indx_dim" instead of "sdo_indx_dims",
the parser is ignoring the parameter. Since the default
is 2, it still works fine.
Regarding sdo_rtr_override:
Glad that the workaround helped. This is a non-documented parameter
for R-tree that gives a workaround for any possible bugs that
are introduced as part of new features in new releases. Given
the nature of spatial, there could be some data-specific bugs. In 9.2,
there are some new clustering improvements (internal) and guessing
from the error stack the new one is running out of some stack space
internally due to data outliers (does not occur in all datasets though).
The sdo_rtr_override=0 defaults the behavior of the current operation
(create-index or query) to prior releases (like 9.1). This parameter
allows the users to work uninterrupted while things improve in new
releases. The behavior of this parameter should not be used to compare
performance etc. in different versions though and should be used only
as a workaround. (It is not documented due to these implications
and only recommended when needed by spatial).
Spatial will definitely try to improve on the error messages.
Please file a bug with some sample data or send Oracle
the data at the earliest so that this can be fixed properly.
- Ravi.

Using hint when creating index

Hi,
is it possible to use a hint when creating an index.
for example normally when creating an index, optimizer does full table scan, but i want it to use a different index to walk through the table.
any ideas?
technically impossible?

If the new index is a subset of an existing index, Oracle should be able to read the existing index to create the new index.
However, if the index consists of such a combination of columns that one or more is not in the subset then it has to read all the rows of the table.
Hemant K Chitale

InterMedia Error when creating Index

Sorry, the error texts are in French, hopefully someone will help me.
I have checked listner.ora and tnsmanes.ora: they look fine, (however, we have ....KEY=EXTPROC)), not EXTPROC0 as it appears sometimes in the doc) but something must be wrong someplace.
Seems to be related to another question in this forum.
Thanks for any help.
(actually, when running from sql worksheet, I get a Net8 listener ids not running or cannot start external procedure ??
create index quick_text on kd.kd_enseigne(desc_long) indextype is ctxsys.context
ORA-29855: erreur d'exZcution de la routine ODCIINDEXCREATE
ORA-20000: erreur interMedia Text :
DRG-11422: initialisation des services linguistiques impossible
DRG-00100: internal error, arguments : [52100],[drxs.c],[557],[gxtopen],[0]
ORA-06512: S "CTXSYS.DRUE", ligne 126
ORA-06512: S "CTXSYS.TEXTINDEXMETHODS", ligne 54
ORA-06512: S ligne 1
SVRMGR>

<BLOCKQUOTE><font size="1" face="Verdana, Arial, Helvetica">quote:</font><HR>Originally posted by Omar Alonso:
Please post db version and platform. Are you sure the listener is running?<HR></BLOCKQUOTE>
db version is 8.1.5, platform is Linux.
By running the check script we saw that the cartridge was invalid. We had to reinstall anither instance, now it works.
Thank you.

ORA-19025: EXTRACTVALUE returns value of only one nod- When creating index

Hi,
My table have 2 columns . Columns are
Key varchar2(50)
Attribute XMLType
Below is my sample XML which is stored in Attribute column.
<resource>
<lang>
<lc>FRE</lc>
<lc>ARA</lc>
</lang>
<site>
<sp>257204</sp>
<sp>3664</sp>
</site>
<page>
<pp>64272714</pp>
<pp>64031775</pp>
<pp>256635</pp>
</page>
<key>
<kt>1</kt>
</key>
</resource>
When i try to create a index on XML column and i am getting the above exception. kindly help me out becz i'm not familar with oracle.
Query is
create index XMLTest_ind on language_resource_wrapper
(extractValue(attribute, '/resource/site/sp') )
index on sp,pp elements in the above XML.

Thanks for the suggestion...
The problem is that in one row, information in a data dump about two different things was combined into one, due to a gap in the input file. The starting delimiter for the second thing and the ending delimiter for the first were missing. The result was that many entity tags that should have been unique were duplicated, ion that particular row.
I was able to guard the view against future such errors with occurrences using this
in the WHERE clause ...
AND NOT ( XMLCLOB LIKE '%<TAG1>%<TAG1>%'
OR XMLCLOB LIKE '%<TAG2>%<TAG2>%'
OR XMLCLOB LIKE '%<TAG3>%<TAG3>%'
/* ... Repeated once for each tag used with extractvalue */
OR XMLCLOB LIKE '%<TAGN>%<TAGN>%'
It filters out any row with two identical starting tags, where one is expected.
I am pleased to see that the suggestion got through.

Insufficient Privileges when create materialized view as user system

If I login as system (connect sys/****@DevDB) and try to create a materialized view for another schema (e.g. XDCONTROLDB), I get the insufficient privileges error. If I login as sys as sysdba then I can create successfully.
I have searched some ariticles in Google and grant create any snapshot, create any table, create any view, global query rewrite, select any table system privileges to system but still get the same error.
Any other privileges I need to grant to system?
Cheers
below is a sample script to create the view which get the error:
CREATE MATERIALIZED VIEW XDControlDB."XDTest1" PCTFREE 10
PCTUSED 0 MAXTRANS 255
STORAGE ( INITIAL 64K NEXT 0K MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0)
TABLESPACE "USERS"
BUILD IMMEDIATE
REFRESH COMPLETE START WITH sysdate NEXT sysdate + 1/24
ENABLE QUERY REWRITE AS
SELECT * From XDControlDB.RiskInstance;
Message was edited by:
user500168
Message was edited by:
user500168

Thanks for your reply. After I grant privileges to system, I login as system and try to create the view as below which I get the insufficient privileges error:
CREATE MATERIALIZED VIEW XDControlDB."XDTest1" PCTFREE 10
PCTUSED 0 MAXTRANS 255
STORAGE ( INITIAL 64K NEXT 0K MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0)
TABLESPACE "USERS"
BUILD IMMEDIATE
REFRESH COMPLETE START WITH sysdate NEXT sysdate + 1/24
ENABLE QUERY REWRITE AS
SELECT 1 From XDControlDB.RiskInstance;
As you can see, I try to create the view under a schema called 'XDCONTROLDB'. If I login as sys as sysdba, then it create successfully.
After I create UserA, and grant the privileges I mentioned in the ealier post, I login as UserA, and run the statement above I get the same privileges error. But if I change the stament to below which will create the view under UserA's schema, then it create successfully:
CREATE MATERIALIZED VIEW UserA."XDTest1" PCTFREE 10
PCTUSED 0 MAXTRANS 255
STORAGE ( INITIAL 64K NEXT 0K MINEXTENTS 1 MAXEXTENTS
2147483645 PCTINCREASE 0)
TABLESPACE "USERS"
BUILD IMMEDIATE
REFRESH COMPLETE START WITH sysdate NEXT sysdate + 1/24
ENABLE QUERY REWRITE AS
SELECT 1 From XDControlDB.RiskInstance;
Looking for your suggestions,
Cheers

ORA-01031: insufficient privileges when creating a table in other schema

Dear all,
I appreciate your help please in this issue :
when i try to issue the below statement to create a table in an another schema than the user i am connected in
CREATE TABLE SCHEMA_NAME_B.HST_ARCH nologging AS
SELECT *
FROM HST
WHERE 1 = 0;
I always get ORA-01031: insufficient privileges error, even if i have granted the create table privilege to the user i am connected in.
What other privileges should i grant also,
Please if you have any idea.

user562674 wrote:
Dear all,
I appreciate your help please in this issue :
when i try to issue the below statement to create a table in an another schema than the user i am connected in
CREATE TABLE SCHEMA_NAME_B.HST_ARCH nologging AS
SELECT *
FROM HST
WHERE 1 = 0;
I always get ORA-01031: insufficient privileges error, even if i have granted the create table privilege to the user i am connected in.
What other privileges should i grant also,
Can you show us a cut/paste from the sql*plus of session of yours which should show that you have given the privilege directly to this user and after that the command fails?
Aman....

4.0 EA2 - Insufficient Privileges When Creating Object With Proxy

When I have connected by proxying to another user, I receive the following message when trying to create a new object:
The database user has insufficient privileges for the given operation.
Steps to reproduce:
Connect by proxying to another user
Right Click on Views
Select New View
I noticed this under EA1, though, not sure if reported. This worked under 3.2.2

Sounds like your management needs a stern lecture on the concept of change management. <g>
I am not debating what you do. I am questioning the logic, or lack thereof, of doing it that way. My recommendation would be to change your procedure to one that:
A. Is more in line with good change management practices.
B. Works.

Insufficient privileges when creating user logged in as SYS

Hi,
I'm working on 11.1.0.6.0 Enterprise Edition, Advanced Security options, Label Security a and Database Vault installed. (for testing purposes)
I'm creating a new user being logged as SYS using this sentence:
CREATE USER "HR_DIRECTOR" PROFILE "DEFAULT" IDENTIFIED BY "*******" DEFAULT TABLESPACE "USERS" TEMPORARY TABLESPACE "TEMP" ACCOUNT UNLOCK;
However, the command fails with the message "Failed to commit: ORA-01031: insufficient privileges . You do not have enough privileges to perform this operation. You must have the appropriate system and object privileges to create, edit, or drop database objects or objects outside of your schema."
Please note that I'm working on a fresh DB install and I have also installed Database Vault in this instance for testing purposes, but still haven't configured any realm or command rules on it.
Is it possible Vault is the reason why I am not able to create a new user?
Thanks and Regards,
Leandro

Hi, It seems I've found it.
After you install Database Vault and associate it with your SID, SYS user is revoked the CREATE USER system privilege.
Only a user with the DV_ACCTMGR role may create, alter or drop a user. This is done in order to separate responsabilities in your database. A SYS user cannot grant himself this role or the DV_OWNER role.
(If interested, check page 10-4 from http://www.oracle.com/pls/db111/to_toc?pathname=server.111/b31222/toc.htm)
Regards,
Leandro

Insufficient Permission When Creating Standby

I have a remote server which I believe I have prepped appropriately. I have installed grid infrastructure /w ASM, and database software. I have created a virtually blank initMyDB.ora file with a single parameter (db_name) as per docs. I start that skeletal database instance in NOMOUNT mode.
I go to RMAN and try to connect to the primary as SYS. It connects easily.
I try to connect to the local instance as SYS. It gives me the "ora-01031 insufficient privileges" error.
I can, of course, log into +ASM and change the SYS password/change permissions/etc, but I cannot log into the skeletal instance and do anything to SYS as the db is in NOMOUNT mode.
I'm a Data Guard newcomer, so what am I doing wrong? DB is 11r2 and OS is RHEL 5.
Thanks

893968 wrote:
I have a remote server which I believe I have prepped appropriately. I have installed grid infrastructure /w ASM, and database software. I have created a virtually blank initMyDB.ora file with a single parameter (db_name) as per docs. I start that skeletal database instance in NOMOUNT mode.
I go to RMAN and try to connect to the primary as SYS. It connects easily.
I try to connect to the local instance as SYS. It gives me the "ora-01031 insufficient privileges" error.
I can, of course, log into +ASM and change the SYS password/change permissions/etc, but I cannot log into the skeletal instance and do anything to SYS as the db is in NOMOUNT mode.
I'm a Data Guard newcomer, so what am I doing wrong? DB is 11r2 and OS is RHEL 5.
ThanksHi,
In a Data Guard configuration, all physical and snapshot standby databases must use a copy of the password file from the primary database,
and that copy must be refreshed whenever the SYSOPER or SYSDBA privilege is granted or revoked,
and after the password of any user with these privileges is changed.
Regards
Mahir M. Quluzade

Creating index for standard SAP tables

Hi!
What are the advantages and disadvantages of creating addtional indexes for tables with massive amount of data (BSEG, BKPF, COEP, etc...).
If I create a new index it supposed to make the table access faster, for the cost of hard disk space.
Am I right?
Thank you
Tamá

Hi,
Primary and secondary indexes
Index: Technical key of a database table.
Primary index: The primary index contains the key fields of the table and a pointer to the non-key fields of the table. The primary index is created automatically when the table is created in the database.
Secondary index: Additional indexes could be created considering the most frequently accessed dimensions of the table.
Structure of an Index
An index can be used to speed up the selection of data records from a table.
An index can be considered to be a copy of a database table reduced to certain fields. The data is stored in sorted form in this copy. This sorting permits fast access to the records of the table (for example using a binary search). Not all of the fields of the table are contained in the index. The index also contains a pointer from the index entry to the corresponding table entry to permit all the field contents to be read.
When creating indexes, please note that:
An index can only be used up to the last specified field in the selection! The fields which are specified in the WHERE clause for a large number of selections should be in the first position.
Only those fields whose values significantly restrict the amount of data are meaningful in an index.
When you change a data record of a table, you must adjust the index sorting. Tables whose contents are frequently changed therefore should not have too many indexes.
Make sure that the indexes on a table are as disjunctive as possible.
(That is they should contain as few fields in common as possible. If two indexes on a table have a large number of common fields, this could make it more difficult for the optimizer to choose the most selective index.)
Accessing tables using Indexes
The database optimizer decides which index on the table should be used by the database to access data records.
You must distinguish between the primary index and secondary indexes of a table. The primary index contains the key fields of the table. The primary index is automatically created in the database when the table is activated. If a large table is frequently accessed such that it is not possible to apply primary index sorting, you should create secondary indexes for the table.
The indexes on a table have a three-character index ID. '0' is reserved for the primary index. Customers can create their own indexes on SAP tables; their IDs must begin with Y or Z.
If the index fields have key function, i.e. they already uniquely identify each record of the table, an index can be called a unique index. This ensures that there are no duplicate index fields in the database.
When you define a secondary index in the ABAP Dictionary, you can specify whether it should be created on the database when it is activated. Some indexes only result in a gain in performance for certain database systems. You can therefore specify a list of database systems when you define an index. The index is then only created on the specified database systems when activated
Thanks and Regards
Arun Joseph

Insufficient priviledge when creating index

Similar Messages

Maybe you are looking for