Add a unique constraint on binary XML table

How add a unique constraint of "brevet" field?
The following INSERT failed
SQL Error: ORA-19025: EXTRACTVALUE renvoie la valeur d'un seul noeud
19025. 00000 - "EXTRACTVALUE returns value of only one node"
If the ALTER is made after the INSERT is done, INSERT is valid but ALTER failed with the same error message!
/* copy the file compavions.xml
<?xml version="1.0" encoding="ISO-8859-1"?>
<compagnie>
     <comp>AB</comp>
     <flotte>
          <avion immat="F-WTSS" capacite="90">
               <typeAv>Concorde</typeAv>
          </avion>
          <avion immat="F-GFDR" capacite="145">
               <typeAv>A320</typeAv>
          </avion>
          <avion immat="F-GTYA" capacite="150">
               <typeAv>A320</typeAv>
          </avion>
     </flotte>
     <nomComp>Air Blagnac</nomComp>
     <pilotes>
          <pilote>
          <brevet>PL-1</brevet>
          <nom>C. Sigaudes</nom>
          </pilote>
          <pilote>
          <brevet>PL-2</brevet>
          <nom>P. Filloux</nom>
          </pilote>
     </pilotes>
</compagnie>
in C:\...
--DROP DIRECTORY repxml;
--CREATE DIRECTORY repxml AS 'C:\...';
DROP TABLE pilote_binary_xml5;
CREATE TABLE pilote_binary_xml5 OF XMLType
XMLTYPE STORE AS BINARY XML
VIRTUAL COLUMNS
(col AS (EXTRACTVALUE(OBJECT_VALUE, '/compagnie/pilotes/pilote/brevet')));
ALTER TABLE pilote_binary_xml5 ADD CONSTRAINT brevet_unique UNIQUE (col);
INSERT INTO pilote_binary_xml5 VALUES (XMLType(BFILENAME ('REPXML','compavions.xml'), NLS_CHARSET_ID ('AL32UTF8')));
--ALTER TABLE pilote_binary_xml5 ADD CONSTRAINT brevet_unique UNIQUE (col);

You could try something like
(extract(OBJECT_VALUE,compagnie/pilotes/pilote/brevet').getStringVal());
but this is probably unadvisable.
I suggest an alternative is for you to look at XMLINDEX so that you can bring the 'proper' XML functions into play like XMLTABLE etc.

Similar Messages

Migrate B-Tree Indexes of XML O-R Table to XMLIndex on Binary XML Table

We need slight help on how to migrate existing B-TREE Indexes from XML Obj-Rel Tables to XMLIndex on new XML Binary Tables
We use searches on Nested Collection Elements (defined unbounded in XSD)
and related DDL for XML Obj-Rel Tables is shown below:
CREATE TABLE TNMAB_AGREEMENT_XML
AGREEMENT_XML xmltype,
CREATE_BY     VARCHAR2(15) NULL ,
CREATE_DT_GMT     TIMESTAMP NULL ,
CREATE_CLIENT_ID VARCHAR2(65) NULL ,
UPDATE_BY     VARCHAR2(15) NULL ,
UPDATE_DT_GMT     TIMESTAMP NULL ,
UPDATE_CLIENT_ID VARCHAR2(65) NULL ,
PIC_VERSION_NUM     NUMBER(20) NULL
XMLTYPE COLUMN AGREEMENT_XML XMLSCHEMA "AB_Agreement_V1_XMLDB.xsd" ELEMENT "Agreement"
VARRAY AGREEMENT_XML.XMLDATA."SHIPPING_PARTY_GROUPS"
STORE AS TABLE SHIPPING_PARTY_GROUPS_NT
(PRIMARY KEY (NESTED_TABLE_ID, ARRAY_INDEX) ENABLE)
VARRAY SHIPPING_PARTIES
STORE AS TABLE SHIPPING_PARTIES_NT
(PRIMARY KEY (NESTED_TABLE_ID, ARRAY_INDEX) ENABLE)
VARRAY AGREEMENT_XML.XMLDATA."SALES_OFFICE_CODES"."STRING_WRAPPERS"
STORE AS TABLE SALES_OFFICE_CODES_NT
(PRIMARY KEY (NESTED_TABLE_ID, ARRAY_INDEX) ENABLE)
TABLESPACE TNMAB_XMLDB_ME_DATA;
Table has PK and Unique Index which for the Binary XML Table, it will be setup on Virtual Columns (to enforce
Unique Constraints)
We have 6 more Normal Indexes on this Table, some created on Nested Elements as shown below:
-- 4 Normal B-TREE Indexes on Leaf level Elements
create index TNMAB_AGREEMENT_XML_IDX1 on TNMAB_AGREEMENT_XML (AGREEMENT_XML.XMLDATA."AGREEMENT_VERSION")
tablespace TNMAB_XMLDB_ME_INDX;
create index TNMAB_AGREEMENT_XML_IDX2 on TNMAB_AGREEMENT_XML (AGREEMENT_XML.XMLDATA."LAST_UPDATED_BY")
tablespace TNMAB_XMLDB_ME_INDX;
create index TNMAB_AGREEMENT_XML_IDX3 on TNMAB_AGREEMENT_XML (AGREEMENT_XML.XMLDATA."LAST_UPDATED")
tablespace TNMAB_XMLDB_ME_INDX;
create index TNMAB_AGREEMENT_XML_IDX4 on TNMAB_AGREEMENT_XML (AGREEMENT_XML.XMLDATA."CREATION_DATE")
tablespace TNMAB_XMLDB_ME_INDX;
--2 Indexes created on Nested Table (Collection)
create index TNMAB_AGREEMENT_XML_NT_IDX1 on SALES_OFFICE_CODES_NT NT(NT.STR_VAL, NT.NESTED_TABLE_ID)
tablespace TNMAB_XMLDB_ME_INDX;
create index TNMAB_AGREEMENT_XML_NT_IDX2 on SHIPPING_PARTIES_NT NT(NT.CUSTOMER_HOLDER.SAP_ID, NT.NESTED_TABLE_ID)
tablespace TNMAB_XMLDB_ME_INDX;
Could you please let us know how we should migrate above Indexes to XMLIndex format.
Specifically, not sure how the last 2 Indexes on Nested Tables is to be defined.
Any help or resources pointing to this would be greatly appreciated.
Thanks for the help,
Auro

Can't tell due to using XMLDATA pseudocolumn. Would need a sample XML document structure that can be used to define the XPATH structure and ALSO need the database version you are using (ALL digits) to see if you would need / can use STRUCTURED or UNSTRUCTURED XMLINDEX indexes.
See the XML Index section (http://www.liberidu.com/blog/?page_id=441) on for guidance and/or of course the XMLDB Developers Guide for your database version
http://www.liberidu.com/blog/?page_id=441
XMLIndex (part 1) – The Concepts
XMLIndex (Part 2) – XMLIndex Path Subsetting
XMLIndex (Part 3) – XMLIndex Syntax Dissected
XMLIndex Performance and Fuzzy XPath Searches
Structured XMLIndex (Part 1) – Rules of Numb
Structured XMLIndex (Part 2) – Howto build a structured XMLIndex
Structured XMLIndex (Part 3) – Building Multiple XMLIndex Structures

How to add an unique column to an existing table?

How to add an unique column to an existing table?
I have a large table which has no unique constraint. and I want to add an unique column for it. How to do it?
Does adding a sequence is a good choice? How to do it?
Thank you

Hi,
alter table tablename
add constraint contraint_name unique (columnname);but before that you need to check in the table.column there is no duplicate record exist.
Does adding a sequence is a good choice?
Your talking about unique constraint then yes.
Regards,
Taj

Why Isn't xmlindex being used in slow query on binary xml table eval?

I am running a slow simple query on Oracle database server 11.2.0.1 that is not using an xmlindex. Instead, a full table scan against the eval binary xml table occurs. Here is the query:
select -- /*+ NO_XMLINDEX_REWRITE no_parallel(eval)*/
      defid from eval,
      XMLTable(XMLNAMESPACES(DEFAULT 'http://www.cigna.com/acme/domains/eval/2010/03',
      'http://www.cigna.com/acme/domains/derived/fact/2010/03' AS "ns7"),
      '$doc/eval/derivedFacts/ns7:derivedFact' passing eval.object_value as "doc" columns defid varchar2(100) path 'ns7:defId'
       ) eval_xml
