Unique key violation

Similar Questions

• Unique key violation - the DB adapter

  Hello

  I have a composite SOA (deployed in clusters of 4 nodes) who questions database and calls a stored procedure (which invokes the records in multiple tables). Now, when I'll be large amount of data in the source database, the composite is mark and tries to insert the records in the target database. But sometimes error cases dating violation of unique key constraint while inserting records into the target database.

  Is locks of adapter DB table before inserting the records so that others may not violate the constraints and they will be able to see changes made by other SOA forums?

  Thank you!

  Yes, certainly not DbAdapter... the problem is the way you do your check and the lack of a facility of mutex in BPEL... Assuming you are using BPEL...

  Ideal scenario...

  1 check key has... There is no instance

  example 1 - insert the key... was ok

  example 2 - check button has exist......

  instance 2 - updates of key has... ok

  Parallel scenario...

  1 check key has... There is no instance

  2 check key has... There is no instance

  example 1 - insert the key... was ok

  example 2 - Insert key a... failure... duplicate a key...

  Hope you get what I'm trying to show here... There is nothing there to prevent another instance to check the existence of the key even before the first instance commits the transaction that inserted the key...

  BPEL is not a mutex AFAIK... something like the statement "synchronized" in Java for example...

  https://docs.Oracle.com/javase/tutorial/essential/concurrency/locksync.html

  Thus, you must use a different approach, for example, try and introduce first always, if the insertion fails try and update... It's 'thread safe' than the approach that you use...

  Much better is to is to abandon controls at all and always insert using the key substitution, such as sequences or guid... If you insert an Oracle database, simply use a sequence, or use the function generate GUIDs BPEL...

  https://en.Wikipedia.org/wiki/Surrogate_key

  See you soon,.

  Vlad

