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

Similar Questions

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

  What is "significance" of the following difference: -.
  
  Some PK indexes in the database that I deal with are scripted by creating a Unique index first, then adding the PK constraint with syntax "using the index.
  
  Others simply create the PK using the addition of the primary key constraint syntax.
  
  We're much better than the other or where in the documentation would review it? I can't find that he discusses more probably looking in the wrong book.
  
  Thanks in advance. Bill

  Hi Bill,

  If you create a unique index first then add PK constraint or create a PK constraint directly, one and the same.

  Say, there is a unique index on the column 'a' and now you want to apply PK constraint on the same column, instead of dropping the index and re-create the same, you can use the existing one. It's ok if the amount of data is less, but for a huge amount of data, it is a killer.

  Here's a little comparison of the two cases:

  SQL> drop table t purge;
  
  Table dropped.
  
  SQL> create table t ( a number);
  
  Table created.
  
  SQL> create unique index t_idx on t(a);
  
  Index created.
  
  SQL> alter table t add constraint t_pk primary key (a) using index t_idx;
  
  Table altered.
  
  SQL> select uniqueness from user_indexes where index_name = 'T_IDX';
  
  UNIQUENES
  ---------
  UNIQUE
  
  SQL> select constraint_name, constraint_type, index_name from user_constraints where table_name = 'T';
  
  CONSTRAINT_NAME                C INDEX_NAME
  ------------------------------ - ------------------------------
  T_PK                           P T_IDX
  
  SQL>
  SQL>
  SQL>
  SQL>
  SQL>
  SQL>
  SQL>
  SQL>
  SQL>
  SQL>
  SQL> drop table t purge;
  
  Table dropped.
  
  SQL> create table t ( a number);
  
  Table created.
  
  SQL> alter table t add constraint t_pk primary key (a);
  
  Table altered.
  
  SQL> select uniqueness from user_indexes where index_name = 'T_PK';
  
  UNIQUENES
  ---------
  UNIQUE
  
  SQL> select constraint_name, constraint_type, index_name from user_constraints where table_name = 'T';
  
  CONSTRAINT_NAME                C INDEX_NAME
  ------------------------------ - ------------------------------
  T_PK                           P T_PK
  
  SQL>
  

  I hope that the answer was clear.

  Concerning

  Asif Momen
  http://momendba.blogspot.com

• How to call user B to drop/create an indexes on a table owned by the user has?

  Hello!
  We have the following situation:
  = > user B has a table that has an index
  = > user connects to the database and must have sufficient privileges or the ability to drop/create an index for a table owned by the user B.
  Since there are several different schemas in the database, it is not possible to grant the privilege "to create any index' or 'delete any index '.
  for the user.
  = > to do even more complicated: the necessary procedure must not belong to user B
  
  I tried to solve this problem with a stored procedure (which belongs to user C). Why do we use user C? C the user has several packages,
  procedures and functions that get used by other users (for example for purposes of logging, refresh materialized views,...)
  
  So the logic is:
  = > user A calls user procedure C. In this procedure the call "run immediately" ALTER SESSION SET CURRENT_SCHEMA = B' "»
  is executed successfully. The next step, the < drop index B.i1 > statement would get executed. But this statement fails with the
  exception ' ORA-01031: insufficient privileges ".
  
  If this procedure is created in the schema of the user B then everything works fine - but because of our current design of the database, this procedure
  must belong to the user C.
  
  Does anyone know a solution to this problem?
  
  Any help will be appreciated
  
  Rgds
  JH

  I think you need the privilege DROP_ANY_INDEX directly to user C.

