Creation of a PK via Create Unique Index key more OR through PK restrict only

Similar Questions

• Error ' t CREATE UNIQUE INDEX W_PROD_CAT_DH_U1 ON W_PROD_CAT_DH

  Hello

  I use OLIVIER 7.9.6.4

  and EBS Instance ORA12.1.3

  I get below error when I tried to run full load for the DAC order management

  CREATE A UNIQUE INDEX

  W_PROD_CAT_DH_U1

  WE

  W_PROD_CAT_DH

  (

  INTEGRATION_ID Asc

  DATASOURCE_NUM_ID Asc

  EFFECTIVE_FROM_DT Asc

  )

  NOLOGGING

  ORA-01452: cannot CREATE a UNIQUE INDEX. duplicate keys found

  Among the responsible 1,45,423 records 24 140 are duplicated.

  Apart from the removal of duplicates of records in DB is there any changes that I can do in Informatica mapping to limit duplicate records to be loaded into DB.

  Any question even face to face only one?

  Kind regards

  NN.

  Hello

  For those who have faced the question above.

  Here is the Solution.

  1. Informatica PowerCenter Designer, place you in the SIL_Vert\Mappings folder and open the "SIL_ProductCategoryDimension_Hierarchy" mapping in the mapping Designer tool.
  2. Change the qualifier Source SQ_W_PRODCAT_DS to display the dialog box change Transformations and switch to the Properties tab.
  3. Select the name of the attribute processing Sql Query and edit the substitution of sql to change the status of outer join left in w_product_d as:
  4. DATABASE W_PRODCAT_DS
  5. LEFT OUTER JOIN W_PRODUCT_D PROD ON
  6. BASE. PROD_ID = PROD. INTEGRATION_ID AND PROD. CURRENT_FLG = 'Y '.
  7. Save the details and archive.

  
  

  The changes described above helped me load management command successfully.

  
  

  Kind regards

  NN.
  

  
  

• Implementation error on step "Create Unique Index on flow table.

  Hello
  
  I'm getting following error on execution of the interface. It simple interface with text file as source and oracle table as the target. Primary key has been set on the Empno column in the target. I tried to use all the CKM but error remains the same. I disabled the journaling option as well. Here is the statement that it generates for unique indexes
  
  create a unique index ABC. "I have _Emp$ 'idx '.
  on ABC. "" I have$ _Emp ' ('Empno')
  
  
  I did not understand why she strives to create a unique index on the flow table, even when I turn off the option in CKM for does not create index. Even more later, I tried with the evolution of the seam, but error remains same. Initially, I tried with Oracle CKM (Create Index for the I$ Table), then turned off the option to create indexes, then tried out with CKM SQL and Oracle CKM, but result is the same.
  
  
  Any help is appreciated.
  
  Thank you
  -CHikk
  
  
  911: 42000: java.sql.SQLException: ORA-00911: invalid character
  
  java.sql.SQLException: ORA-00911: invalid character
  
  
  at oracle.jdbc.driver.DatabaseError.throwSqlException(DatabaseError.java:125)
  
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:316)
  
  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:282)
  
  at oracle.jdbc.driver.T4C8Oall.receive(T4C8Oall.java:639)
  
  at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:185)
  
  at oracle.jdbc.driver.T4CPreparedStatement.execute_for_rows(T4CPreparedStatement.java:633)
  
  at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1086)
  
  at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:2984)
  
  at oracle.jdbc.driver.OraclePreparedStatement.executeUpdate(OraclePreparedStatement.java:3057)
  
  at com.sunopsis.sql.SnpsQuery.executeUpdate (SnpsQuery.java)
  
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.execStdOrders (SnpSessTaskSql.java)
  
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTaskTrt (SnpSessTaskSql.java)
  
  at com.sunopsis.dwg.dbobj.SnpSessTaskSqlI.treatTaskTrt (SnpSessTaskSqlI.java)
  
  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask (SnpSessTaskSql.java)
  
  at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep (SnpSessStep.java)
  
  at com.sunopsis.dwg.dbobj.SnpSession.treatSession (SnpSession.java)
  
  at com.sunopsis.dwg.cmd.DwgCommandSession.treatCommand (DwgCommandSession.java)
  
  at com.sunopsis.dwg.cmd.DwgCommandBase.execute (DwgCommandBase.java)
  
  at com.sunopsis.dwg.cmd.e.i (e.java)
  
  at com.sunopsis.dwg.cmd.g.y (g.java)
  
  at com.sunopsis.dwg.cmd.e.run (e.java)
  
  at java.lang.Thread.run (unknown Source)

  Hello

  Just go to the topology, the physical Architecture, right-click on Oracle technology and another tab change the delimiter 'object' for nothing...

  That will fix it.