• Unique constraint violation error

  Hi all
  
  I have a procedure called - FHM_DASHBOARD_PROC which inserts data into a table called FHM_DASHBOARD_F retrieve records in multiple tables. However, for a particular type of record, these data are not inserted because of the Unique constraint violation
  
  the procedure is:
  

  create or replace
  PROCEDURE FHM_DASHBOARD_PROC AS
  
  DB_METRICS_CNT1Z number;
  --V_PODNAME varchar2(10);
  V_KI_CODE_DB_STATSZ varchar2(50);
  V_ERRORSTRING varchar2(100);
  
  --CURSOR PODNAME_CUR IS SELECT PODNAME,SHORTNAME FROM CRMODDEV.POD_DATA WHERE PODSTATUS_ID=1 AND PODTYPE_ID=1 ORDER BY PODNAME;
  
  
  -- DB STATS
  
  BEGIN 
  
    -- OPEN PODNAME_CUR;
      --   LOOP
        --   FETCH PODNAME_CUR INTO V_PODNAME,V_POD_SHORTNAME ;
          -- EXIT WHEN PODNAME_CUR%NOTFOUND;
  
             BEGIN
             
                   SELECT COUNT(*) INTO DB_METRICS_CNT1Z FROM FHM_DB_METRICS_F A, FHM_DB_D B where A.DBNAME=B.DBNAME and PODNAME=V_PODNAME AND DB_DATE=TRUNC(SYSDATE-1);
                             DBMS_OUTPUT.PUT_LINE('DB_METRICS_CNT1Z :'|| DB_METRICS_CNT1Z);
                             IF DB_METRICS_CNT1Z >0 THEN
                           
                      DBMS_OUTPUT.PUT_LINE('DB STATS');
                                
                     INSERT INTO FHM_DASHBOARD_F(PODNAME,DASH_DATE,KI_CODE,KI_VALUE,KI_STATUS)
                                
                        (SELECT PODNAME, DASH_DATE AS CU_DATE, KI.KI_CODE, NVL(PF.KI_VALUE,0), 
                                                                CASE
                                                                 WHEN PF.KI_VALUE = ki.warning_threshold then 2
                      when PF.KI_VALUE=0 then 0
                      ELSE 1 
                      END  AS ALERT_STATUS
                      
                      FROM 
                      
                      (SELECT PODNAME,DB_DATE AS DASH_DATE,decode(a.stats_last_status,'SUCCEEDED',1,'FAILED',2,'STOPPED',2,NULL,0) KI_VALUE from  
                      FHM_DB_METRICS_F a,fhm_db_d b where a.dbname=b.dbname and podname='XYZ' and db_date=TRUNC(SYSDATE-1) and dbtype='OLTP')PF,
                      FHM_KEY_INDICATOR_D KI where PF.PODNAME=KI.POD_NAME AND KI.TIER_CODE=3 AND KI.KI_NAME='DB_STATS'
                      AND (PF.PODNAME,TRUNC(PF.DASH_DATE),KI.KI_CODE) NOT IN (SELECT PODNAME,DASH_DATE,KI_CODE FROM FHM_DASHBOARD_F)); 
                               COMMIT;
                   
                           ELSE
                                  SELECT KI_CODE INTO V_KI_CODE_DB_STATSZ FROM FHM_KEY_INDICATOR_D WHERE POD_NAME=V_PODNAME AND KI_NAME='DB_STATS';
                                   DBMS_OUTPUT.PUT_LINE('V_KI_CODE_DB_STATSZ :'||V_KI_CODE_DB_STATSZ);
                                   INSERT INTO FHM_DASHBOARD_F(PODNAME,DASH_DATE,KI_CODE,KI_VALUE,KI_STATUS) VALUES(V_PODNAME,TRUNC(SYSDATE-1),V_KI_CODE_DB_STATSZ,0,0); 
                                   COMMIT; 
                                   
                           END IF;
                          
       EXCEPTION
                          WHEN OTHERS THEN
                          V_ERRORSTRING :='INSERT INTO FHM_DASHBOARD_F_ERROR_LOG(POD_NAME,KI_NAME,ERRORNO,ERRORMESSAGE,DATETIME) VALUES
                 ('''||V_PODNAME||''',''DB_STATS'','''||SQLCODE||''','''||SQLERRM||''',SYSDATE)';                         
                 EXECUTE IMMEDIATE  V_ERRORSTRING;
                          COMMIT;
            END;
  
        --END LOOP;
    --CLOSE PODNAME_CUR;
  
  
  END;
  
  
  END FHM_DASHBOARD_PROC;

  and the table where data integration is
  

  CREATE TABLE "CRMODDEV"."FHM_DASHBOARD_F"
    (
      "PODNAME" VARCHAR2(25 BYTE) NOT NULL ENABLE,
      "DASH_DATE" DATE,
      "KI_CODE"   NUMBER NOT NULL ENABLE,
      "KI_VALUE"  NUMBER,
      "KI_STATUS" NUMBER,
      CONSTRAINT "FHM_DASHBOARD_F_DATE_PK" PRIMARY KEY ("DASH_DATE", "PODNAME", "KI_CODE") USING INDEX PCTFREE 10 INITRANS 2 MAXTRANS 255 NOLOGGING COMPUTE STATISTICS STORAGE(INITIAL 4194304 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT) TABLESPACE "CRMODDEV_IDX" ENABLE,
      CONSTRAINT "FHM_DASHBOARD_F_KI_CODE_FK" FOREIGN KEY ("KI_CODE") REFERENCES "CRMODDEV"."FHM_KEY_INDICATOR_D" ("KI_CODE") ENABLE
    )
    PCTFREE 10 PCTUSED 40 INITRANS 1 MAXTRANS 255 NOCOMPRESS NOLOGGING STORAGE
    (
      INITIAL 3145728 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT
    )
    TABLESPACE "CRMODDEV_TBL" ENABLE ROW MOVEMENT ;

  the constraint primary key is FHM_DASHBOARD_F_DATE_PK and is on 3 columns of the table, DASH_DATE, PODNAME, KI_CODE
  
  
  
  And it's the query used in the procedure to insert the data into the table
  

  (SELECT  PODNAME, DASH_DATE AS CU_DATE, KI.KI_CODE, NVL(PF.KI_VALUE,0), 
                                 CASE
                                 WHEN PF.KI_VALUE = ki.warning_threshold then 2
  when PF.KI_VALUE=0 then 0
  ELSE 1 
  END  AS ALERT_STATUS
  From 
  (Select  Podname,Db_Date As Dash_Date,Decode(A.Stats_Last_Status,'SUCCEEDED',1,'FAILED',2,'STOPPED',2,Null,0) Ki_Value From  -- Added Distinct
  FHM_DB_METRICS_F a,fhm_db_d b where a.dbname=b.dbname and podname in ('XYZ') and db_date = TRUNC(SYSDATE-2) and dbtype='OLTP')PF,
  Fhm_Key_Indicator_D Ki Where Pf.Podname=Ki.Pod_Name And Ki.Tier_Code=3 And Ki.Ki_Name='DB_STATS'
  And (Pf.Podname,Trunc(Pf.Dash_Date),Ki.Ki_Code) Not In (Select Podname,Dash_Date,Ki_Code From Fhm_Dashboard_F));

  It gives * record * 2 suite
  ---------------------------------------
  XYZ JANUARY 20 12 2521 1 1
  XYZ JANUARY 20 12 2521 1 1
  
  It gives the Unique constraint violation error when inserting. Then, I changed in the above insertion code by adding a distinct clause. Once the query gives only a SINGLE record accordingly. However, this record is not be inserted into the table and give the same error.
  
  Now the question is how should I insert that record into the table with success?
  
  
  If the message is too long, however, I gave you the real structure of the object or procedure and error.
  
  Thank you in advance.

  When you have 5 columns in the game adding THAT SEPARATE is n ot solution that you can still get the same error once.

  Check the target table if the data exists before inserting... If this is not the case, check the structure of the table for a unique constraint created on other columns.

  select *from 
  where
  DASH_DATE=date '2012-01-20'
  and PODNAME='XYZ'
  and  KI_CODE=2521;
  