• How to create faster index in the table of 500 GB

  Dear Experts,

  I have to create 20 index on table data-ware house. This table is of size 500 GB.

  freshen up this weekly chart using the external table.

  creating 20 indexes on this table consumes a lot of time.

  I have 40 GB of ram on 2012 box windows with 8 processors.

  I installed 11 GR 2.

  I have 4 drives C D E F

  for AN index, it takes 4 hours

  
  

  I added enough space to the tablespace

  I put the tablespace in a drive D:\
  

  
  

  I'm under control to create indexes below

  create index  X_3_INVEN_ITEM_ID_IDX  on   X_3_PV_TD_2 (INVENTORY_ITEM_ID)  parallel 32 nologging;
  
  

  output long ops

  SID, SERIAL # CONTEXT SOFAR TOTALWORK LESS TARGET % _COMPLETE TIME_REMAINING

  ---------- ---------- ---------- ---------- ---------- ---------------------------------------------------------------- ---------------------------------------------------------------- ---------- --------------

  108 10 0 3758 140973 Rowid Scan AD range. X_3_PV_TD_2                                    2.67            256

  173 23 0 5279 141470 Rowid Scan AD range. X_3_PV_TD_2                                    3.73            258

  114 6 0 10092 141786 Rowid Scan AD range. X_3_PV_TD_2                                    7.12            261

  99         59          0      46283     325908 Sort Output                                                                                                                     14.2          15207

  68        214          0      46763     323623 Sort Output                                                                                                                    14.45          14973

  35         93          0      47531     318364 Sort Output                                                                                                                    14.93          14570

  164         70          0      45058     288506 Sort Output                                                                                                                    15.62          12886

  227         31          0      44130     282285 Sort Output                                                                                                                    15.63          13011

  13          3          0      51890     309515 Sort Output                                                                                                                    16.76          12874

  222 67 0 28837 141380 Rowid Scan AD range. X_3_PV_TD_2                                    20.4            343

  73 37 0 32472 141488 Rowid Scan AD range. X_3_PV_TD_2 22.95 212

  47 8 0 34332 141154 Rowid Scan AD range. X_3_PV_TD_2 24,32 202

  176 20 0 35197 141161 Rowid Scan AD range. X_3_PV_TD_2 24.93 205

  19 7 0 35239 141325 Rowid Scan AD range. X_3_PV_TD_2 24.93 205

  80 4 0 40399 141611 Rowid Scan AD range. X_3_PV_TD_2 28,53 193

  144 20 0 44960 141481 Rowid Scan AD range. X_3_PV_TD_2 31,78 182

  233 101 0 74086 169228 Rowid Scan AD range. X_3_PV_TD_2 43,78 176

  128 165 0 78765 141436 Rowid Scan AD range. X_3_PV_TD_2 55.69 173

  235 1 0 41199796 70035728 table Scan AD. X_3_PV_TD_2 58,83 19804

  199 6 0 52748651 70035728 table Scan AD. X_3_PV_TD_2 75,32-9709

  44 2 0 53686039 70035728 table Scan AD. X_3_PV_TD_2 76,66 9022

  204 26 0 119969 141464 Rowid Scan AD range. X_3_PV_TD_2                                   84.81             40

  202 48 0 138880 162276 Rowid Scan AD range. X_3_PV_TD_2                                   85.58             43

  17 33 0 126506 141778 Rowid Scan AD range. X_3_PV_TD_2                                   89.23             28

  48 7 0 137772 141360 Rowid Scan AD range. X_3_PV_TD_2                                   97.46             15

  Temp tablespace

  
  

  USED_MB USED TOT_MB % NOM_TABLESPACE

  ------------------------------ ---------- ---------- ----------
TEMP 11533 286719 4.02

  temporary tables

  OWNER SEGMENT_NAME SEGMENT_TY TABLESPACE_NAME EXTENTS BYTES_