• How to find duplicate keys found when error ORA-01452: cannot CREATE a UNIQUE INDEX.

  Hi gurus,

  I fall for this stupid error

  "cannot CREATE a UNIQUE INDEX; duplicate keys found.

  
  

  It is that the Unique Index key is composed of multiple columns

  CREATE A UNIQUE KEY001AUTORISATIONS_APPORT ON TFT_AUTORISATIONS_APPORT INDEX

  (AUT_APPORTEUR, AUT_AGENCE, AUT_PRODUIT, AUT_OPTION, AUT_TARIF, AUT_DATE_AUTORISATION)

  TABLESPACE KEYS_TFT NOPARALLEL NOLOGGING

  Now,.

  My question is, how to find duplicates keys blocking Index creation?

  Thanks if you can help

  Run this query to display the list of the duplicates already existing.

  Select AUT_APPORTEUR, AUT_AGENCE, AUT_PRODUIT, AUT_OPTION, AUT_TARIF, AUT_DATE_AUTORISATION, count (1) as cnt

  of TFT_AUTORISATIONS_APPORT

  Group

  AUT_APPORTEUR, AUT_AGENCE, AUT_PRODUIT, AUT_OPTION, AUT_TARIF, AUT_DATE_AUTORISATION

  view count (1) > 1

  Concerning

  NJ