where eval_xml.defid in ('59543','55208'); The predicate is not selective at all - the returned row count is the same as the table row count (325,550 xml documents in the eval table). When different values are used bringing the row count down to ~ 33%, the xmlindex still isn't used - as would be expected in a purely relational nonXML environment.
My question is why would'nt the xmlindex be used in a fast full scan manner versus a full table scan traversing the xml in each eval table document record?
Would a FFS hint be applicable to an xmlindex domain-type index?
Here is the xmlindex definition:
CREATE INDEX "EVAL_XMLINDEX_IX" ON "EVAL" (OBJECT_VALUE)
INDEXTYPE IS "XDB"."XMLINDEX" PARAMETERS
('XMLTable eval_idx_tab XMLNamespaces(DEFAULT ''http://www.cigna.com/acme/domains/eval/2010/03'',
''http://www.cigna.com/acme/domains/derived/fact/2010/03'' AS "ns7"),''/eval''
       COLUMNS defId VARCHAR2(100) path ''/derivedFacts/ns7:derivedFact/ns7:defId''');Here is the eval table definition:
CREATE
TABLE "N98991"."EVAL" OF XMLTYPE
    CONSTRAINT "EVAL_ID_PK" PRIMARY KEY ("EVAL_ID") USING INDEX PCTFREE 10
    INITRANS 4 MAXTRANS 255 COMPUTE STATISTICS STORAGE(INITIAL 65536 NEXT
    1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0 FREELISTS 1
    FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT CELL_FLASH_CACHE
    DEFAULT) TABLESPACE "ACME_DATA" ENABLE
XMLTYPE STORE AS SECUREFILE BINARY XML
    TABLESPACE "ACME_DATA" ENABLE STORAGE IN ROW CHUNK 8192 CACHE NOCOMPRESS
    KEEP_DUPLICATES STORAGE(INITIAL 106496 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS
    2147483645 PCTINCREASE 0 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT
    CELL_FLASH_CACHE DEFAULT)
ALLOW NONSCHEMA ALLOW ANYSCHEMA VIRTUAL COLUMNS
    "EVAL_DT" AS (SYS_EXTRACT_UTC(CAST(TO_TIMESTAMP_TZ(SYS_XQ_UPKXML2SQL(
    SYS_XQEXVAL(XMLQUERY(
    'declare default element namespace "http://www.cigna.com/acme/domains/eval/2010/03"; (::)
/eval/@eval_dt'
    PASSING BY VALUE SYS_MAKEXML(128,"XMLDATA") RETURNING CONTENT ),0,0,
    16777216,0),50,1,2),'SYYYY-MM-DD"T"HH24:MI:SS.FFTZH:TZM') AS TIMESTAMP
WITH
TIME ZONE))),
    "EVAL_CAT" AS (CAST(SYS_XQ_UPKXML2SQL(SYS_XQEXVAL(XMLQUERY(
    'declare default element namespace "http://www.cigna.com/acme/domains/eval/2010/03";/eval/@category'
    PASSING BY VALUE SYS_MAKEXML(128,"XMLDATA") RETURNING CONTENT ),0,0,
    16777216,0),50,1,2) AS VARCHAR2(50))),
    "ACME_MBR_ID" AS (CAST(SYS_XQ_UPKXML2SQL(SYS_XQEXVAL(XMLQUERY(
    'declare default element namespace "http://www.cigna.com/acme/domains/eval/2010/03";/eval/@acmeMemberId'
    PASSING BY VALUE SYS_MAKEXML(128,"XMLDATA") RETURNING CONTENT ),0,0,
    16777216,0),50,1,2) AS VARCHAR2(50))),
    "EVAL_ID" AS (CAST(SYS_XQ_UPKXML2SQL(SYS_XQEXVAL(XMLQUERY(
    'declare default element namespace "http://www.cigna.com/acme/domains/eval/2010/03";/eval/@evalId'
    PASSING BY VALUE SYS_MAKEXML(128,"XMLDATA") RETURNING CONTENT ),0,0,
    16777216,0),50,1,2) AS VARCHAR2(50)))
PCTFREE 0 PCTUSED 80 INITRANS 4 MAXTRANS 255 NOCOMPRESS LOGGING STORAGE
    INITIAL 65536 NEXT 1048576 MINEXTENTS 1 MAXEXTENTS 2147483645 PCTINCREASE 0
    FREELISTS 1 FREELIST GROUPS 1 BUFFER_POOL DEFAULT FLASH_CACHE DEFAULT
    CELL_FLASH_CACHE DEFAULT
TABLESPACE "ACME_DATA" ; Sample cleansed xml snippet:
<?xml version = '1.0' encoding = 'UTF-8' standalone = 'yes'?><eval createdById="xxxx" hhhhMemberId="37e6f05a-88dc-41e9-a8df-2a2ac6d822c9" category="eeeeeeee" eval_dt="2012-02-11T23:47:02.645Z" evalId="12e007f5-b7c3-4da2-b8b8-4bf066675d1a" xmlns="http://www.xxxxx.com/vvvv/domains/eval/2010/03" xmlns:ns2="http://www.cigna.com/nnnn/domains/derived/fact/2010/03" xmlns:ns3="http://www.xxxxx.com/vvvv/domains/common/2010/03">
   <derivedFacts>
      <ns2:derivedFact>
         <ns2:defId>12345</ns2:defId>
         <ns2:defUrn>urn:mmmmrunner:Medical:Definition:DerivedFact:52657:1</ns2:defUrn>
         <ns2:factSource>tttt Member</ns2:factSource>
         <ns2:origInferred_dt>2012-02-11T23:47:02.645Z</ns2:origInferred_dt>
         <ns2:factValue>
            <ns2:type>boolean</ns2:type>
            <ns2:value>true</ns2:value>
         </ns2:factValue>
      </ns2:derivedFact>
      <ns2:derivedFact>
         <ns2:defId>52600</ns2:defId>
         <ns2:defUrn>urn:ddddrunner:Medical:Definition:DerivedFact:52600:2</ns2:defUrn>
         <ns2:factSource>cccc Member</ns2:factSource>
         <ns2:origInferred_dt>2012-02-11T23:47:02.645Z</ns2:origInferred_dt>
         <ns2:factValue>
            <ns2:type>string</ns2:type>
            <ns2:value>null</ns2:value>
         </ns2:factValue>
      </ns2:derivedFact>
      <ns2:derivedFact>
         <ns2:defId>59543</ns2:defId>
         <ns2:defUrn>urn:ddddunner:Medical:Definition:DerivedFact:52599:1</ns2:defUrn>
         <ns2:factSource>dddd Member</ns2:factSource>
         <ns2:origInferred_dt>2012-02-11T23:47:02.645Z</ns2:origInferred_dt>
         <ns2:factValue>
            <ns2:type>string</ns2:type>
            <ns2:value>INT</ns2:value>
         </ns2:factValue>
      </ns2:derivedFact>
            With the repeating <ns2:derivedFact> element continuing under the <derivedFacts>The Oracle XML DB Developer's Guide 11g Release 2 isn't helping much...
Any assitance much appreciated.
Regards,
Rick Blanchard

odie 63, et. al.;
Attached is the reworked select query, xmlindex, and 2ndary indexes. Note: though namespaces are used; we're not registering any schema defns.
SELECT /*+ NO_USE_HASH(eval) +/ --/*+ NO_QUERY_REWRITE no_parallel(eval)*/
eval_xml.eval_catt, df.defid FROM eval,
--df.defid FROM eval,
XMLTable(XMLNamespaces( DEFAULT 'http://www.cigna.com/acme/domains/eval/2010/03',
                        'http://www.cigna.com/acme/domains/derived/fact/2010/03' AS "ns7" ),
        '/eval' passing eval.object_value
         COLUMNS
           eval_catt VARCHAR2(50) path '@category',
           derivedFact XMLTYPE path '/derivedFacts/ns7:derivedFact')eval_xml,
XMLTable(XMLNamespaces('http://www.cigna.com/acme/domains/derived/fact/2010/03' AS "ns7",
                          DEFAULT 'http://www.cigna.com/acme/domains/eval/2010/03'),
        '/ns7:derivedFact' passing eval_xml.derivedFact
         COLUMNS
           defid VARCHAR2(100) path 'ns7:defId') df
WHERE df.defid IN ('52657','52599') AND eval_xml.eval_catt LIKE 'external';
--where df.defid = '52657';
SELECT /*+ NO_USE_HASH(eval +/ --/*+ NO_QUERY_REWRITE no_parallel(eval)*/
eval_xml.eval_catt, df.defid FROM eval,
--df.defid FROM eval,
XMLTable(XMLNamespaces( DEFAULT 'http://www.cigna.com/acme/domains/eval/2010/03',
                        'http://www.cigna.com/acme/domains/derived/fact/2010/03' AS "ns7" ),
        '/eval' passing eval.object_value
         COLUMNS
           eval_catt VARCHAR2(50) path '@category',
           derivedFact XMLTYPE path '/derivedFacts/ns7:derivedFact')eval_xml,
XMLTable(XMLNamespaces('http://www.cigna.com/acme/domains/derived/fact/2010/03' AS "ns7",
                          DEFAULT 'http://www.cigna.com/acme/domains/eval/2010/03'),
        '/ns7:derivedFact' passing eval_xml.derivedFact
         COLUMNS
           defid VARCHAR2(100) path 'ns7:defId') df
WHERE df.defid IN ('52657','52599') AND eval_xml.eval_catt LIKE 'external';
--where df.defid = '52657'; create index defid_2ndary_ix on eval_idx_tab_II (defID);
     eval_catt VARCHAR2(50) path ''@CATEGORY''');
