Unique constraints

Similar Questions

• correct handling of foreign keys in unique constraints for operations ON DELETE SET NULL

  During my troubleshooting at a client site, I came across an interesting setup where I would like to ask your opinion.

  
  Consider two tables ADTB and TBLB.

  ADTB:

  INT COLA1

  COLA2 INT

  TBLB:

  COLB1 INT

  COLA2 is COLB1 as a foreign key ON DELETE SET NULL value.

  COLA1 and COLA2 are combined into a UNIQUE for the BATTERY constraint.

  I have two records of TBLB:

  (1)

  (2)

  and two DRUM recordings:

  (1, 1)

  (2, 2)

  so far, all the constraints are valid.

  During my research, I learned that I can not put COLA2 null in ADTB for two lines at the same time:

  TBLA UPDATE set COLA2 = NULL where COLA1 = 1;

  -> OK

  TBLA UPDATE set COLA2 = NULL where COLA1 = 2;

  -> VIOLATED UNIQUE CONSTRAINT

  Unfortunately, it's something my application needs, anyway. In order to get this resolved, but I try to understand, what would happen if I:

  REMOVE THE TBLB;

  ?

  It should set COLA2 in ADTB "Null" on the two lines, which is not allowed due to the UNIQUE CONSTRAINT.

  Can someone shed light on this issue? Thank you.

  
  Yours,

  Ronny

  Unfortunately, as you say, you can't not NULL values in such a unique constraint.  It would be the same as if you had a composite primary key and try to allow one of the columns will be null in several rows with the same value in the other column.  NULL is treated as an "unknown" value, it is possible that it could be the same value (it may or may not be, but Oracle does not know), so it must assume that it might be and that's why treat it as if there is the potential for a duplicate... so it's not unique.

  In short, do not allow null values in your unique constraints.

  The default is in the drawing, not in the way that Oracle is the treatment.  Fix the design if you do not have NULL values.

  In terms of relational database design, it seems that you are trying to transform the 1:M relations M:M relations, and which requires an intermediate table if you have M:1 and 1:M between 3 tables instead.

• Unique constraint on the values in both directions

  I'm looking to create a unique constraint that works in two ways. Say I got a constraint unique in columns 1 and 2. I want it to be impossible for the two lines below the two exist at the same time. Is there a way to do this? I googled around for a while now and I found nothing that works so far.

  Header 1	Header 2
  Dog	CAT
  CAT	Dog

  Hello

  You can create an index based on a single function:, like this:

  CREATE UNIQUE INDEX table_x_header_1_header_2

  ON table_x (LESS (header_1, header_2)

  More LARGE (header_1, header_2)

  );

  How will you use these values?  You might be better to simply create a regular old unique constraint, but also have a CHECK constraint to ensure that header_1<= header_2. ="" that="" way,="" when="" you="" want="" to="" search="" for="" the="" combination="" ('cat',="" 'dog')="" you="" won't="" have="" to="" search="" for="" ('dog',="" 'cat')="">

• Index naming standards does not and unique constraints

  I found yet another question of naming standards

  I have tried to create a unique constraint as a normal index via the unique constraints and indexes in Properties of Table with the assumption that it will use the design properties of models.  This isn't.

  

  As noted in the image of the model above, my Unique constraint model is {table} _ {columns} lancement_remarques

  and my model of Index idx _ {columns} {table}.  Yet, when I try to create the Unique constraint, it creates the naming convention in names like CUSTOMER_ADDRESS__UK (2 lines of underscore?) as shown below.

  

  My assumption is that he needed a column, so I added the column and also applied the rules naming - nothing.

  

  Is my wrong assumption on these constraints being appointed through the models?  If this is not the case, what naming rules is in this context?

  The same behavior is evident when you try to create index.

  I get not all comments on my posts.  Are these bugs or just user error?

  Hello

  Thank you to report the problem, I logged a bug. You can get 'Rules of naming' works properly if you press the button 'Apply' before that.

  I get not all comments on my posts.

  I don't think that anyone (or any job) has been ignored on this forum. Depending on the complexity of the problem and our current commitment (other urgent tasks, holidays, time zone), you can get answer almost immediately or after a certain time.

  It is useful for us, if you mark your messages as replied if you get the right answer.

  Philippe