• How to make Unique key Validation

  ADF 11, ADF, BC.
  I could be missing something, but how do you add a validator for a unique key?
  
  I have a unique key defined on the DB, this unique key has nothing to do with the primary key.
  (Its audit that a code is unique)
  
  In the validators on the entity object, I can put a unique key validator, but it lists only the
  primary key for the definition of not check unique key...
  
  The unique key on the DB works as I get a nice constraint violation error, so how can I
  Add a validator to a single key or at least catch the error to display a friendly message.
  
  Concerning
  Paul

  Hello Paul,

  My recommendation would be to leave the validation of the uniqueness constraint in the DB. Have a read of the article 37.8.3 (updated for 11g, 10 g, it is 33.8.3) guide the developer of Fusion, where you will find a way to provide your own rather than the ugly constraint violation a nice error messages.

  Best,

  John

• Database error: key Violation.

  Hi all
  
  I face this problem while I try to add a user in the comic book.
  
  Database error: key Violation.
  ORA-00001: unique constraint (PRD. PK_DRIVER_007) violated.
  
  May - so that someone knows how to fix this?
  
  Thank you

  The power function

  you have created the index on Resourceid column of the table of driver which is unique, but you're insterting data dubplicate.

  So either delete this index

  Drop index PK_driver_007;

  Or donot insert duplicate values in Resourceid driver table column.

• Replace the unique key on Satellite L500-128

  Hi all

  Today, I removed the key from my computer toshiba laptop +. When I tried to replace it, I saw that the clip under the key has been broken. So now, I want to know if I can buy the clip so I can connect my key with the keyboard again. I don't want to buy a new keyboard. It's a waste of money, because the rest of the keyboard is in a very good state. I'm from the Netherlands.

  With sincere friendships.

  Tom

  Hello

  Maybe it's hard to hear but I think that Akuma is good and you can t replace individual keys only. Only a full keyboard is available and can be ordered and no Exchange, no unique key. The authorized service provider in my country told me that the information

  So I think you need to order a set of keyboard of an authorized service provider.
  But don t worry not about this. Keyboards are not so expensive. ;)

• ODI is recovering not Unique key constraint

  I created a table with script below and reverse engineering it.

  create table test
  (primary_id number,
   unique_not_null_ID number not null,
    col3 number,
   col4 varchar2(200),
   col5 varchar2(2000),
  primary key (primary_id),
  unique (unique_not_null_ID) 
  )
  

  But all looking in the constraint of the data store only the primary key is here

  Also, within the quick edit tab Interface is show

  (1) Primary_id: = UK and CN of check

  (2) Unique_not_null_id: = CN is the Coachman

  
  

  So, why there no Unique constraint picked up?

  
  

  I think then it will only mark it too fast Edition.
  

  Hi spear,

  Please note that during standard reverse engineering unique keys are not reverse engineering. Then you need to either do reverse engineering on measurement or add a unique touch to the ODI level.

  https://docs.Oracle.com/CD/E28280_01/integrate.1111/e12643/create_rev_model.htm#ODIDG225

