Dropping crashed indexes

I am trying to create an index on a LONG RAW column, and have had some trouble. The index creation job does not ever complete, but there are no errors.
I am trying to clean up the indexes, using the command
DROP INDEX schema.indexname FORCE;
I used force because in CTXSYS.CTX_INDEXES, the IDX_STATUS column for that index is POPULATE.
After executing the DROP INDEX command, it seems successful, but when I try to re-create the index I get this error message:
ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-20000: interMedia Text error:
ORA-00001: unique constraint (CTXSYS.DRC$IDX_COLSPEC) violated
ORA-06512: at "CTXSYS.DRUE", line 126
ORA-06512: at "CTXSYS.TEXTINDEXMETHODS", line 54
ORA-06512: at line 1
How do I thoroughly clean up these indexes?

The issue was that the index creation job was taking a very very long time (8 hrs.), and I was killing it, which I shouldn't have done, but I had to shut my laptop down.
The index creation command was:
CREATE INDEX SILVERPORTAL_ADMIN.CTX_CMDOCCONTENTS_I
on SILVERPORTAL_ADMIN.CMDOCCONTENTS( contentdata ) INDEXTYPE IS
ctxsys.context PARAMETERS('MEMORY 50M STORAGE mystore DATASTORE CTXSYS.DEFAULT_DATASTORE filter ctxsys.inso_filter format column ctx_fmt');
The mystore preference was created thusly:
ctx_ddl.create_preference('mystore', 'BASIC_STORAGE');
ctx_ddl.set_attribute('mystore', 'I_TABLE_CLAUSE',
'tablespace MARSHX01');
ctx_ddl.set_attribute('mystore', 'K_TABLE_CLAUSE',
'tablespace MARSHX01');
ctx_ddl.set_attribute('mystore', 'R_TABLE_CLAUSE',
'tablespace MARSHX01');
ctx_ddl.set_attribute('mystore', 'N_TABLE_CLAUSE',
'tablespace MARSHX01');
ctx_ddl.set_attribute('mystore', 'I_INDEX_CLAUSE',
'tablespace MARSHX01');
ctx_ddl.set_attribute('mystore', 'P_TABLE_CLAUSE',
'tablespace MARSHX01');
I got around this by manually deleting all the DR$* tables created by the index job, and simply waited the job out thereafter.
null

Similar Messages

REBUILD INDEX vs DROP/CREATE INDEX

Hi there,
Does anyone has already got some performance degradation after REBUILD INDEXes ? Would it be better to perform DROP/CREATE INDEX instead ?
Thank you very much for anu reply.
Best regards,
Helena

Hi,
>>so is it then better to DROP/CREATE them ?
Well, In fact I learned that when you rebuild an index, Oracle creates a new index from the old index and does not perform sorting while building the new index, which results in performance enhancement. In this case, depending of the size of your data it's necessary sufficient space on a tablespace for storing the old as well as the new index (while creating the new index). Other advantage, is that Oracle can use the old index for answering queries while it builds the new index too using [alter index <index_name> rebuild online].
Cheers

How to Drop an index from a used table. online