create index eval_catt_2ndary_ix on eval_idx_tab_I (eval_catt);The xmlindex is getting picked up but a couple of problesm:
1. In the developemnt environment, no xml source records for defid '52657' or '52599' are being displayed - just an empty output set occurs; in spite of these values being present and stored in the source xml.
This really has me stumped, as can query the eval table to see the actual xml defid vaues '52657' and '52599' exist. Something appears off with the query - which didn't return records even before the corrresponding xml index was created.
2. The query still performs slowly, in spite of using the xmlindex. The execution plan shows a full table scan of eval occurring whether or not a HASH JOIN or MERGE JOIN (gets used in place of the HASH JOIN when the NO_USE_HASH(eval) int is used.
3. Single column 2ndary indexes created respectively for eval_catt and defid are not used in the execution plan - which may be expected upon further consideration.
In the process of running stats at this moment, to see if performance improves....
At this point, really after why item '1.' is occurring?
Edited by: RickBlanchardSRSCigna on Apr 16, 2012 1:33 PM

Errors creating indexes on Binary XML Tables

Hi,
Oracle details are as follows:
Oracle Database 11g Enterprise Edition Release 11.2.0.2.0 - 64bit Production
PL/SQL Release 11.2.0.2.0 - Production
"CORE 11.2.0.2.0 Production"
TNS for IBM/AIX RISC System/6000: Version 11.2.0.2.0 - Production
NLSRTL Version 11.2.0.2.0 - Production
I'm currently having an issue when attempting to create a suitable index on a binary xml table. I have a Binary xml table that stores a number of xml documents. I have created an index on this table as follows:
create index TEST_WQI_idx_1 on TEST_WEB_QUOTE_INDX1(OBJECT_VALUE)
INDEXTYPE IS XDB.XMLINDEX
PARAMETERS ('PATHS (INCLUDE
(/webPolicy/QuoteId))');
Querying the table with the following:
SQL> l
1 select xmlcast(xmlquery('/webPolicy/Sections/interopSection[1]/PolicyItems/item/Version/text()' PASSING OBJECT_VALUE RETURNING CONTENT)
2 as number) "VERSION",
3 xmlcast(xmlquery('/webPolicy/QuoteId/text()' PASSING OBJECT_VALUE RETURNING CONTENT)
4 as number) "QUOTEID"
5 FROM TEST_WEB_QUOTE_INDX1
6 where xmlcast(xmlquery('/webPolicy/QuoteId/text()' PASSING OBJECT_VALUE RETURNING CONTENT)
7* as number) = 22824
SQL> /
VERSION QUOTEID
1 22824
Execution Plan
Plan hash value: 3559428808
| Id | Operation | Name | Rows | Bytes | Cost (%CPU)| Time |
| 0 | SELECT STATEMENT | | 545 | 1071K| 1030 (1)| 00:00:19 |
| 1 | SORT AGGREGATE | | 1 | 3022 | | |
|* 2 | TABLE ACCESS BY INDEX ROWID | SYS895336_TEST_WQI__PATH_TABLE | 1 | 3022 | 2 (0)| 00:00:01 |
|* 3 | INDEX RANGE SCAN | SYS895336_TEST_WQI__PIKEY_IX | 1 | | 1 (0)| 00:00:01 |
|* 4 | FILTER | | | | | |
| 5 | TABLE ACCESS FULL | TEST_WEB_QUOTE_INDX1 | 545 | 1071K| 4 (0)| 00:00:01 |
| 6 | SORT AGGREGATE | | 1 | 3022 | | |
|* 7 | TABLE ACCESS BY INDEX ROWID| SYS895336_TEST_WQI__PATH_TABLE | 1 | 3022 | 2 (0)| 00:00:01 |
|* 8 | INDEX RANGE SCAN | SYS895336_TEST_WQI__PIKEY_IX | 1 | | 1 (0)| 00:00:01 |
Predicate Information (identified by operation id):
2 - filter(SYS_XMLI_LOC_ISTEXT("SYS_P0"."LOCATOR","SYS_P0"."PATHID")=1)
3 - access("SYS_P0"."RID"=:B1 AND "SYS_P0"."PATHID"=HEXTORAW('5E6C') )
4 - filter(CAST( (SELECT "SYS"."STRAGG"("SYS_P2"."VALUE") FROM
"WEB_STAGING"."SYS895336_TEST_WQI__PATH_TABLE" "SYS_P2" WHERE "SYS_P2"."PATHID"=HEXTORAW('5E6C') AND
"SYS_P2"."RID"=:B1 AND SYS_XMLI_LOC_ISTEXT("SYS_P2"."LOCATOR","SYS_P2"."PATHID")=1) AS number)=22824)
7 - filter(SYS_XMLI_LOC_ISTEXT("SYS_P2"."LOCATOR","SYS_P2"."PATHID")=1)
8 - access("SYS_P2"."RID"=:B1 AND "SYS_P2"."PATHID"=HEXTORAW('5E6C') )
Note
- dynamic sampling used for this statement (level=2)
- Unoptimized XML construct detected (enable XMLOptimizationCheck for more information)
However, I also need to add an additional field to this index to allow appropriate queries against the data in the table, version number. This field can be seen from the statement above (VERSION) which runs OK and returns the data I’d expect. However, when I attempt to add this index using the following statement I get an error returned and the index becomes corrupted:
alter index TEST_WQI_idx_1 rebuild
parameters ('PATHS (INCLUDE ADD
(/webPolicy/Sections/interopSection[1]/PolicyItems/item/Version))');
After some investigation, the issue seems to revolve around the use of the [1] condition in the statement /interopSection[1]. I can create the index by removing the [1] condition, but this does not return the expected result. In actual fact, as there are 2 interopSection elements in the xml file, both with a version number of 1, the statement returns 11, which would appear to be the two version numbers concatenated together. I need to be able to reference the version number from the first interopSection in the queries against the table, and I need to be able to index this column correctly for performance issues.
I'm unsure why this xpath statement is not working correctly in the alter index statement, but returns ok when used within the query against the table and was wondering if you would be able to help me to have a working index against this element.
Thanks in advance for any help you can provide in relation to this.

Sorry, here is the error:
Error starting at line 20 in command:
alter index TEST_WQI_idx_1 rebuild
parameters ('PATHS (INCLUDE ADD
(/webPolicy/Sections/interopSection[1]/PolicyItems/item/Version))')
Error report:
SQL Error: ORA-29858: error occurred in the execution of ODCIINDEXALTER routine
ORA-64131: XMLIndex Metadata: failure during the looking up of the dictionary
ORA-30968: invalid XPATH or NAMESPACE option for XML Index
29858. 00000 - "error occurred in the execution of ODCIINDEXALTER routine"
*Cause: Failed to successfully execute the ODCIIndexAlter routine.
*Action: Check to see if the routine has been coded correctly.

Adding a UNIQUE Constraint to an existing table

Hi,
I got this issue because of the existing data. My issue is in my table I want to add a unique constraint to two columns but i cannot add this becuase of the existing repeating data. And I cannot do a data repair to fix the repeating data since the customer is reling on this data so we can not get the decision to repair the data.
As a solution I try this method, by adding a function to check the repeating data before inserting the data to the table. It's working fine to a user but when it come to multiple users it's not working because users can log to the database and can do their transactions simultaneously.
My question is; is there a way in oracle to add a constraint to the data that can add in future not to the old existing data?
Thanks,
Darex.

user9359353 wrote:
Hi,
As a solution I try this method, by adding a function to check the repeating data before inserting the data to the table. It's working fine to a user but when it come to multiple users it's not working because users can log to the database and can do their transactions simultaneously.
show us what is "not working". if you are calling this function from a trigger the correct way, the first person to commit will have their data inserted and the next person will not be able to insert.
edit: you may want to have a read through this thread: where I was encountering a problem with multi-row validation using triggers:
Row level validation dependant on other rows?
note this post:
Rob van Wijk wrote:
Hi WhiteHat,
Here are two blogposts of mine about this subject that you might find useful.
One with some guidelines about implementing entity rules: http://rwijk.blogspot.com/2008/08/implementing-entity->rules.html
And one with an example how to implement (among others) an overlap check in the context of another option for your >question, the product RuleGen: http://rwijk.blogspot.com/2008/05/rulegen-test.html
Hope this helps.
Regards,
Rob.Edited by: WhiteHat on Jun 8, 2011 3:51 PM

HOWTO: Add a UNIQUE constraint to a populated column

Here is the way to add a unique constraint to a populated column, ensuring that the existing values are unique as well.
ALTER TABLE t1
ADD CONSTRAINT t1_uk UNIQUE (col1,col2)
EXCEPTIONS INTO my_exceptions
/If the alter table statement fails this will populate the MY_EXCEPTIONS table with the rows that contain duplicate values for (col1,col2). These are identified by ROWID. We can then chose to:
[list]
[*]delete rows with a bad key;
[*]amend the values of the key columns;
[*]re-apply the constraint with the NOVALIDATE option.
[list]
We should be wary of choosing the NOVALIDATE option. There's usually a good reason why the unique constraint is required and we should not circumvent it. Apart from anything else, Oracle allows us to build foreign keys referencing NOVALIDATE unique keys. This could result in child rows that have two parents, which is normal in biology, but very wrong in a database.
NOVALIDATE is useful in datawarehouses and suchlike, because little updating occurs and the data integrity issues are of less imporatance. I don't think it ought to be used in OLTP situations. The code example at the end of this posting illustrates why we should exercise caution with NOVALIDATE.
Once we have handled the duplicate values we can re-run the alter table statement and apply the constraint.
If you don't already have an EXCEPTIONS table (it can be called anything, it's the structure that counts) you may need to run (or get a DBA to run) a script called UTLEXCPT.SQL, which will be in the $ORACLE_HOME/rdbms/admin directory.
Cheers, APC
SQL> SELECT col1, col2, col3 FROM t1;
      COL1       COL2       COL3
         1          1          0
         2          1          0
         2          1          0