• Unique constraint in the form of master detail error

  Hi all

  I need help, the following requirement.

  I have a master detail form developed on master-child table. the tables have the composite key.

  Old masters has a composite key on columns (A, B)

  Children table has a composite key on columns (A, B, C)

  Child block look something like below

  C       A          B

  10 AAA 1000

  20 1300 BBB

  30 CCC 1400

  40 DDD 1200

  Increments of column C with 10 for each record, and if a new record is insert in intermediaries the records it is incremented to 5.

  My requirement is when an end user attempts to insert record between 20 and 30 or 30 and 40 and clicks on save, the value of the C column must regenerate as shown below

  C       A          B

  10 AAA 1000

  20 1300 BBB

  XXX 30 900

  40 CCC 1400

  50 DDD 1200

  Button Save I wrote the following code

  Declare
    ln_Count NUMBER :=0;
    ln_c number :=0
    cursor c1 is
    select c
    from child
    where a=:child.a
    and b=:child.b
  Begin
    Go_Block('Child');
    First_Record;
    LOOP
    ln_Count:= ln_Count+10;
    :child.C := ln_Count;
    EXIT When :System.Last_Record = 'TRUE';
    Next_Record;
    END LOOP;
  
  
    For c_cur in c1 Loop
    update child
    set c:=ln_c+10
    where a=:child.a
    and b=:child.b 
    and c=c_cur.c
    end loop;
    Forms_DDL('commit');
       
       commit_prc('Commit');  -- We have our own program unit to call commit_form
  
  END;
  

  I tried above in a way because, before approving the changes to the table, I update the existing values in the table of the C column so I would not get unique constraint error.

  When you click the button Save, I get a constraint exception. Hope I made my requirement clear.

  Can someone give me a clue to this implementation.

  Thank you

  malandain

  With this update, all your C-columnvalue became negative. When you post the form thereafter, forms update agaion records one by one the new positive figures. Because the numbers of 'old' in the db are now negative, there will be no violation-UK.

• How to display a validation on a modal dialog error based on a unique constraint?

  Hi all

  Apex 4.1

  See example on apex.oracle.com:

  Workspace: EDIAZJORGE

  User name: TEST

  Password: test123

  Application: 55036 - Validation of modal Page

  I have a page with two elements, to make and model, where the user will be able to enter the model, say, a car and use a pick to dolist. If make does not exist, the user can click on the [+] button that opens a modal dialog box to add a new do.

  Everything works fine except when I try to insert a double do, which triggers a unique constraint violation error:

  AJAX call back Server error ORA-00001: unique constraint (EDIAZJORGE. MAKE_UK1) violated to execute the PL/SQL Code

  I want to enter this event and inform the user about an error inside the modal dialog box, but I don't know what is the best way to achieve this. My guess is that I'll have to make an Ajax call to run an application process and capture the exception of DUP_VAL_ON_INDEX, but I'm not very familiar with the Ajax part.

  Any suggestions?

  Thank you

  Erick

  I'm sorry Erick, I was in error. You always get an alert but with a nicer message. The actions of builtin DA do not allow interaction with them, so no way to manage the return of ourselves.

  In light of this, I copied the page in enforcement 77635 1-2 and made some changes to it. Basically, I copied the code to Jorge and modified so that it uses $.ajax instead of apex.server.process. I much prefer it to htmldb_Get - you shouldn't really use it either. More $.ajax has the advantage of this apex.server.process is based on it. That should work well on 4.1.

  Sorry Jorge, won't steal the Thunder, I guess I was... bored? And decided to do some apex?