• How to avoid the report query needs a unique key to identify each line

  Hello

  How to avoid the error below

  The report query needs a unique key to identify each row. The supplied key cannot be used for this query. Please change the report attributes to define a unique key column.

  I have master-detail tables but without constraints, when I created a query as dept, emp table he gave me above the error.

  Select d.deptno, e.ename

  by d, e emp dept

  where e.deptno = d.deptno

  Thank you and best regards,

  Ashish

  Hi mickael,.

  Work on interactive report?

  You must set the column link (in the attributes report) to something other than "link to display single line." You can set it to 'Exclude the column link' or 'target link to Custom.

• Why we cannot create more than one primary key on a table. Why we create several unique key on a table. Please explain if anyone have details of this.

  Why we cannot create more than one primary key on a table. Why we create several unique key on a table. Please explain if anyone have details of this.

  «a primary key has semantic meaning, it is to be immutable (never change of value), unique and not null.»

  a unique constraint is simply "at any time, these values are unique - they can change and they can be null.

  You use a unique when constraint

  (a) you do not already have a primary key for a table can have only one
  (b) you allow NULL values in attributes
  "(c) to allow you to update the values in the attributes.

  https://asktom.Oracle.com/pls/Apex/f?p=100:11:0:P11_QUESTION_ID:5541352100346689891

• table partitioned and unique keys

  I really don't understand why Oracle does not apply in some cases, unique keys.

  Let's say I have a table

  create table t (t_type not null, t_key not null, id not null, not null value)

  list partition (t_type)

  (

  type1 partition values ('ppp1"),

  rest of partition (default) values

  ) as

  Select "ppp" | rownum, rownum, rownum, rownum of double connect by rownum < = 100;

  And following changes in the indices for unique keys

  -1

  create index idx_1 on t (t_key, id);

  ALTER table t add constraint t_uk unique (t_key) using index idx_1;

  ALTER table drop constraint t_uk drop index;

  -2

  create index idx_1 on t (t_key, id, t_type);

  ALTER table t add constraint t_uk unique (t_key) using index idx_1;

  ALTER table drop constraint t_uk drop index;

  -3

  create index idx_1 on t (t_key, id, t_type) local;

  ALTER table t add constraint t_uk unique (t_key) using index idx_1;

  Drop index idx_1;

  -4

  create an index only idx_1 on t (t_key, id);

  ALTER table t add constraint t_uk unique (t_key) using index idx_1;

  Drop index idx_1;

  -5

  create an index only idx_1 on t (t_key, id, t_type);

  ALTER table t add constraint t_uk unique (t_key) using index idx_1;

  Drop index idx_1;

  -6

  create an index only idx_1 on t (t_key, id, t_type) local;

  ALTER table t add constraint t_uk unique (t_key) using index idx_1;

  Drop index idx_1;

  -7

  create index idx_1 on t (t_key, t_type, id) local;

  ALTER table t add t_uk unique constraint (t_key, t_type) using index idx_1;

  ALTER table drop constraint t_uk drop index;

  -8

  create an index only idx_1 on t (t_key, t_type, id) local;

  ALTER table t add t_uk unique constraint (t_key, t_type) using index idx_1;

  Drop index idx_1;

  I got the set of questions:

  1. first and second cases were performed with success while 4th and 5th failed.

  The only difference is that the overall index in 4th and 5th cases are unique.

  It is unclear why ' ORA-14196: specified index cannot be used to apply the constraint. ' has occurred.

  2. in the third case index is similar to that in second place with the only difference that it is local.

  Still, it is not clear why it failed with ORA-14196.

  3 and the last question why ORA-14196 arose in 8 cases, while the 7th, it didn't.

  The only difference is the local index in 8 cases is unique.

  Thank you

  Hi Alex

  (1) index 4 and 5 cannot be used to police the unique constraint as a unique index must have the same list of column under duress. Index 4, to establish in a non-unique index or to remove the column id of the index. To index 5, you will need to make a non-unique index or remove the columns id and index t_type.

  (2) 3 index cannot be used to the unique constraint of police that it is a local index and is not partitioned column (t_type) in both the definition of index/constraint. If allowed, this would require Oracle having to visit each partition to ensure that any new value of t_key is truly unique, that would not scale. Include the t_type column in the constraint and the index to both t_type and t_key as of the columns (so move the id column 3rd position) and it would be successful.

  (Index 3) 8 fails for the same reason as in 1). It's a unique index with a different column from the constraint list. Remove the id column of the index or to make it a non-unique index and it will be successful.

  In summary, a unique index MUST have the same list of column than the constraint and a local index MUST have the partitioning columns in both the definition of index/constraint.

  See you soon

  Richard Foote

  http://richardfoote.WordPress.com/