SQL> SELECT col1, col2, cola FROM t2;
      COL1       COL2 COLA
         1          1 I'm child #1
         1          1 I'm child #2
         2          1 I'm child #3
SQL> ALTER TABLE t1
2 ADD CONSTRAINT t1_uk UNIQUE (col1, col2);
ALTER TABLE t1 ADD CONSTRAINT t1_uk UNIQUE (col1, col2)
ERROR at line 1:
ORA-02299: cannot validate (TST2.T1_UK) - duplicate keys found We can't add a unique key, so we decide to use the NOVALIDATE clause.
SQL> CREATE INDEX t1_i ON t1(col1, col2);
Index created.
SQL> ALTER TABLE t1
2 ADD CONSTRAINT t1_uk UNIQUE (col1, col2) ENABLE NOVALIDATE;
Table altered.
SQL> INSERT INTO t1 VALUES (2, 1, 1);
insert into t1 values (2, 1, 1)
ERROR at line 1:
ORA-00001: unique constraint (TST2.T1_UK) violated Well, we can't add any more duplicate keys, so that's alright isn't it? Nope. We can add a foreign key to table T2 referencing T1 but we don't know which row in T1 is the parent of the rows in T2.
SQL> ALTER TABLE t2
2 ADD CONSTRAINT t2_t1_fk foreign key (col1, col2)
3 REFERENCES t1(col1, col2)
Table altered.
SQL> SELECT rowid FROM t1 WHERE col1 = 2;
ROWID
AAAVnMAANAAAB96AAB
AAAVnMAANAAAB96AAC
SQL> DELETE FROM t1 WHERE rowid = 'AAAVnMAANAAAB96AAB';
1 row deleted.
SQL> DELETE FROM t1 WHERE rowid = 'AAAVnMAANAAAB96AAC';
DELETE FROM t1 WHERE rowid = 'AAAVnMAANAAAB96AAC'
ERROR at line 1:
ORA-02292: integrity CONSTRAINT (TST2.T2_T1_FK) violated - child record found
SQL> ROLL
Rollback complete.
SQL> DELETE FROM t1 WHERE rowid = 'AAAVnMAANAAAB96AAC';
1 row deleted.
SQL> DELETE FROM t1 WHERE rowid = 'AAAVnMAANAAAB96AAB';
DELETE FROM t1 WHERE rowid = 'AAAVnMAANAAAB96AAB'
ERROR at line 1:
ORA-02292: integrity CONSTRAINT (TST2.T2_T1_FK) violated - child record found
SQL> ROLL
Rollback complete.
Why this matters: queries joining child and parent tables return more rows than we'd expect normally.
SQL> SELECT t2.cola
2 FROM   t2
3 WHERE t2.col1 = 2
4 and    t2.col2 = 1;
COLA
I'm child #3
SQL> SELECT t2.cola, t1.col4
2 FROM   t1, t2
3 WHERE t2.col1 = 2
4 AND    t2.col2 = 1
5 AND    t1.col1 = 2
6 AND    t2.col2 = 1;
COLA                    COL4
I'm child #3            I'm the daddy
I'm child #3            No, I'm the daddy!!
SQL> Caveat emptor
This posting is issued on behalf of the Rogue Moderators. It is posted with the best of intentions but is not guaranteed in any way, shape or form. In particular, the code is presented "as is" and you assume full responsibility for running it on your system. Furthermore, you must not download and install software from the internet unless you know what you are doing and have the permission of whoever owns your system. It was never this hard for the Lone Ranger.