---------- ------------------------------ ---------- -------------------- ---------- ---------------
AD 156.1601650 TEMPORARY USERS 96 209,715,200

  Question:

  How to fix this?

  (a) run several parallel create sqlplus statement index different sessions

  (b) create a tablespace to put data files in different hard drives like D: E: F: C:

  (c) create the separate tablespace for each hard drive and map it to a single disk IO benefit

  (d) I have 8 processors but parallel 32 is not speed

  (e) how these clues I can run in parallel. Is it OK to run 20 parallel index 32 sqlplus sessions

  All that I have to create 20 index on the table of 500 GB

  target memory = 30GB

  index of names to create 20, each index is 10 GB

  his is of 80 hours (4 hours per index)

  This machine is waiting, I just used all the resources of the machine to accelerate.

  Thanks for reading this

  Thanks for the help in advance

  I was talking about your end of issue speed up construction of index, where I proposed

  orclz >

  orclz > alter session set workarea_size_policy = manual;

  Modified session.

  orclz > alter session set sort_area_size = 2147483647;

  Modified session.

  orclz > create index

  Post edited by: JohnWatson

  Sorry, I misread it: this question was not from you. My apologies. My solution should work for you, however: give yourself a big PGA, manually. Automatic PGA management using not will never give you enough.

• 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.
  

  
  

• unique index on flow error

  Hi gurus,
  
  One of my work in ODI 10.1.3.5 fails to step: create a unique index on the flow table
  and
  throw this error: ORA-02158: invalid CREATE INDEX option
  
  in previous places of employment, he executed successfully but now his failure to get...
  
  I'm looking:
  
  1. What can be the reason of this failure.
  2. can I I skip this step by changing a setting in the flow control tab / (without checking the step by IKM (ignoring the error) - as he will ignore the other packages using the same IKM)
  3. the used IKM is the INCREMENTAL of the IKM ORACLE.
  
  Thank you
  Ravi

  Hi Ravi,

  I'll try to help you.

  1. What can be the reason of this failure.

  ODI will create a non-unique index running based on the PK (primary key) defined in the target data store. So, it could be because some invalid CREATE INDEX option is shown in the flow tab.

  2. can I I skip this step by changing a setting in the flow control tab / (without checking the step by IKM (ignoring the error) - as he will ignore the other packages using the same IKM)

  Better, the flow tab, you can do FLOW_TABLE_OPTION of virgins and try.

  3. the used IKM is the INCREMENTAL of the IKM ORACLE.

  Should be good.

  Thank you
  Guru

• Cannot create indexes on the flow table

  Hello

  I'm new to ODI.

  The problem is that during the execution of an interface, I get the error of the "IKM Oracle Dimension to slow variation"

  The command in step "Create unique index on the flow table:

  creating index < % = odiRef.getTable ("L", "INT_NAME", "A") % > idx

  on < % = odiRef.getTable ("L", "INT_NAME", "A") % > (< % = odiRef.getColList ("", "[column]", ",", "", "SCD_NK") % >)

  < % = odiRef.getUserExit ("FLOW_TABLE_OPTIONS") % >

  generate the following statement which lacks the name of the column between the (_)

  Create index I$ _MYTABLE_idx

  I have $_MYTABLE)

  NOLOGGING

  The result is that the interface fails with the error 936: 42000: java.sql.SQLException: ORA-00936: lack of expression caused by the previous command wrong.

  Please, can you help me?

  Thank you very much

  Angelo

  Hello

  I'm really really sorry! I just realized that you are working on the SCD. Basically, you are looking for all the column mapped as SCD_NK (key to slowly change natural Dimensions) insofar as shown here

  Substitution QAnywhere

  IF you need to read this

  SCD Type 2 - ODIExperts.com

  Let me know.

• 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

• (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 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 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 / 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

• 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.

• How to find the unique index to break the record?

  Hello

  When I do an UPDATE on a table how can I accumulate documents violates a unique index on the table? Is there something like "EXCEPTIONS IN" when using ALTER TABLE MODIFY CONSTRAINT... ENABLE VALIDATE EXCEPTIONS IN...?

  Oracle DB 10g

  Look in the logging of DML errors

  ORACLE-BASE - DML Oracle 10 g Release 2 of the database connection error