I need to drop an index from a table that is constantly used , read and write.
The DML's are locking the table and preventing the index drop (ORA-00054: resource busy and acquire with NOWAIT specified )
I tried to lock the table first - using 'lock table TAB1 in exclusive mode'
but when i ran the 'drop index' command , the drop (as all DDL's) first commits and this frees the lock which cause again the ORA-00054: resource busy and acquire with NOWAIT specified error.
I would appriciate any help .I can't take the DB or table or Application writing to the table offline. I need something like 'create index IND1 online' for DROP but there is none as far as I know...
Thanks in advanve.
Amit Zor

"It is requsted for the removal of an ORDER BY clause from a CPU consuming query.
The extra field enables me to remove it as the result set comes back ordered by the index"
It might do that today, but it is not guaranteed to do it tomorrow. Oracle may be able to retrieve the records ordered using that index, but I would leave it in your query if you are depending on the rows being ordered. The CBO is smart enough to not actually sort the rows (i.e. act on the ORDER BY clause) if it can get them sorted using the index, but if it decides to use another access path for one of many reasons your results will not be sorted without the ORDER BY.
Since the CBO seems to think that your existing index is useful (which is why you cannot get the lock on it), your only option is to wait for a period of really low activity on the database and try it then.
John

Can't drop text index (ORA-00054: resource busy) - causes?

Thanks, you were right! It works now, but I have another issue. I only added about 75 MB of PDFs (20 files) into my table, and indexed it. Indexing took about 4 minutes. But now, whenever I try to drop the index, I get this error:
ORA-00054: resource busy and acquire with NOWAIT specified
I tried waiting an hour, and it still gives me the error - it really shouldn't be doing anything. Would a memory or storage space issue cause this? I'd appreciate any help you could give. Thanks.

Try drop index <name> force

Dropping table indexes prior to using the MERGE utility

I am being asked to change the processing done when updates are being applied to the database.
Process:
1. Initial data load - Use SQL Loader to load the main database tables.
2. Daily data load - Use SQL Loader to load records to temporary tables and then use MERGE utility to insert new records and update existing records in the main database tables. Just prior to starting the MERGE utility, I drop the indexes on the main database tables. At the end of the MERGE, I re-create the indexes.
The problem seems to be the application using the database can't handle the queries if the indexes are dropped and being readded.
Does anyone have any ideas?

I am currently dropping indexes because when the MERGE processing takes place, it can insert new records or update existing records (based on the primary keys matching).
When I started to use the MERGE, I don't think the update was successful because the primary key constraint. So I disabled the primary keys indexing and other contraints during the MERGE. Then recreated at the end of the MERGE. Perhaps I need to revisit the information for MERGE.
I don't have any real benchmarking other than the application developers indicating that they experience the application processing delay during the daily load. I've thought about loading into a shadow table and rename at the end of the load but it not really be possible now.

Issue in dropping an index when doing Online Index drop and Creation

Hi All,
We have done an implementation, wherein, we are creating Online indexes and dropping them when we have a new Release, and a new build. What we do is, we take the difference in existing DB indexes and the ones present in our script, and then a script is executed which drops/modifies/creates new index.
However, what is happening is when we are carrying out some activity in our application, the script tries
to drop an index and fails with "Resource Busy and acquire with NOWAIT."
Any ideas how to handle this situation. Or should we segregate dropping of old indexes and creation of new indexes?

cause for this problem:
Resource Busy and acquire with NOWAIT:
Whenever you try to do any structural changes on a table oracle try to lock the table exclusively with NOWAIT option(this is in 10.2g while in 11g you can change the wait timeout). If oracle fails to lock the table exclusively then ORA-00054 will occur.
Solution for this: (try this link)
http://arjudba.blogspot.com/2009/01/ora-00054-resource-busy-and-acquire.html
http://oracle-error.blogspot.com/2008/10/ora-00054-resource-busy-and-acquire.html
RSD

Can I add new zone section without drop the index

Hi,
Could somebody tell me is there a way to add new zone section for XML document without drop the index and then recreate it.
Thanks

in oracle 8i version there is no need for rebuliding index for creation of zonal section. Server process started by ctxsrv
will do the dml .And later you can rebuild
the index when you make many changes to documents.(not neccessary)

Primary Key could not be changed without dropping the index

I want to change the primary key in the "alter table modus". I don't see any INDEX. I refresh the DATA and get the following error:
ORA-01785: ORDER BY-Angabe muss Positionsnummer von Ausdruck der SELECT-Liste enthalten
Version: 3.0.03 Build-03.97
Edited by: mesch181 on Apr 17, 2011 12:31 PM

That error message has nothing to do with dropping an index.
There is a bug in current versions of sql developer where the query used to populate the data grid is stored and if the table structure changes the query can be invalid. Try closing the table and re-opening it.

How to drop a index

I am trying to drop one index but its failling
SQL> select INDEX_NAME,DROPPED from dba_indexes where INDEX_NAME='XXCCI_HZ_CODE_ASSIGNMENTS_N1';
INDEX_NAME DRO
XXCCI_HZ_CODE_ASSIGNMENTS_N1 NO
SQL> Drop index XXCCI_HZ_CODE_ASSIGNMENTS_N1;
Drop index XXCCI_HZ_CODE_ASSIGNMENTS_N1
ERROR at line 1:
ORA-01418: specified index does not exist
what is the problem plz help.

Ya the Edited time and Posted times are probably correct on your computer but on mine, it shows your posted time in my timezone but your edited time in your timezone. They should keep it standard.
Posted: Sep 18, 2008 3:15 PM - RTSEN TIMEZONE
Edited by: Anand... on Sep 19, 2008 2:46 AM - ANAND TIMEZONEEdit - Sorry to the OP for redirecting the thread, i'll post this in the feedback forum to see if this is an error.
Edited by: rkhtsen on Sep 18, 2008 3:36 PM

Change index's columns without drop the index

Hi all,
I would like to know whether is possible to remove columns from index without having to drop the index. If the answer is yes could you tell me what is the command?
Thanks,
Dani

Thank you Leo for the confirmation.
Cheers,
Dani

Predefined transformations for drop/create index?

Hi,
I want to add pre/postmap transformations for dropping/recreating indexes in the target table, for performance reasons.
I can't find any predefined transformations for this (such as WB_DISABLE/ENABLE_ALL_CONSTRAINTS for constraints). It seems I have to program this myself (dynamic PL/SQL for reuse with other tables seems the logical choice), but it seems such a dumb oversight - has Oracle really not supplied predefined transformations for this? It must be an extremely common need in ETL?
Regards,
Kai Quale
University of Oslo

On further thought, one needs more information than the table name to (re)create an index. (That's actually one of my pet peeves against Oracle - that you can't enable/disable indexes in the same way as constraints.)
Offhand, the only solution I see is to store index metainformation in a separate table, write custom procedures for disabling FKs/dropping indexes and enabling FKs/creating indexes, using the metatable.
It is a pretty common task in data warehousing - disable FK/drop index => run mapping => enable FK/create index. How do people do this in OWB?
Regards,
Kai

Does dropping bitmap index and creation of b- index cause any dead locks

Does dropping a bitmap index on table which is being used continuously for DML operations and creation of b- index cause any dead locks on a table
in oracle 10g database
( 10.1.0.4.0 - 64bi).
we have seen alert log file which has dead lock occurrence.. would index change/re-creation resulted dead lock or some other reason?
Could you please give us info or help us on this.. thanks in advance..

Bitmap indexes can be the cause of deadlocks on busy systems.
Dropping indexes may cause some locking.
Creating indexes may cause some locking.
You haven't given any traces or scripts or lock information, so difficult to say which one (if any) was the cause of your deadlocks.
It would be better to do this activity when the system is not busy.

Dock Downloads Folder Drag & Drop Crashes Finder

When attempting to Drag & Drop files from the Downloads folder in the Dock to a different folder, whether that folder be on the Desktop, or open in a Finder window, Finder crashes and relaunches. Sometimes the file gets placed, sometimes it remains in the Dock. I have a similar problem with Mountain Lion on my 13" MBP, although Finder does not crash, it simply won't allow files to be dragged from the Dock to a folder icon on the Desktop.
This problem has been persistent through several updates, and has been present since upgrading to Lion, and is a problem on more than one computer. This does not happen with every file, but happens often enough to be frustrating. It also happens consistently when moving more than 2 files from the Downloads folder in the Dock to either the Desktop, or a folder. I am also unable to Drag & Drop a file from the Downloads (or Documents folder for that matter...) to any folder icon on the desktop.
I attempted this morning to file a bug report with Apple, but the Bug Reporting site had an error, and the Home Button on the Error page does nothing (hooray for web design!).

Step one is to log into a newly created admin user account and see if the problem persists.
As for the BR issue, https://bugreport.apple.com/cgi-bin/WebObjects/RadarWeb.woa/wa/signIn loads w/o issues.

Dropping/Creating index for an individual partition on a partitioned table.

Hi,
I wanted to know how to create and drop index for a single individual partition on a partitioned table.
Thanks..

You are not allowed to create an index on a single partition. All the table, mean all the partitiones must be indexed. You can create local or global indexes on partitioned tables. Local indexes ,imho, are easier maintained. For more info refer to documentation http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_5010.htm#i2062403
Also, index partitions are maintained through corresponding table partitions. For example, if a table partition is truncated or is dropped, the corresponding index partition is also truncated or dropped (in case of locally partitioned indexes of course). In case of globally partitioned indexes, you will have to rebuild the index each time you truncate or drop a table partition.

While dropping table, INDEXES created by us, note, not by oracle, does not drop.

Hellow Friends,
I want to know when we drop the table, the indexes created on it does not drop with it. Offcourse I know the indexes which are created when we give constraints on columns drops.
Have you got my point, I am talking about those indexes which are created by us time to time according to our needs.
Thankyou
Sumeet

Hellow Armold,
I tried
drop table <table_name>;
ThankYou
Sumeet

Dropping crashed indexes

Similar Messages

Maybe you are looking for