Hi,
You can not create unique key with duplicate values as you know. Now if you want to create unique key then you have to delete duplicate records from the table but this again if you can afford to delete because this data may be more importante to you and you can not delete any record.
or you can use ENABLE NOVALIDATE option of oracle explain by Tom on below link.
http://asktom.oracle.com/pls/asktom/f?p=100:11:0::::P11_QUESTION_ID:8806498660292
or if you dont want to use Tom's way then you go with primary key like
Drop old primary key if there is already on the column.
create new primary key with enable novalidate option.

Unique Constraint on CLOB XML

From my research it appears you can't put a unique constraint on an xml record if the xml is stored as a CLOB. Could somebody confirm I am correct?
If I'm wrong please provide an example on how do do it on the value attribute for the "key" node in following xml:
<DomainObject className="Building" xmlns="hello world">
<primitive value="1" name="key"/>
<primitive value="111" name="jobId"/>
<primitive value="1.0" name="height"/>
</DomainObject>
Thanks,
Steve

Since nobody responded I wung it. Even in schema based XML I don't think there is a way to put a unique constraint on the column in the way I needed it, so I wrote a BEFORE INSERT trigger which makes sure the key being inserted doesn't duplicate a key already in the table.
Steve

[[11g] many XMLSCHEMA for a given binary XML table

Hi,
--1-----------------------------------
I cannot create a table associated with several xmlschemas.
create table "VALIDATE_XML_SCHEMA" of XMLTYPE
XMLTYPE STORE AS BASICFILE BINARY XML
XMLSCHEMAS (XMLSCHEMA "http://www.binary.com/root.xsd" ELEMENT "ROOT",
XMLSCHEMA "http://www.different.com/root.xsd" ELEMENT "ROOT") DISALLOW NONSCHEMA;
==> ORA 22853
Does this syntax is wrong?
--2----------------------------------
What about add and remove an existing associated xmlschma ?
ALTER table "VALIDATE_XML_SCHEMA"
REMOVE XMLSCHEMAS (XMLSCHEMA "http://www.different.com/root.xsd" ELEMENT "ROOT");
ALTER table "VALIDATE_XML_SCHEMA"
ADD XMLSCHEMAS (XMLSCHEMA "http://www.different.com/root.xsd" ELEMENT "ROOT") DISALLOW NONSCHEMA;
---------------------------------

OK, so here it goes ...
TEST1.xsd
<?xml version = "1.0" encoding = "UTF-8"?>
<xsd:schema xmlns:xsd = "http://www.w3.org/2001/XMLSchema"
      elementFormDefault = "qualified">
<xsd:element name = "TEST1XML">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element ref = "ID"/>
        <xsd:element ref = "Description"/>
      </xsd:sequence>
    </xsd:complexType>
</xsd:element>
<xsd:element name = "ID">
    <xsd:simpleType>
      <xsd:restriction base = "xsd:string">
        <xsd:length value = "4"/>
      </xsd:restriction>
    </xsd:simpleType>
</xsd:element>
<xsd:element name = "Description">
    <xsd:simpleType>
      <xsd:restriction base = "xsd:string">
        <xsd:maxLength value = "35"/>
      </xsd:restriction>
    </xsd:simpleType>
</xsd:element>
</xsd:schema>TEST2.xsd
<?xml version = "1.0" encoding = "UTF-8"?>
<xsd:schema xmlns:xsd = "http://www.w3.org/2001/XMLSchema"
      elementFormDefault = "qualified">
<xsd:element name = "TEST2XML">
    <xsd:complexType>
      <xsd:sequence>
        <xsd:element ref = "ID"/>
        <xsd:element ref = "AccessedOn"/>
      </xsd:sequence>
    </xsd:complexType>
</xsd:element>
<xsd:element name = "ID">
    <xsd:simpleType>
      <xsd:restriction base = "xsd:string">
        <xsd:length value = "4"/>
      </xsd:restriction>
    </xsd:simpleType>
</xsd:element>
<xsd:element name = "AccessedOn" type="xsd:dateTime" />
</xsd:schema>and the offending script
SET TIMING ON;
BEGIN
   DBMS_XMLSCHEMA.REGISTERSCHEMA(
     SCHEMAURL => 'http://localhost/xsd/TEST1.xsd',
     SCHEMADOC => BFILENAME('XML_FILES_DIR','TEST1.xsd'),
     LOCAL     => TRUE,
     GENTYPES => FALSE,
     GENBEAN   => FALSE,
     GENTABLES => FALSE,
     FORCE     => FALSE,
     CSID      => NLS_CHARSET_ID('AL32UTF8'),
     OPTIONS   => DBMS_XMLSCHEMA.REGISTER_BINARYXML);
END;
BEGIN
   DBMS_XMLSCHEMA.REGISTERSCHEMA(
     SCHEMAURL => 'http://localhost/xsd/TEST2.xsd',
     SCHEMADOC => BFILENAME('XML_FILES_DIR','TEST2.xsd'),
     LOCAL     => TRUE,
     GENTYPES => FALSE,
     GENBEAN   => FALSE,
     GENTABLES => FALSE,
     FORCE     => FALSE,
     CSID      => NLS_CHARSET_ID('AL32UTF8'),
     OPTIONS   => DBMS_XMLSCHEMA.REGISTER_BINARYXML);
END;
CREATE TABLE XML_TEST_TBL OF XMLTYPE
   XMLTYPE STORE AS SECUREFILE BINARY XML
   XMLSCHEMAS( XMLSCHEMA "http://localhost/xsd/TEST1.xsd" ELEMENT "TEST1XML",
               XMLSCHEMA "http://localhost/xsd/TEST2.xsd" ELEMENT "TEST2XML")
   DISALLOW NONSCHEMA;
COMMIT;After running the script, I get
PL/SQL procedure successfully completed.
Elapsed: 00:00:00.45
PL/SQL procedure successfully completed.
Elapsed: 00:00:01.47
CREATE TABLE XML_TEST_TBL OF XMLTYPE
   XMLTYPE STORE AS SECUREFILE BINARY XML
   XMLSCHEMAS( XMLSCHEMA "http://localhost/xsd/TEST1.xsd" ELEMENT "TEST1XML",
               XMLSCHEMA "http://localhost/xsd/TEST2.xsd" ELEMENT "TEST2XML")
   DISALLOW NONSCHEMA
Error at line 28
ORA-22853: invalid LOB storage option specificationSo, I am indeed hitting the issue !
And to complement the posts made so far, all the other errors (ALTER TABLE syntax, multiple schemas for OBJECT RELATIONAL storage) mentioned still occur in 11.1.0.7 ....
Maybe Mark can advise on how to proceed with this. I must say though that I am not too happy creating SRs... It might give a bad impression about me AND about the product and that would be unfair on both counts.
Best Regards
Philip

[11g] adding a virtual col to a binary XML table?

Hi
Is it possible to add a virtual col to an existing binay XML table ?
CREATE TABLE compagnie_binaryXML OF XMLType
XMLTYPE STORE AS BINARY XML
VIRTUAL COLUMNS
(vircolcomp AS (EXTRACTVALUE(OBJECT_VALUE,'/compagnie/comp')),
vircolnomcomp AS (EXTRACTVALUE(OBJECT_VALUE,'/compagnie/nomComp')),
vircolnompil AS (EXTRACTVALUE(OBJECT_VALUE,'/compagnie/pilotes/pilote/nom')),
vircolbrevpil AS (EXTRACTVALUE(OBJECT_VALUE,'/compagnie/pilotes/pilote/@brevet')));
OK, but
ALTER TABLE compagnie_binaryXML ADD vircolsalpil AS (EXTRACTVALUE(OBJECT_VALUE,'/compagnie/pilotes/pilote/s
alaire'));
ORA-22856: impossible d'ajouter des colonnes à des tables objet

Hi
IMHO this has nothing to do with XMLType... They simply forget to change the checks performed before adding a column... In fact, this is a "known problem" with object tables.
SQL> create type ttt as object (n number);
2 /
SQL> create table t of ttt;
SQL> alter table t add v as (to_char(n));
alter table t add v as (to_char(n))
ERROR at line 1:
ORA-22856: cannot add columns to object tables
oracle@helicon:~/ [DBA11106] oerr ora 22856
22856, 00000, "cannot add columns to object tables"
// *Cause:   An attempt was made to add columns to an object table. Object
//           tables cannot be altered to add columns since its
//           definition is based on an object type.
// *Action: Create a new type with additional attributes, and use the new
//           type to create an object table. The new object table will have
//           the desired columns.In summary, I would open an SR and let fix the problem.
HTH
Chris

How add primary key constraint to already existing table with data

I want apply primary key constraint to already existing table with data
is there any command or way to do

Alternatively, assuming you want to ensure uniqueness in your primary key column you can do this:
alter table <table name> add constraint <cons name> primary key (col1,col2) exceptions into <exception_table>
If the altter table statement fails this will populate the EXCEPTIONS table with the rows that contain duplicate values for (col1,col2).
You will need to run (or get a DBA to run) a script called UTLEXCPT.SQL (which will be in the $ORACLE_HOME/rdbms/admin directory) if you don't already have an EXCEPTIONS table.
Cheers, APC

Tip: Unique Constraint on Part of Table

Here's a cute little trick I picked up from where it was hiding deep within one of the manuals:
Consider a table where one column needs to be unique, but only part of the time based on some condition within the row. For example, col1 must be unique when its value is above 1000 but any number of rows can have the same value for col1 when it is 999 or less. Another example would be a flag column that determines that col1 must be unique. Don't ask me WHY you would do either of these things.
Here's how to accomplish the first example (btw both examples require a PK on the table):
CREATE TABLE junk(
junk_key INTEGER NOT NULL,
col1 INTEGER NOT NULL,
CONSTRAINT pk_junk PRIMARY KEY(junk_key)
--The way we accomplish this is with a function-based index.
CREATE UNIQUE INDEX idx_semiuniq ON junk(
CASE WHEN col1>=1000 THEN TO_CHAR(col1) ELSE '~' || TO_CHAR(junk_key) END);
--The following statements should succeed:
insert into junk values(1,1);
insert into junk values(2,1);
insert into junk values(3,1000);
insert into junk values(4,1001);
update junk set col1=1002 where junk_key=4;
--The following statements should fail:
insert into junk values(5,1000);
update junk set col1 = 1001 where junk_key=1;
The same strategy applies to the second example, except that in this case we'll need an additional column to indicate that col1 needs to be unique:
CREATE TABLE junk( junk_key INTEGER NOT NULL,
col1 INTEGER NOT NULL,
uniq_flag CHAR(1) NOT NULL,
CONSTRAINT pk_junk PRIMARY KEY(junk_key),
CONSTRAINT ck_junk CHECK (uniq_flag IN ('Y','N'))
CREATE UNIQUE INDEX idx_semiuniq ON junk(CASE WHEN uniq_flag = 'Y' THEN TO_CHAR(col1) ELSE '~' || TO_CHAR(junk_key) END);
--these should succeed:
insert into junk values(1,1,'N');
insert into junk values(2,1,'N');
insert into junk values(3,1,'Y');
insert into junk values(4,2,'Y');
--these should fail:
insert into junk values(5,2,'Y');
update junk set uniq_flag='Y' where junk_key=2;
Another way to accomplish this is with a "not exists" in a check constraint, but I think the function-based index will perform better especially when inserting or updating large numbers of rows.

You could try something like
(extract(OBJECT_VALUE,compagnie/pilotes/pilote/brevet').getStringVal());
but this is probably unadvisable.
I suggest an alternative is for you to look at XMLINDEX so that you can bring the 'proper' XML functions into play like XMLTABLE etc.

Unique constraint control in data table

I developped a form where the user can enter or modify a list of profiles.
Each profile has a code (entered by the user).
I need to control that the profile code is unique.
What are the recomendations?
Should I do that control in the validation method, in the action method, or should I let this control to the database and manage an excpetion (but how...) ?
Do you have an example of such controls?

Thanks for your answer.
Actually, this is what I'm trying to do, but it's not so obvious:
1 - I need to control the unicity of the code in the list. So, I need to have all the new values before validating. The "Validator" attribute doesn't apply to the datatable.
2 - I want to verify the codes with other rows in the DB (which can be hidden on this screen). So, should I access to the DB from the managed bean just to verify?
I don't know if it's possible, but what I'd like is to try to do the insert, then the DB will send back an exception, but then, I don't know how to manage this exception. Because if I try to insert, I'm at the end of the lifecycle. I'm not any longer in the validation phase.

Indices and constraints on XML Tables/Columns (with Schema)

Hi,
I've read a lot of documents by know, but the more I read the more I got confused. So I hope you can help me.
Frist my Oracle Server Version: Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit
I've manages to create a table with a column with the type SYS.XMLTYPE and the storage modle "Object Relational" with an XML Schema.
I can insert data and I can execute XQuery statements.
I can also create an XMLTYPE table with my Schema, althoug the tool SQL Developer keeps telling me, that the one column wich is generated within the table is of the type CLOB instead of object realtional (which is what I defined).
The query for that is:
CREATE TABLE ENTRY_XML OF XMLTYPE
XMLTYPE STORE AS OBJECT RELATIONAL
XMLSCHEMA "BBMRI_Entry.xsd" ELEMENT "Entry";
That's where I am, now my questions:
1. What's the difference? I'm aware of the obviouse difference, that with the first way I can add relational columns as well, but apart from that? If I only want to store the xml data, is the second approach always better (especially in regard to my next question)?
2. My schema contains elements with attributes (which contain IDs), which have to be unique. So I tried to add a UNIQUE constraint, but failed. I found this (http://www.oracle.com/technology/sample_code/tech/java/codesnippet/xmldb/constraints/Specify_Constraints.html), but it just doesn't work.
Query: "ALTER TABLE ENTRY_XML CONSTRAINT ENTRY_XML_SUBID_UNQIUE UNIQUE (xmldata."SubId");"
Error: "ORA-01735: invalid ALTER TABLE option"
3. I didn't try yet, but I need to specifiy foreign keys within the XML as well (which is explained in the link at question 2). I guess the solution to question 2 will make this possible as well.
4. Since I can create a UNIQUE constaint for attributes (well, I can't yet, but I hope that this will change soon) I woundered if it would be possible to realize something like auto_increment. Although I see the problem with validating the xml input if the Ids are empty. Any suggestions on that problem? Do I have to query for the highest (free) id before I can insert the new documents?
Well, that's enough for today, I hope someone can help me!
Greetings, Florian

I've read through all the literature (again) and found out, that I did most of the stuff right in the first place. I just missinterpreted the generated tables for the types and wondered why they only contained one column. Well, at least one mistery solved.
But know to make it easier just one question, which might solve all problems I have:
How can I create UNIQUE constraints and FOREIGN KEYS when I have a table or column of the type XmlType with a schema using the object relational storage method?
I found a solution http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14259/xdb05sto.htm#i1042421 (Example 5-12), but it just does not work for me.
I removed the FOREIGN KEY and tried it again and the UNIQUE Key works.
So basically the question is how to retrieve the "AId" Attribute. "XMLDATA"."AId", "XMLDATA"."Attribute"."AId" and "XMLDATA"."Subject"."Attribute"."AId" all do not work.
I've added my schema declarations at the bottom (which I've already successfully registred and used without foreign keys and constraints, so they work).
After I've registered the two schema files 3 types and 11 tables where created. One type for the attribute, one for the study type and one probably to link the attributes to the study types. The tables are one for the attribute, 4 for the content*-elements, 2 for the study type (I don't really know why two) and 4 with strange names starting with "SYS_NT" and then some random numbers and letters (looks alot like some base64 encoded string).
The Query I try to use to create the table is: (The table "Attribute" already exists and contains a field "ID", which is it's PK.)
CREATE TABLE STUDYTYPE_XML
OF XMLType (UNIQUE ("XMLDATA"."STId"),
FOREIGN KEY ("XMLDATA"."AId") REFERENCES ATTRIBUTE(ID))
XMLTYPE STORE AS OBJECT RELATIONAL
ELEMENT "StudyType.xsd#StudyType";
The error I get is:
Error starting at line 1 in command:
CREATE TABLE STUDYTYPE_XML
OF XMLType (UNIQUE ("XMLDATA"."STId"),
FOREIGN KEY ("XMLDATA"."AId") REFERENCES ATTRIBUTE(ID))
ELEMENT "StudyType.xsd#StudyType"
Error at Command Line:3 Column:37
Error report:
SQL Error: ORA-22809: nonexistent attribute
22809. 00000 - "nonexistent attribute"
Cause: An attempt was made to access a non-existent attribute of an
object type.
Action: Check the attribute reference to see if it is valid. Then retry
the operation.
Attribute-Schema (Attribute.xsd):
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:attribute name="AId">
          <xs:simpleType>
               <xs:restriction base="xs:integer">
                    <xs:minInclusive value="0" />
               </xs:restriction>
          </xs:simpleType>
     </xs:attribute>
     <xs:attribute name="Name" type="xs:string" />
     <xs:element name="ContentString" type="xs:string" />
     <xs:element name="ContentInteger" type="xs:integer" />
     <xs:element name="ContentDouble" type="xs:decimal" />
     <xs:element name="ContentDate" type="xs:date" />
     <xs:element name="Attribute">
          <xs:complexType>
               <xs:choice minOccurs="0" maxOccurs="1">
                    <xs:element ref="ContentString" />
                    <xs:element ref="ContentInteger" />
                    <xs:element ref="ContentDouble" />
                    <xs:element ref="ContentDate" />
               </xs:choice>
               <xs:attribute ref="AId" use="required" />
               <xs:attribute ref="Name" use="optional" />
          </xs:complexType>
     </xs:element>
</xs:schema>
Study Type Schema (StudyType.xsd):
<xs:schema xmlns:xs="http://www.w3.org/2001/XMLSchema" elementFormDefault="qualified" attributeFormDefault="unqualified">
     <xs:include schemaLocation="Attribute.xsd" />
     <xs:attribute name="STId">
          <xs:simpleType>
               <xs:restriction base="xs:integer">
                    <xs:minInclusive value="0" />
               </xs:restriction>
          </xs:simpleType>
     </xs:attribute>
     <xs:element name="StudyType">
          <xs:complexType>
               <xs:sequence>
                    <xs:element ref="Attribute" minOccurs="1" maxOccurs="unbounded" />
                    <xs:element ref="StudyType" minOccurs="0" maxOccurs="unbounded" />
               </xs:sequence>
               <xs:attribute ref="STId" use="required"/>
          </xs:complexType>
     </xs:element>
</xs:schema>
Edited by: alwaysspam on Sep 8, 2010 5:35 PM

Insert called before delete in a collection with unique constraint

Hi all,
I have a simple @OneToMany private mapping:
private Collection<Item> items;
@OneToMany(mappedBy = "parent", cascade = CascadeType.ALL)
public Collection<Item> getItems() {
return items;
public void setItems(Collection<Item> items) {
this.items = items;
public void customize(ClassDescriptor classDescriptor) throws Exception {
OneToManyMapping mapping = (OneToManyMapping)
classDescriptor.getMappingForAttributeName("items");
mapping.privateOwnedRelationship();
I have a unique constraint on my Items table that a certain value cannot be duplicated.
My problem appears when I remove a previously saved item from the collection and add a new item containing the same data, at the same time.
After I save the parent and do a flush, I receive SQLIntegrityConstraintViolationException because TopLink performs first an insert query instead of deleting the existing item.
I tested the application and everything went fine with: remove item / save parent / insert item / save parent
I checked on the Internet and the documentation but didn't find anything similar to my problem. I tried debugging TopLink's internal calls but I'm missing some general ideas about all the inner workings and don't know what to look for. I use TopLink version: Oracle TopLink Essentials - 2.1 (Build b60e-fcs (12/23/2008))
Does anyone have a hint of what to look for?
Edited by: wise_guybg on Sep 25, 2009 4:01 PM
Edited by: wise_guybg on Oct 5, 2009 11:22 AM

Thank you for the suggestions James
As I mentioned briefly I have done some debugging but couldn't understand how collections are updated. What I did find out is that setShouldPerformDeletesFirst() doesn't come into play in this case because this is not a consecutive change on entities.
What I have in my case is a collection inside an entity that the user has tampered with and now TopLink has to do a merge. I cannot call flush() in the middle since the user has not approved that the changes made to the entity should be saved.
I see that for TopLink it's not easy to figure out the order in which changes were made to a collection. Here is pseudo-code of when the constraint is touched:
entity.items.remove(a)
entity.items.add(b)
merge(entity)
And here is code that executes without a problem:
entity.items.remove(a)
merge(entity)
entity.items.add(b)
merge(entity)
So once again, I think that collection changes are managed differently but I don't find a way to tell TopLink how to handle them. Any ideas?

Add a unique constraint on binary XML table

Similar Messages

Maybe you are looking for