• Customized for a Unique constraint processing scripts

  Hallo,

  How can I create the Unique constraint (not a Unique Index) transformation scripts:

  var key_column = 'KEY';
  // get tables
  tables = model.getTableSet().toArray();
  for (var t = 0; t < tables.length;t++){
       table = tables[t];
       table_name = table.getName();
       abbr = table.getAbbreviation()+"_";
       key_col = table.getElementByName(key_column);
       if (key_col!=null){
            uniq = table.createIndex(); // it is right?
            table.setDirty(true);
            uniq.setName('UNIQUE'); // does not matter
            uniq.add(id3_col);
            uniq.setUK(true); // a method does not exist
            table.setUK(uniq);// a method does not exist
        }
  }
  
  

  regarding

  Oleg

  Hello Oleg,

  lines 14 and 15 are false. The use of the persistence method is:

  uniq.setIndexState ("Unique constraint");

  Other options here - you can spot if you look at the XML file representing the table with PK and UK constraints and regular index - "primary constraint, «Unique Index ordinary', «Clear index»»

  Philippe

• Can we create a Unique constraint on DFF attribute of a Standard Oracle Table

  Hi all

  Can we create a Unique constraint on DFF attribute of a Standard Oracle Table.

  There will be problems of integrity of the data in this case?

  Any help will be greatly appreciated.

  Best regards

  gt1942

  You should not. The same field of de FACTO forces might be used beyond business groups/associations causing cross-functional problems. This would be considered a direct customization and may affect Oracle features seeded depending on where you want to add it.

  Kind regards

  Arif.

• How to create a Unique constraint on a column that already has duplicates. Only future duplicates should be avoided

  Hi all

  Can someone let me know how to create a Unique constraint on a column that already has duplicates. Only future duplicates must be avoided.

  Any help will be greatly appreciated.

  Best regards

  gt1942

  ALTER table Add constraint unique (column_name) may be deferred novalidate;

• Oracle DB: Check Unique constraints before award of sequence (ID)

  Hello!

  I am building a Java web application using JPA.

  I used to fill the table IDs, sequences of generators, reported through DB and javax.persistence annotation (@Sequence).

  Some tables have simple unique constraints (example: Table_Country: Country column "country_name" must be Unique).

  At the time of execution, trying to persist a country name that is already in my Table_Country, java will throw exception: OK. But I noticed: before that, DB has allocated a sequence ID to my object.

  My question is: there's way (apart from making programmatic or triggers for and during the audit) of database to check unique constraints before award of sequence?

  Thanks in advance!

  My question is: there's way (apart from making programmatic or triggers for and during the audit) of database to check unique constraints before award of sequence?

  No - for several reasons.

  1. the real constraint is not verified by Oracle until you provide the values you are using Oracle.

  2. If you try to perform the audit before giving the value to Oracle another user could enter this value and insert it before you and which would still cause your problem.

  Oracle is a multi-user system. Even if you try to "look" at the next value in the sequence other users could easily allocate this value until you can get it so the value you 'read' would really not be the value you get.

  You can't tell what the value of the next sequence will be except by actually calling NEXTVAL to return.

  As others have said it seems that yours is a JPA number.