• Re-create all indexes on new data files

  Hello

  on FSCN 9.2 on Win 2008

  We'll re-create all indexes (belonging to sysadm) in the new data files.

  -Are there any script or utility to do this?

  -can you offer me any scenario?

  Otherwise, I think only of:

  0-extract DDL for all areas of storage and index.

  1-drop tablesapces

  2 Create tablespaces (by the DBMS_GETDLL script ('TABLESPACE'...)

  3 re-create all indexes (by the DBMS_GETDLL script ('INDEX',...))

  4 rebuild all indexes.

  Any idea?

  Thank you.

  of 786997.1

  There is no trace of PeopleTools that stores the name of the tablespace for the index.

  Here's how to work the tablespaces.

  There is a table called PSDDLMODEL where we store the information of DOF model for index and table creation, among other things. DDL models contain a template with replaceable parameters. One of the parameters in the create index Oracle is a field called INDEXSPC. This field by default is PSINDEX.

  If you wish to override this value, you can go in the App Designer, open a folder, select Tools-> data Administrations-> select Index to edit the index and then select modify DDL, then select change the setting for the Create Index and Create Unique Index model. This replaces PSINDEX for this record. The name of the underlying table is PSIDXDDLPARM.

  If you want to change the default PSINDEX to something else, go to the utilities Menu and use DOF model by default and change the PSINDEX to something else. Once you change this setting, the next time that you create the index, it will be created in the tablespace.

  If you create an index in a different tablespace outside PeopleSoft, we have no knowledge of this and do not update our tables in order to take into account where he currently resides. Once you have updated the default template and replaced the records you want to replace, you can make a Data Mover, followed of a Data Mover import export and the index will be created as they have been redefined. Or you can just do a SQL Create Index and re-create all of them.

• Creating / deleting indexes using a Package

  In SchemaA:

  CREATE OR REPLACE PACKAGE TESTPACKAGE AS
  PROCEDURE Create_Indexes;
  PROCEDURE Drop_Indexes;
  END TESTPACKAGE;
  /
  
  CREATE OR REPLACE PACKAGE BODY TESTPACKAGE AS
  PROCEDURE Create_Indexes
  IS
  BEGIN
  EXECUTE IMMEDIATE 'CREATE UNIQUE INDEX SCHEMAB.IDX1 ON SCHEMAB.TABLEA (COLUMN_PK) NOLOGGING NOPARALLEL';
  COMMIT;
  EXCEPTION
     WHEN NO_DATA_FOUND THEN
         DBMS_OUTPUT.PUT_LINE('NO DATA FOUND IN BASE TABLES' );
     WHEN OTHERS THEN
        DBMS_OUTPUT.PUT_LINE('ERROR MESSAGE:' || SQLERRM );
  END;
  
  PROCEDURE Drop_Indexes
  IS
  BEGIN
  EXECUTE IMMEDIATE 'DROP INDEX SCHEMAB.IDX1';
  COMMIT; 
  
  EXCEPTION
  WHEN NO_DATA_FOUND THEN
  DBMS_OUTPUT.PUT_LINE('NO DATA FOUND IN BASE TABLES' );
  WHEN OTHERS THEN
  DBMS_OUTPUT.PUT_LINE('ERROR MESSAGE:' || SQLERRM );
  END;
  
  END;
  {code}
  I have granted the following on SCHEMAB.TABLEA to SCHEMAA
  
  GRANT SELECT, INSERT, UPDATE, DELETE, REFERENCES, ALTER, INDEX ON TABLEA TO SCHEMAA;
  
  The problem is that when i am logged into Oracle 10g I can execute any of the commands i have put into the execute immediate and they work. However when I execute the package it tells me it has completed but the index has not been created nor has it been dropped in SchemaB. I am not getting any error messages displayed.
  
  The reason before anyone asks why is that there is a nightly load of data happening from scratch so the process is basically Schema A will drop the indexes , execute a truncate table statement on the tables in schema B. The populate will happen and then the create indexes will be executed. This is being done for speed.
  
  Any help would be greatly appreciated.
  thanks                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                                

  (1) A ONCE OTHER exception that does not again raise an exception handler is almost certainly a mistake. In your case, you write DBMS_OUTPUT via error message, but unless your front end comes to try to read and display the DBMS_OUTPUT buffer, the error will be ignored. You really want to remove this exception handler.

  (2) creating an index will not trigger a NO_DATA_FOUND if there is no data in the table, this exception handler is superfluous.

  (3) If you want that the user has to be able to create an index in the schema of the user B, the user must be granted the CREATE ANY INDEX privilege (directly, not through a role). If you get a permissions error after removing incorrect exception handlers, create the index, this is probably the problem. If you get an error of permissions deleting the index after removing incorrect exception handlers, you need to ensure that the user is granted the privilege to DEPOSIT ANY CLUE.

  (4) since the different PRIVILEGES (CREATE ANY INDEX, DROP ALL INDEXES, etc.) are powerful enough and not limited to a particular schema, is there a logical reason does not put this code in detail b. first?

  Justin

• Unique index constraint Vs Unique

  Dear all,

  I just want to understand what is the difference between a Unique Index and uniqueness constraint

  I can create indexes like that, it duplicates will be blocked

  create table abhi_1 
  ( l_number number 
  )
  CREATE UNIQUE INDEX abhi_1_UK ON abhi_1
  (l_number);
  

  I can also use below syntax for duplicates blocking (index will be created internally)

  create table abhi_1 
  ( l_number number, 
  constraint abhi_1_UK UNIQUE (L_number)
  )
  

  Please specify,

  Hello

  I would use a unique constraint.  Allows you to create foreign key constraints referencing the single column.

  As you said, when you create a unique constraint, Oracle automatically creates an index for it if necessary.  You can explicitly set the attributes of that index (for example, the name and tablespace) If you wish.

• (ORA-00955) conflict of naming for index and constraint when you use a unique index (.. desc,.. CSA)

  Hello

  indexes and constraints are in different namespaces, so it should be possible to give them the same name.

  In the following case that apparently does not work:
  

  create unique index orders_year_show_uq
    on orders (year desc, show_orders asc);
   
   alter table orders
    add constraint orders_year_show_uq unique (year, show_order);
  

  When I run these statement, I get a "SQL Error: ORA-00955: name is already used by an existing object". ""

  If I clean and I execute the same instructions as above with the only difference on the 2 line, using "asc year" instead of "year desc":

  
    on orders (year asc, show_orders asc);
  

  then it success.

  I can't explain it, you have an idea?

  Thanks in advance.

  Kind regards

  Giovanni

  First of all, you have show_orders in index and show_order in the constraint. I'll assume that it's a typo. Second, when you create constraint without index enhance the specification Oracle seeks indexes existing on the same set of columns in ascending order. If this index does not exist (and it's your case, since one of your columns to index is in descending order), Oracle tries to create one with the same name as the constraint. That's why you get ORA-00955: name is already used by an existing object. In general, you can specify explicitly the index name to force the Oracle by using the existing index. But it will not help you. If you issue

  ALTER table orders add unique constraint (year, show_orders) orders_year_show_uq using index orders_year_show_uq;

  You will get the ORA-14196: specified index cannot be used to apply the constraint.

  In any case, Oracle does not support using index DESC for PK/UK.

  SY.

• Unique index on two columns based on the conditon

  I have a table where I have two columns name and feed.
  

  create table test1 (name varchar(20), feed varchar(4));
  
  insert into test1 values('abc','L3');
  insert into test1 values( 'abc','Both');
  insert into test1 values('abc','L2');

  I want to create a unique index for the lines abc - L3 and cant abc - both together be inserted, rest the other flow values is not a problem, so the first two rows can not be there in the table.
  
  Please suggest
  
  Thajs

  create unique index test1_ind1 on test1 (name, case when feed = 'Both' then 'L3' else feed end );
  

  Who did what you asked...

  However, I highly doubt it does what you WANT.

  Please provide information on the requirements, and we the flesh that out a little better.

• ORA-01502 error in the case of a unique index unusable and dml in bulk

  Hi all.
  
  The BP is 11.2.0.3 on a linux machine.
  
  I did a unique index unusable and issued a dml on the table.
  Howerver, oracle gave me the error ORA-01502.
  
  In order to avoid the ORA-01502 error, should I drop the unique index and bulk make dml and rebuild the index?
  
  Or is there another solution without recreating the unique index?
  

  create table hoho.abcde as
  select level col1 from dual connect by level <=1000 
  
  10:09:55 HOHO@PD1MGD>create unique index hoho.abcde_dx1 on hoho.abcde (col1);
  
  Index created.
  
  10:10:23 HOHO@PD1MGD>alter index hoho.abcde_dx1 unusable;
  
  Index altered.
  
  Elapsed: 00:00:00.03
  10:11:27 HOHO@PD1MGD>delete from hoho.abcde where rownum < 11;
  delete from hoho.abcde where rownum < 11
  *
  ERROR at line 1:
  ORA-01502: index 'HOHO.ABCDE_DX1' or partition of such index is in unusable state

  Thanks in advance.
  Best regards.

  Do I have to accept the unique index maintenance workload(undo generation/redo for undo generation)
  when doing bulk dml?
  

  I think so.

  The amount of data you load compared to existing data in the table?

  If say for example, you add 20%, and then to compare the retention of 20% adds data during the major part collect to create all of the index after insertion so
  you choose the drop/recreate the unique index

  Best regards

  Mohamed Houri
  www.hourim.WordPress.com

• Unique index with TRIM

  I want to create a unique constraint with TRIM, I get the error message. Is there a way...

  ALTER TABLE core_business.cb_pensioner ADD CONSTRAINT unique_claim_no UNIQUE(TRIM (claim_no))   deferrable initially deferred NOVALIDATE;
  
  ORA-00904: : invalid identifier

  Pre 11g - unique index; 11g go - virtual columns.

  SQL> create table t1
    2  (col1 varchar2(10));
  
  Table created.
  
  SQL> alter table t1 add constraint uk_t1 unique (trim(col1));
  alter table t1 add constraint uk_t1 unique (trim(col1))
                                              *
  ERROR at line 1:
  ORA-00904: : invalid identifier
  
  SQL> create unique index i1 on t1 (trim(col1));
  
  Index created.
  
  ... virtual column method ...
  
  SQL> drop index i1;
  
  Index dropped.
  
  SQL> alter table t1 add col2 as (trim(col1));
  
  Table altered.
  
  SQL> alter table t1 add constraint uk_t1 unique (col2);
  
  Table altered.
  
  SQL> insert into t1 (col1) values ('1');
  
  1 row created.
  
  SQL>  insert into t1 (col1) values ('1  ');
   insert into t1 (col1) values ('1  ')
  *
  ERROR at line 1:
  ORA-00001: unique constraint (RIMS.UK_T1) violated
  
  SQL> select * from t1;
  
  COL1       COL2
  ---------- ----------
  1          1
  
  SQL> 
  

• Unique index and "$SYS_NC00012".

  Hi bolow is creating scritpt index that I created in on the table

  CREATE UNIQUE INDEX TESTUK_05
  ON TEST (COL1_NO,
               COL2_NO,
               COL3_DATE,
               COL4_NO DESC)
  PCTFREE 002
  INITRANS 5
  STORAGE (
            INITIAL 200M
            PCTINCREASE 0
          )
  TABLESPACE USERS;

  but when I m running table user_ind_columns he shows me another column name instead of the last column that is "col4_no".

  select TABLE_NAME,INDEX_NAME,COLUMN_NAME from user_ind_columns where table_name='TEST' order by INDEX_NAME;
  
  TEST      TESTUK_05            COL3_DATE
  TEST      TESTUK_05            COL2_NO
  TEST      TESTUK_05            COL1_NO
  TEST      TESTUK_05            SYS_NC00012$

  PLEASE TEL ME WHY IT GIVES NAME AS COLUMN "SYS_NC00012$" INSTEAD OF COL4_NO

  See notes on "ASC | DESC' at http://download.oracle.com/docs/cd/B19306_01/server.102/b14200/statements_5010.htm#i2062403

  'DESC' creates a function-based Index. Oracle creates a column for COL4_NO expression in descending order.

  I would advise that you not misc mix ASC and DESC of columns in an index.

  Hemant K Collette

  Published by: Hemant K grapple on March 9, 2011 16:58
  URL edited to CREATE INDEX Syntax

  Published by: Hemant K grapple on March 9, 2011 17:09

• unique index on two columns

  Hi all
  I want a unique index on two columns, but when I try this it will show me

    1  CREATE UNIQUE INDEX sale_order_no
    2*   ON sale_order (sale_order_no, season_year)
  SQL> /
    ON sale_order (sale_order_no, season_year)
       *
  ERROR at line 2:
  ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found

  I want to do not overlap with the combination of these two
  
  Plaese Guide
  Thanks and greetings
  Vikas

  You would this behavior if SALE_ORDER_NO has NULL values. If it contains NULL values, a unique single-column index will succeed but an index unique multi-column will fail when it finds duplicates in SEASON_YEAR.

  See:

  SQL> create table dummy_objects (object_id  number, object_owner varchar2(30), object_name varchar2(30));
  
  Table created.
  
  SQL> insert into dummy_objects values (0,'HEMANT','TABLE_A');
  
  1 row created.
  
  SQL> insert into dummy_objects values (1,'HEMANT','TABLE_B');
  
  1 row created.
  
  SQL> insert into dummy_objects values (NULL,'HEMANT','NULL_1');
  
  1 row created.
  
  SQL> insert into dummy_objects values (NULL,'HEMANT','NULL_2');
  
  1 row created.
  
  SQL> create unique index dummy_objects_u1 on dummy_objects(object_id);
  
  Index created.
  
  SQL> drop index dummy_objects_u1;
  
  Index dropped.
  
  SQL> create unique index dummy_objects_u2 on dummy_objects(object_id, object_owner);
  create unique index dummy_objects_u2 on dummy_objects(object_id, object_owner)
                                          *
  ERROR at line 1:
  ORA-01452: cannot CREATE UNIQUE INDEX; duplicate keys found
  
  SQL>
  

  Hemant K Collette
  http://hemantoracledba.blogspot.com

• Unique index or Unique constraint

  Hi all
  
  I am a student of Oracle SQL Expert Certification. At one point in the book, speaking of the clues, the author says that a unique index is not the same a unique constraint. However, it does not explain why they are two different things.
  
  Could someone clarify the difference between the two, please?
  
  Thank you very much
  
  Valerio

  A constraint has a different meaning for an index. It gives the optimizer more information and allows you to have foreign keys on the column, then that is not a unique index.

  for example:

  SQL> create table t1 (col1 number, col2 varchar2(20), constraint t1_uq unique (col1));
  
  Table created.
  
  SQL> create table t2 (col1 number, col2 varchar2(20));
  
  Table created.
  
  SQL> create unique index t2_idx on t2 (col1);
  
  Index created.
  
  SQL> create table t3 (col1 number, col2 number, col3 varchar2(20), constraint t3_fk
    2                   foreign key (col2) references t1 (col1));
  
  Table created.
  
  SQL> create table t4 (col1 number, col2 number, col3 varchar2(20), constraint t4_fk
    2                   foreign key (col2) references t2 (col1));
                   foreign key (col2) references t2 (col1))
                                                     *
  ERROR at line 2:
  ORA-02270: no matching unique or primary key for this column-list
  

  It's like saying ' what is the difference between a Chair and a Chair? They both allow you to sit! »

• creating a unique index of instaed of using the primary key index

  Hello
  
  I heard in a debate sometimes it is better to create a unique index on a column and use it instead of using the primary key index in oracle. I did not understand what that the reason propely.
  
  Can someone please help me in this topic if it is valid.
  
  Thanks in advance

  On the surface, which does not seem reasonable... Volume of the DML is irrelevent to determine which column is the primary key for a table.

  My wild speculation a bit at a reasonable time could someone do...

  If you use synthetic primary keys (i.e. the keys generated by sequence) and that your tables are subject to large volumes of inserts such as there is a danger that the block "to the right" will be the source of contention block and worry not about analysis of beach on the column, you can create a reverse on this column (unique or non-unique) key index before creating the primary key constraint and to indicate Oracle to use this existing index to respect the primary key constraint.

  Obviously, however, this involves a lot of assumptions to arrive at a reasonable point. There may well be another set of assumptions that could also lead to a valid argument. Or it could be a myth that someone has heard and just repeats.

  Justin