• Please choose a unique key in the selected Recordset or click Cancel - DWCC2015 error

  I am trying to add a form to UPDATE in the PCOC assistance from the server behaviors panel and when I have it, select the unique primary key in my database table, I am presented with the following error:

  "Please choose a unique key in the selected Recordset or click Cancel.

  I tripled checked - the key that I select is correct, it is a primary key in my table of MSSQL database - it does not accept it.

  Any ideas?  Clear the Cache of DW and start over?

  Thank you.

  NJ

  As I suggested in another thread, if you really need to use the obsolete server behaviors, install Dreamweaver CS6, which is included in your subscription to creative cloud. Better yet, stop using the server behaviors. They have been deleted, because the code is desperately obsolete. It will stop working in PHP 7, coming in the next two weeks.

• Short ODI IKM Unique key error

  Hello

  I am trying to load data in and short 3.1 datadomain through the IKM ODI of short downloaded from delivery. I use ODI 11.1.1.1.7 with IKM SQL for short for 3.1. I managed to solve the problem all the way until step 9 of the dataload

  Here are the steps to get that:

  Step 1-4 Drop, Create, load, Analyze table work

  6 - integration - context properties of loading RecordWriter

  7 initialize Logger

  8 validate Options

  9 initialize short schema (ERROR)

  Above step 9 errors with:

  org.apache.bsf.BSFException: exception of Jython:

  Traceback (most recent call changed):

  File "< string >", line 57, < module >

  File '< string >", line 15, in throwException

  at sun.reflect.NativeConstructorAccessorImpl.newInstance0 (Native Method)

  at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:57)

  at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)

  at java.lang.reflect.Constructor.newInstance(Constructor.java:525)

  at org.python.core.PyReflectedConstructor.constructProxy(PyReflectedConstructor.java:163)

  java.lang.Exception: java.lang.Exception: there is no unique key in the schema

  at org.apache.bsf.engines.jython.JythonEngine.exec(JythonEngine.java:146)

  at com.sunopsis.dwg.codeinterpretor.SnpScriptingInterpretor.execInBSFEngine (SnpScripting

  
  

  I'm sure I'm missing something and I can't find it in the documentation. Help, please.

  
  

  Thanks in advance.
  

  This cased by you did not indicate the unique key in your column of your data store in the models.

  1 extend the data store in the models.

  2. expand the attributes

  3. double-click on the PK column you want

  4. click on the Flexfields

  5 uncheck "short property is Unique.

  Or you do not want to set a short Server Unique key and let the server automatically generate the PK.

  You can open your interface and in the configuration of IKM together the value of 'AUTO_GENERATE_RECORSPEC' is true.

• Engineering problems the surrogate with Unique key primary key

  SDDM 3.3.0.747 with 2 problems (at least so far).  I hope that the problem comes from this recruit SDDM and I forgot a setting. PROBLEM 1 I don't want to start a religious debate on substitution vs natural keys but I'm having a problem correctly both the logic model of engineering.  I'm a rookie when it comes to SDDM but have many years of experience with the Designer. By default, only I wish I had a natural UID (UK) and a surrogate mother based on a primary key UID (PK) which is used for foreign keys.  The problem I have with engineering is I can successfully engineer the substitute PK, engineer of the FK with the PK, but cannot get the unique key to contain surrogate keys in the child table.  If I check the identification property in relationships, the PK columns and the UK are included in the child PK and the United Kingdom contains no columns. The installation program, I've defined two reference entities, PROBABILITY and GRAVITY with unique keys natural defined.  I also have a child entity RISK_ASSESMENT with links to entities of the PROBABILITY and SEVERITY and both have the "use surrogate keys:": check box selected.  The unique key of the entity RISK_ASSESMENT includes links to PROBILITY and GRAVITY.  None of the entities have a PK or replacement of the defined keys and they all have the checkbox "Create a surrogate key" checked.  In addition the following preferences are defined: Data Modeling/model/logic NO checked - use and the first Unique key as primary key value NOT checked - name - Keep under the name of the from attribute Checked - entity carrier to create controlled key - use surrogate PROBLEM 2 key relationship when the foreign key columns are engineered I want names have a prefix 'FK_"but they don't.  Models are defined as follows: Data Modeler/assignment of Standard/Templates Foreign Key name: FK_ {children} {parent} foreign key column: engineer FK_ {Ref column} relational model/General checked Options - translation name Marcus Bacon apply

  Once more, I designed without removing anything and still no FK to the United Kingdom of the child.

  There is a synchronization problem in DM 4.0 EA1. This will be fixed for the production version.

  Philippe

• Potential problems for tables without primary keys and unique keys

  GoldenGate 11.2.1.0.3/Solaris 10
  DB: Oracle for Oracle (Source and target is 11.2.0.3)
  Topology: unidirectional
  
  
  In our one-way configuration GG, little of the tables being replicated is not a primary key or a Unique key.
  
  Last week when we have implemented GG for the test, we received warnings for these table below.
  

  GGSCI > add trandata WMHS_UD.crtn_dtl
  
  2013-01-12 11:34:33  WARNING OGG-00869  No unique key is defined for table 'CRTN_DTL'. All viable columns will be used to represent the key, but may not guarantee uniqueness.  KEYCOLS may be used to define the key.
  
  Logging of supplemental redo data enabled for table WMHS_UD.crtn_dtl.

  Replication seems to work very well for these tables.
  
  Googling, I think that there may be performance degradation when you replicate tables without PK or the United Kingdom.
  
  But are there other potential problems such as data of a certain kind not replicated to the lack of PK/UK?

  It really depends on the data.

  By default, GG is combining all columns as a virtual primary key but don't no conflict control by default. So when you can be sure that the record you insert into the table is unique, then it will work.
  BUT as soon as you insert the same record, which is already inserted, then you will encounter problems.

  Let me show what happens when you use an initial charge because it makes it easier to describe:
  We start at 10:00 the capture for a table. Now, you insert a record at 10:00 in the tables. When you now start an initial charge to 10.02, then check you have inserted in the database to 10.01 will be repeated two times. During the IPL as the initial charge is made to 10.02 and it includes data of 10.01 AND it will be replicated again through the process of capture/replicate.

• Number of unique key in a table column

  Hi all...
  
  
  Please help me with this problem. Looking for the number of threads, but could not understand how do.
  
  
  I have a master form / retail users (main table) and responsibilities (detail table).
  The problem is with the table Details (responsibilities), the detail is "" "FORM TABULAR" ".
  A user can have the following responsibilities RESP1, RESP2, RESP3, RESP4 (it's a '' select list' ")
  
  
  When the administrator creates users, they will strike "" Add line"," once they choose a responsibility of the selection list.
  When they hit add line once again, "'chosen responsibility should display in the selection list.
  
  
  EX: when they select RESP "RESP1' in the first row, if they hit add line once again,"RESP1"does not present it as an option for users to select.
  
  
  EX: If the user already has an RESP "" RESP3"" in the database, "'' RESP3" ' should not display if they try to add another RESP.
  
  Each select list should display different values depend on the values they have chosen so far *.
  
  -> we can put constaint unique key on this column or put validation on this page, but I'm looking for the implementation
  
  
  Please check the following application example:
  
  
  http://Apex.Oracle.com/pls/Apex/f?p=42177
  
  
  Please help me in this task
  
  Thank you

  There is no way to declaratively in the Apex to do this.

  In version 4.x:
  1. There is no declarative way to dynamically filter a list of values in a tabular presentation. For each line, the LOV is actually pre-built on a hidden row zero when the page first appears.
  2. to do this, you will need to come up with a process, possibly including AJAX, to fill an array of values to the selection list, delete the values in the table if they have been selected on the other lines of the page and then re - fill the selection on the new list online.

  In version 3.x:
  1 lines are stored in the database every time that you add a row (actually the page saves and repainted with a new line). You can set your LOV SQL to return the values valid less those already stored in the database that the user adds lines.
  2. However, that won't necessarily work 100% if you look at a page with several lines already on it and want to update the existing lines and you need in any case a sort of validation or a unique constraint.

  It is not impossible, but it's very very labor intensive and maintainability is more difficult if another developer a year or two down the road to inherit this page you.

  I'd really like to tell your business analyst or key functional end users what they ask for is not supported by Apex first review (and to tell you the truth, it is indeed non-supported, so you are not lying down or fake apology) and they consider like allowing more traditional validation via a unique constraint and page validation.