• Question of the unique constraint with finance charge

  Hi friends,

  As part of the implementation of 11 g BIAPPS-ODI during the execution of a finance charge is my load of CM plan failed with the error like below

  ODI-1519: series step 'Load start Plan (InternalID:1242500)' failed because step 'Refresh Global Variable (InternalID:1243500)' child is in error.

  ODI-1519: series step 'Refresh Global Variable (InternalID:1243500)' failed because the step child "Warehouse loading Phase (InternalID:2336500)" is a mistake.

  ODI-1519: series step "Warehouse loading Phase (InternalID:2336500)" failed because the child step "SIL 1 charge (InternalID:2337500)" is a mistake.

  ODI-1519: series step '1 SIL Load (InternalID:2337500)' failed, because the child step '2 group of dimensions of SIL (InternalID:2338500)' is a mistake.

  ODI-1519: series step '2 group of dimensions of SIL (InternalID:2338500)' failed because the child step "Parallels - independent DimGroup (InternalID:2346500)" is a mistake.

  ODI-1518: parallel step 'Parallels - independent DimGroup (InternalID:2346500)' failed. level of 1 child by mistake, which is more than the maximum number of allowed errors (0) defined for parallel step.  Has no measures of the child: 3 SIL Dims POSHIER_DIM (InternalID:2369500)

  ODI-1519: series step '3 SIL Dims POSHIER_DIM (InternalID:2369500)' failed because the child "POSHIER_DIM (InternalID:2372500)" is a mistake.

  ODI-1519: series step "POSHIER_DIM (InternalID:2372500)" failed because step "SIL_PositionDimensionHierarchy (InternalID:2377500)" child is in error.

  ODI-1217: SILOS_SIL_POSITIONDIMENSIONHIERARCHY Session (4278500) fails with return code 1.

  ODI-1226: SIL_PositionDimensionHierarchy.W_POSITION_DH step fails after 1 attempt.

  ODI-1240: Flow Run SIL_PositionDimensionHierarchy.W_POSITION_DH fails during an operation of integration. This flow of charge table target W_POSITION_DH.

  ODI-1228: SIL_PositionDimensionHierarchy.W_POSITION_DH (integration) of the task fails when connecting ORACLE target BIAPPS_DW.

  Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (DEV_DW. W_POSITION_DH_U2) violated

  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:462)

  at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:405)

  at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:931)

  at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:481)

  at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:205)

  at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:548)

  at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:217)

  at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:1115)

  at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1488)

  at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3769)

  at oracle.jdbc.driver.OraclePreparedStatement.execute(OraclePreparedStatement.java:3954)

  at oracle.jdbc.driver.OraclePreparedStatementWrapper.execute(OraclePreparedStatementWrapper.java:1539)

  at oracle.odi.runtime.agent.execution.sql.SQLCommand.execute(SQLCommand.java:163)

  at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:102)

  at oracle.odi.runtime.agent.execution.sql.SQLExecutor.execute(SQLExecutor.java:1)

  at oracle.odi.runtime.agent.execution.TaskExecutionHandler.handleTask(TaskExecutionHandler.java:50)

  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.processTask(SnpSessTaskSql.java:2913)

  at com.sunopsis.dwg.dbobj.SnpSessTaskSql.treatTask(SnpSessTaskSql.java:2625)

  at com.sunopsis.dwg.dbobj.SnpSessStep.treatAttachedTasks(SnpSessStep.java:577)

  at com.sunopsis.dwg.dbobj.SnpSessStep.treatSessStep(SnpSessStep.java:468)

  at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:2093)

  at com.sunopsis.dwg.dbobj.SnpSession.treatSession(SnpSession.java:1895)

  to oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$ 2.doAction(StartScenRequestProcessor.java:580)

  at oracle.odi.core.persistence.dwgobject.DwgObjectTemplate.execute(DwgObjectTemplate.java:216)

  at oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor.doProcessStartScenTask(StartScenRequestProcessor.java:512)

  to oracle.odi.runtime.agent.processor.impl.StartScenRequestProcessor$ StartScenTask.doExecute (StartScenRequestProcessor.java:1068)

  at oracle.odi.runtime.agent.processor.task.AgentTask.execute(AgentTask.java:137)

  to oracle.odi.runtime.agent.support.DefaultAgentTaskExecutor$ 2.run(DefaultAgentTaskExecutor.java:82)

  at java.lang.Thread.run(Thread.java:662)

  How to solve the question above using ODI 11 g. I'm using Oracle ERP R12.1.3 as a source of data for this.

  Thanks in advance.

  Kind regards

  Saro

  What is the result of a query on table W_POSITION_DH or W_POSITION_D duplicate?

  Naeem

