Oracle Error 14063
Library mySQL Code Library PHP Code Library JavaScript Code Library Oracle Terms & Definitions Oracle Error Codes PSOUG Community Blogs Oracle Jobs Board PSOUG Forum Oracle User Group Directory Free Oracle Magazines Online Learning Center PSOUG Presentations Advanced Code Search News and Events Sponsors Page Submit Code Contact Us Oracle Error: ORA-14063 Error Description: Unusable index exists on unique/primary constraint key Error Cause: User attempted to add or enable a primary key/unique constraint on column(s) of a table on which there exists an index marked Index Unusable. Action: Drop the existing index or rebuild it using ALTER INDEX REBUILD. There haven't been any comments added for this error yet. You may add one if you like. Add a comment Name: Email: URL: Chars left:1000 (1000 max) (No HTML, but newlines will be preserved) Home : Code Library : Sponsors : Privacy : Terms of Use : Contact Us 71 users online © 2009 psoug.org PSOUG LOGIN Username: Password: Forgot your password?
»Databases »ORA-14063: Unusable index exists on unique/primary constraint key Pages 1 You must login or register to post a reply Topic RSS feed Posts [ 11 ] 1 Topic by PaulEr 2012-05-05 11:09:27 PaulEr Member Offline Registered: 2012-05-02 Posts: 2,807 Topic: ORA-14063: Unusable index exists on unique/primary constraint key IMP-00017: following statement failed with ORACLE error 14063: "ALTER TABLE" TEST_BIT "ADD CONSTRAINT" TEST_BIT_PK "PRIMARY KEY (" ID ") USI" "NG INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE (INITIAL 65536 FREELISTS" "1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE" USERS "LOGGING" IMP-00003: http://psoug.org/oraerror/ORA-14063.htm ORACLE error 14063 encountered ORA-14063: Unusable index exists on unique/primary constraint key Hello! Faced here such problem, at circuit import. Overcame by means of import of the circuit without constraint, then rebuild to all indexes, after that import of all . Whether there is any else decision? Thanks. 2 Reply by Viewer 2012-05-05 11:20:27 Viewer Member Offline Registered: 2004-02-04 Posts: 4,594 Re: ORA-14063: http://www.progtown.com/topic547299-ora14063-unusable-index-exists-on-uniqueprimary-constraint-key.html Unusable index exists on unique/primary constraint key 1. For the first time we import with an option ignore=y2. rebuild indexes3. Repeated import with an option ignore=y rows=n 3 Reply by PaulEr 2012-05-05 12:03:28 PaulEr Member Offline Registered: 2012-05-02 Posts: 2,807 Re: ORA-14063: Unusable index exists on unique/primary constraint key Thanks big! Only something does not quit a stone floret imp file=C:\ROZN.dmp log=C:\rozn1.log fromuser=ROZN touser=TEST ignore=y rows=n Does not add defined constraint - (referential).In a broad gull: IMP-00017: following statement failed with ORACLE error 14063: "ALTER TABLE" TEST_BIT "ADD CONSTRAINT" TEST_BIT_PK "PRIMARY KEY (" ID ") USI" "NG INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 STORAGE (INITIAL 65536 FREELISTS" "1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE" USERS "LOGGING" IMP-00003: ORACLE error 14063 encountered ORA-14063: Unusable index exists on unique/primary constraint key 4 Reply by Blockhead 2012-05-05 12:13:28 Blockhead Member Offline Registered: 2003-04-27 Posts: 1,839 Re: ORA-14063: Unusable index exists on unique/primary constraint key the circuit on existence UNUSABLE - indexes. 5 Reply by Blockhead 2012-05-05 12:15:29 Blockhead Member Offline Registered: 2003-04-27 Posts: 1,839 Re: ORA-14063: Unusable index exists on unique/primary constraint key It to you for an exam
any loss suffered as a result of following https://asktom.oracle.com/pls/apex/f?p=100:11:0::::P11_QUESTION_ID:16429483554360 any of this blog posts.. Happy Learning... Sunday, February 21, 2016 ORA-14063: Unusable index exists on unique/primary constraint key ########################## ## Error ########################## ORA-14063: Unusable index exists on unique/primary constraint key ### Full Error oracle error Processing object type DATABASE_EXPORT/SCHEMA/TABLE/CONSTRAINT/CONSTRAINTORA-39083: Object type CONSTRAINT failed to create with error:ORA-14063: Unusable index exists on unique/primary constraint keyFailing sql is:ALTER TABLE "ABC_OWNER"."ABC_TABLE" ADD CONSTRAINT "ABC_TABLE_PK" PRIMARY KEY ("RULE_NAME") USING INDEX "ABC_OWNER"."ABC_TABLE_PK" ENABLEORA-39083: Object type CONSTRAINT failed to create with error:ORA-14063: Unusable oracle error 14063 index exists on unique/primary constraint key ########################## # Error Occurred ########################## Error occured while doing a full import in 11.2.0.4.0 version ########################## ## Command Executed ########################## Schema level import command. **************************************** Step By Step Analysis ****************************************************** ######################################### # 1) Check index status in Source Database ######################################### #### Check the indexes which are not VALID in Source Database. SET LINES 200 col owner for a15 col index_type for a15 col tablespace_name for a15 col table_owner for a15 Select owner,index_name,index_type,table_owner,table_name,table_type,tablespace_name,status,LAST_ANALYZED from dba_indexes where STATUS='UNUSABLE'; OWNER INDEX_NAME INDEX_TYPE TABLE_OWNER TABLE_NAME TABLE_TYPE TABLESPACE_NAME STATUS LAST_ANAL--------------- ------------------------------ --------------- --------------- ----------------------
21, 2007 - 11:23 am UTC Category: Database � Version: 9.1.2 Whilst you are here, check out some content from the AskTom team: PL/SQL Brain Teaser: Find all the hard-codings! Latest Followup You Asked If I disable PK on a table, the Oracle will drop an index used for enforcing uniqueness, all information about that index will disappear from dba_indexes, dba_ind_columns. If I enable the PK, it will recreate the index with the same name and parameters as it was before. my question is, where is the information about an index stored during the PK is disabled? Thanks, Jan and we said... It uses the defaults - it is not "keeping" the original information anywhere. That -- and it doesn't "have" to drop the index either. Consider: ops$tkyte@ORA9IR2> create table t ( x int ); Table created. ops$tkyte@ORA9IR2> create index t_idx on t(x); Index created. ops$tkyte@ORA9IR2> alter table t add constraint t_pk primary key(x); Table altered. here the index is named t_idx and the constraint t_pk, we know t_idx is the constraint index because: ops$tkyte@ORA9IR2> drop index t_idx; drop index t_idx * ERROR at line 1: ORA-02429: cannot drop index used for enforcement of unique/primary key ops$tkyte@ORA9IR2> alter table t disable constraint t_pk KEEP INDEX; Table altered. ops$tkyte@ORA9IR2> select index_name from user_indexes; INDEX_NAME ------------------------------ T_IDX so that shows the index doesn't have to disappear, but we can make it go away now: ops$tkyte@ORA9IR2> drop index t_idx; Index dropped. ops$tkyte@ORA9IR2> alter table t enable constraint t_pk; Table altered. ops$tkyte@ORA9IR2> select index_name from user_indexes; INDEX_NAME ------------------------------ T_PK and when we re-enable, it named the index by the default name... Reviews Write a Review Which index is grabbed? May 13, 2004 - 11:01 am UTC Reviewer: Ivan from OH Besides just trying the drop index, is there a query to show which index enforces the constraint for the table? When I do the following,