• Retrieve values with a unique constraint

  All,

  It may be a stupid request and I think too speak of it. But, for some reason, I am unable to write a query to accomplish my task.

  I have the T table with some columns and the columns c1, c2, c3 are part of a composite unique constraint. Now I'm updating the value c3 from 52 to 51. But, when I do an update like:

  Update T set c3 = 51 where c3 = 52;

  I get a Unique constraint violation error.

  So, I need to know what are the values of repetition that might be causing this?

  Thanks in advance guys.

  34a22dde-3108-4F05-BE72-eb1043d28314 wrote:

  All,

  It may be a stupid request and I think too speak of it. But, for some reason, I am unable to write a query to accomplish my task.

  I have the T table with some columns and the columns c1, c2, c3 are part of a composite unique constraint. Now I'm updating the value c3 from 52 to 51. But, when I do an update like:

  Update T set c3 = 51 where c3 = 52;

  I get a Unique constraint violation error.

  So, I need to know what are the values of repetition that might be causing this?

  Thanks in advance guys.

  An inelegant way...

  select *
  from your_table tab1
  where (tab1.c1,tab1.c2) in
  (
  select tab2.c1, tab2.c2
  from your_table tab2
  where tab2.c3 = 52
  )
  where tab1.c3 = 51;
  

• Adding a UNIQUE CONSTRAINT to an existing column with duplicate values

  Oracle Forums Hello, I have a table that contains rows 11 901. I tried to define the UNIQUE constraint on the column of xcode, but encountered an error: the column already contain duplicates! I rescued following SQL 'SELECT COUNT (*) FROM States;' the result is 11 901 and 'SELECT COUNT (DISTINCT (xcode)) FROM States;' the result is 11 680. So to enforce this unique key I have to remove the 221 lines. Please how can I do this?

  REMOVE duplicates...

  For example, as

  delete from your_table t
  where rowid <
     (
     select max(rowid)
     from your_table r
     where t.unique_column = r.unique_column);
  

  Thne create the constraint.

• Case-insensitive unique constraint

  Hi guys,.
  
  Is it possible to create a unique constraint that is case-insensitive
  
  I mean if there is a unique constraint on the name of col
  
  then
  'James' and 'JAMES' must not
  
  
  Kind regards
  
  PAPI

  Create a unique index to the basic function of...

  create unique index uk_name on emp(upper(ename));
  

• ORA-00001: unique constraint

  Hi all
  
  I use ODI 11.6 and Oracle 11 g.
  
  When executing my interface, I get the error inserting new line below rate
  
  ODI-1228: failed INT_TEMP_TO_MOSA (integration) task on the target of ORACLE EDGE_DEV_OWNER connection.
  Caused by: java.sql.SQLIntegrityConstraintViolationException: ORA-00001: unique constraint (EDGE_DEV_OWNER. SP_MOS_PK) violated
  
  Any ideas how to solve this problem?
  
  Thank you
  Lony

  Check the separate option in the stream tab. Do not drop the I$ table. Run a group of query keycolumn in Toad cons I$ table and see whether or not duplicate records exist.
  Thank you.

• Unique constraint with condition - validation of EO levels

  I have a table
  create the CUSTOMER table (key number primary client_prefix,)
  client_suffix Varchar2,
  Number of NIN,
  status number (1).
  . . . . . . . .
  . . . . . . . .);
  
  
  I have an obligation to respect a unique constraint where NIN THAT must be unique for the Client_suffix, but the issue is that customers in rejected status
  (status = 9 means that the customer is in rejected status) should be ignored.
  
  It is a new customer can be created with the same client_suffix, combination of NIN has provided other customers
  with the same combination have rejected status. If not, can not be created.
  
  I've already implemented this in the database level. I would like to know how this can be implemented as a validation of EO levels
  
  Jdev version 11.1.2.0.0

  No, you don't need to do...

  Use this technique: http://docs.oracle.com/cd/E26098_01/web.1112/e16182/bcadvgen.htm#sthref439

  John