disable the constraint

Similar Questions

• in what scenario we set the constraint to DISABLE VALIDATE?

  I know there are four State constraint and their combination, thus, we can use.
  >
  -ENABLE ensure that all incoming data meets the constraint
  -DISABLE allow incoming data, regardless of whether it conforms to the constraint
  -VALIDATE to ensure that existing data constraint
  -Existing data NOVALIDATE need not conform to the constraint
  >
  I know also that when we disable validate, we are not able to make any changes to the corresponding columns.
  But what I would like to know what type of scenario, we would need set the constraint to DISABLE VALIDATE?
  
  Any input would be much appreciated.
  Thank you

  Good question I don't also know the answer then tried to find documentation.

  I assume you are using 10g so linking doc 10g:
  http://download.Oracle.com/docs/CD/B19306_01/server.102/b14200/clauses002.htm#i1002349

  VALIDATE DISABLE them disables the constraint and removes the index on the constraint, but retains the valid constraint. This feature is very useful in some situations, data warehouses, because it allows you to load large amounts of data all also saves space by not having not a clue. This setting allows you to load data into a table that is not partitioned in a partitioned table by using the exchange_partition_clause of the statement ALTER TABLE or SQL * Loader. All other changes (inserts, updates, and deletions) table by other SQL statements are not allowed.

• Disable the unique key constraint

  Hello
  
  Is it possible to disable a unique key constraint?
  I tried the following code:
  
  ALTER TABLE table_name
  DISABLE the CONSTRAINT uk_constraint_name
  
  that seems to work fine, but when I try to insert or update a record that the unique constraint is still on. However, Toad in the United Kingdom is marked as disabled.
  
  What do I need to drop the UK and re-create it after my updates?
  
  Thank you

  The behavior that I have demonstrated that during
  a. you have an existing UNIQUE Index
  b. you add a Unique key constraint (with the same or another name, any - except that the error message contains the name of the index is different, if the constraint is disabled)

  OTOH, if you set the Unique key on the table without pre-existing index constraint, Oracle creates an Index. If you disable this constraint, Oracle removes the Index.
  So, if it is a small table and you can afford to recreate the Index each time, you can follow this method.

  SQL> create table t_2 (col_1 number, col_2 varchar2(5));
  
  Table created.
  
  SQL> alter table t_2 add constraint t_2_uk unique (col_1);
  
  Table altered.
  
  SQL> select index_name, uniqueness, status from user_indexes where table_name = 'T_2';
  
  INDEX_NAME                     UNIQUENES STATUS
  ------------------------------ --------- --------
  T_2_UK                         UNIQUE    VALID
  
  SQL> insert into t_2 values (1,'a');
  
  1 row created.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> alter table t_2 disable constraint t_2_uk;
  
  Table altered.
  
  SQL> insert into t_2 values (1,'b');
  
  1 row created.
  
  SQL> select index_name, uniqueness, status from user_indexes where table_name = 'T_2';
  
  no rows selected
  
  SQL>SQL> select constraint_name, constraint_type, status from user_constraints where table_name = 'T_2';
  
  CONSTRAINT_NAME                C STATUS
  ------------------------------ - --------
  T_2_UK                         U DISABLED
  
  SQL> alter table t_2 enable constraint t_2_uk;
  alter table t_2 enable constraint t_2_uk
  *
  ERROR at line 1:
  ORA-02299: cannot validate (AWRADMIN.T_2_UK) - duplicate keys found
  
  SQL> delete t_2 where col_2 = 'b';
  
  1 row deleted.
  
  SQL> alter table t_2 enable constraint t_2_uk;
  
  Table altered.
  
  SQL> select index_name, uniqueness, status from user_indexes where table_name = 'T_2';
  
  INDEX_NAME                     UNIQUENES STATUS
  ------------------------------ --------- --------
  T_2_UK                         UNIQUE    VALID
  
  SQL>
  

  Hemant K Collette

• I can't disable a constraint in SQL Developer

  Here's my question:
  I created a table named pratique1 already.
  Developer SQL PL/SQL using try to run a loop as follows:
  DECLARE
  COUNTER1 NUMBER (2);
  BEGIN
  COUNTER1: = 30;
  ALTER TABLE pratique1
  DISABLE THE CONSTRAINT PRK1;
  LOOP
  COUNTER1: = 30;
  INSERT INTO PRATIQUE1
  VALUES (COUNTER1, 'test7', 8, 9);
  WHEN the OUTPUT COUNTER1 > 26;
  END LOOP;
  END;
  In other words, I insert the value of the variable COUNTER1 as primary key in the field1 column tables.
  I run the script successfully without the ALTER TABLE CONTSRAINT... DISABLE command.
  Whenever I run that I had to increase the starting value of the Variable COUNTER1, so he will not attempt to insert a value pre existed twice in the primary key.
  So I decided to insert the command ALTER TABLE DISABLE CONSTRAINT to do not have to worry about changing the starting value.
  I am able to disable the constraint by using the same command in a vacuum. If I run it through the script as shown above, I get the following error:
  Error report:
  ORA-06550: line 5, column 1:
  PLS-00103: encountered the symbol "ALTER" when expecting one of the following conditions:
  (begin case declare exit end exception for goto if loop mod)
  pragma raise return null select update while with
  < an ID > < a between double quote delimited identifiers of >
  < a variable binding > < < continue close check out lock remove current
  Insert restore open savepoint sql execute commit forall
  purge pipes of fusion
  06550 00000 - "line %s, column % s:\n%s".
  * Cause: Usually a PL/SQL compilation error.
  * Action:
  I would like suggestions.
  Thank you.

  Your question has NOTHING to do with the sql developer.

  Mark this question ANSWER and repost it in SQL and PL/SQL forum.

  https://forums.Oracle.com/community/Developer/English/oracle_database/sql_and_pl_sql

  The problem is that you cannot run the DDL directly in PL/SQL. You must use dynamic SQL statements to execute DDL in PL/SQL.

  RUN IMMEDIATELY ' ALTER TABLE... » ;

  If you need help using the correct, as forum indicated above.

• forced to deleted still apply the constraint

  I have a two-column table that has a couple of constraints which is to keep the pair of these two unique columns. When I insert the first record (the table is empty), I get the constraint violation. I wouldn't have this error. Disabling the constraint does not help so I remove the constraint. Now I can insert that record, but when I try to insert the same record, I this violation with the name of the deleted constraint.
  
  Here is the result: (the deleted constraint is EQ_FOR_QUOTE_HAZ_HAZMAT_RFQ)
  

  SQL> delete from req_for_quote_haz;
  
  1 row deleted.
  
  SQL> commit;
  
  Commit complete.
  
  SQL>  select constraint_name from all_constraints where table_name='REQ_FOR_QUOTE_HAZ';
  
  CONSTRAINT_NAME
  
  ------------------------------
  
  REQ_FOR_QUOTE_HAZ_HAZMAT_ID_FK
  
  
  
  SQL>  insert into REQ_FOR_QUOTE_HAZ values (1815,1);
  
  1 row created.
  
  
  
  SQL>  insert into REQ_FOR_QUOTE_HAZ values (1815,1);
  
   insert into REQ_FOR_QUOTE_HAZ values (1815,1)
  
  *
  
  ERROR at line 1:
  
  ORA-00001: unique constraint (ITS.REQ_FOR_QUOTE_HAZ_HAZMAT_RFQ) violated
  
  
  
  SQL> 

  Any ideas?
  
  Thank you
  View

  Perhaps you have a unique index on the columns. If not can you confirm that you are looking in HIS scheme.

• Drop partition without disabling the foreign key

  Hi all
  
  I have a table parent and child.
  
  Parent table
  
  create the table parent_1
  (identification number,
  create_date date,
  Constraint parent_1_pk001 PRIMARY KEY (id))
  PARTITION OF RANGE (create_date)
  INTERVAL (NUMTODSINTERVAL(1,'DAY'))
  (PARTITION parent_1_part VALUES LESS THAN (January 1, 2010 '));
  
  Child table
  create the table child_1
  (identification number,
  create_date date,
  Constraint child_1_fk001 FOREIGN KEY (id)
  REFERENCES parent_1 (id))
  PARTITION OF RANGE (create_date)
  INTERVAL (NUMTODSINTERVAL(1,'DAY'))
  (PARTITION create_date_part VALUES LESS THAN (January 1, 2010 '));
  
  
  I have problems to delete partition.
  Parent_1
  1 JULY 26, 12
  2 JULY 26, 12
  
  Child_1
  1 JULY 26, 12
  
  ALTER drop partition table CHILD_1 SYS_P274;
  table altered CHILD_1.
  
  ON THE PARENT PARTITION A FALL
  ALTER drop partition table parent_1 SYS_P273;
  
  Error report:
  SQL error: ORA-02266: unique/primary keys in table referenced by foreign keys enabled
  02266 00000 - "unique/primary keys in table referenced by foreign keys enabled.
  * Cause: An attempt was made to truncate a single table or
  primary keys referenced by foreign keys in another table.
  Other unauthorized trades are a drop/truncate partition a
  partitioned table or an ALTER TABLE EXCHANGE PARTITION.
  * Action: Before performing the operations described above, the table, disable the
  constraints foreign key in other tables. You can see what
  constraints are making reference to a table by issuing the following
  command:
  SELECT * FROM USER_CONSTRAINTS WHERE TABLE_NAME = 'tabnam ';
  
  
  PLEASE KNOW IF THERE IS A WAY TO THE PARENT PARTITION DROP WITHOUT TOGGLE FOREIGN CONSTRAINTS
  
  
  Thank you

  SQL Error: ORA-02266: unique/primary keys in table referenced by enabled foreign keys
  02266. 00000 - "unique/primary keys in table referenced by enabled foreign keys"
  *Cause: An attempt was made to truncate a table with unique or
  primary keys referenced by foreign keys enabled in another table.
  Other operations not allowed are dropping/truncating a partition of a
  partitioned table or an ALTER TABLE EXCHANGE PARTITION.
  *Action: Before performing the above operations the table, disable the
  foreign key constraints in other tables. 
  

  You can do until you disable the foreign key constraint

  http://jonathanlewis.WordPress.com/2006/12/10/drop-parent-partition/

  Hope this helps

  Mohamed Houri
  www.hourim.WordPress.com

• by specifying the index tablespace in to disable the primary key constraint

  Hello
  during the ETL I want to disable constraints PK/UK to speed up the load;
  on activation of the constraint, the corresponding indices are created in a different tablespace while they were initially on the creation of the table itself
  I tried to disable PK / UK with the option 'keep the index', the index value corresponding to the status of "unusable" and use ' alter session set skip_unusable_indexes = true', but then I can't insert rows with the error.

  Error: ORA-01502: index 'xxx' or partition of such index is in unusable state

  can anyone tell if there is a way to allow the PK/UK constraint and specify the storage space for the corresponding indices, or keep the index and inserts works?
  I'd like to avoid to drop constraints / indexes and re-create them both from scratch after the load
  Thank you for the advice
  Thank you
  Rgds

  >
  can anyone tell if there is a way to allow the PK/UK constraint and specify the storage space for the corresponding indices, or keep the index and inserts works?
  I'd like to avoid to drop constraints / indexes and re-create them both from scratch after the load
  >
  Have you tried specifying the table space in the USING clause when you activate the constraint?

  ALTER TABLE emp ENABLE PRIMARY KEY USING INDEX TABLESPACE myTS;
  

  See DBA guide
  http://docs.Oracle.com/CD/B28359_01/server.111/b28310/indexes003.htm
  >
  Creating an Index associated with a constraint

  Oracle database applies a UNIQUE key or a constraint integrity PRIMARY KEY on a table by creating a unique index on the unique key or primary key. This index is created automatically by the database when the constraint is enabled. No action is required by you when you run the CREATE TABLE or ALTER TABLE statement to create the index, but you can optionally specify an ESCALATION using clause to exercise control over his creation. This includes them when a constraint is defined and enabled, and when a constraint defined but disabled is selected.
  >
  Note the last sentence two sentences:
  >
  You can optionally specify an ESCALATION using clause to exercise control over his creation. This includes them when a constraint is defined and enabled, and when a constraint defined but disabled is selected.
  >
  You realize, I hope, that the only way can Oracle KNOWS that the index contains valid values is to rebuild?

• What is the order to turn off the constraints and index

  Hi, I need to make some out of constraints and indexes on tables to load quite a date in them. I know that I can just drop them and recreate later. But is it feasible to figure who forced and in what order must be do disable or unusable before a load and after the load that is to say. without dropping to preserve? R before P data loading, and then P before R like I think that controls can jump in evertytime and are quite safe to deal with. But I did not carefully think about more, maybe you have some scripts that say exactly what should be the order to turn off the coast and later on this subject.

  Thank you!

  Hello

  946279 wrote:

  Hi, I need to make some out of constraints and indexes on tables to load quite a date in them. I know that I can just drop them and recreate later. But is it feasible to figure who forced and in what order must be do disable or unusable before a load and after the load that is to say. without dropping to preserve? R before P data loading, and then P before R like I think that controls can jump in evertytime and are quite safe to deal with. But I did not carefully think about more, maybe you have some scripts that say exactly what should be the order to turn off the coast and later on this subject.

  Thank you!

  That's right: disable foreign key constraints before disabling the primary (or Unique) key constraint correspondent.  When you reactivate them, re - enable the constraint of primary (or Unique) key before the corresponding foreign key constraints.

  Aside from that, the order should not issue.

• How to disable the index to the rows of the table updated

  Hello world

  I have a problem on a table with Oracle11g.

  I would update a table a lines opposite two in a table. This table has an index, and during the inversion, the index is duplicated.

  So, I turn off the index and then rebuild all indexes like this: How to disable the index in oracle

  However, I can't update a table when my index finger is rolled unusable.

  I create my table:

  CREATE  TABLE MY_TABLE(
    ID                         NUMBER(5) NOT NULL,
    TYPE                        NUMBER(1) NOT NULL,
    PRIO                       NUMBER(4) NOT NULL,
    CONSTRAINT PK_MY_TABLE
      PRIMARY KEY (ID, TYPE )
  );
  
  CREATE INDEX  PRIO_UK
      ON MY_TABLE(TYPE, PRIO);
  
  
  
  

  Then I selected all the elements and the results is:

  ID	Type	Prio
  1	1	10
  2	1	11

  Then, I tried to update this list with this script:

  UPDATE MY_TABLE set PRIO = 11 WHERE ID = 1 AND TYPE = 1;
  UPDATE MY_TABLE set PRIO = 10 WHERE ID = 2 AND TYPE = 1;
  
  
  
  

  I have an error on the first line, because the subscript for type 1 and 11 priority already exist.

  You have another solution to solve my problem?

  I thank you very much.

  Do not disable your index. Just perform your update with a single blow. Like this

  SQL> select *
    2    from my_table;
  
          ID       TYPE       PRIO
  ---------- ---------- ----------
           1          1         10
           2          1         11
  
  SQL> update my_table
    2     set prio = case when id = 1 and type = 1 then 11
    3                     when id = 2 and type = 1 then 10
    4                end
    5   where (id = 1 and type = 1)
    6      or (id = 2 and type = 1);
  
  2 rows updated.
  
  SQL> select *
    2    from my_table;
  
          ID       TYPE       PRIO
  ---------- ---------- ----------
           1          1         11
           2          1         10
  
  SQL>
  

• Disable all constraints

  My table has many constraints, but I want to load data into this table, so I have to disable constraints, so do we have a SINGLE command to disable all constraints, instead of one by one?
  
  Thank you

  No there is no universal constraint inability. What you can do, it's a loop around the data dictionary view and use dynamic SQL statements:

  begin
       for all_cons in ( select table_name, constraint_name from user_constraints
                            where constraint_type in ('U', 'P', 'R') )
       loop
            execute immediate 'alter table '||all_cons||' disable constraint '||all_cons.constraint_name;
      end loop;
  end;
  

  Note that this fact that relational constraints. Remove the filter on CONSTRAINT_TYPE if you want to include check constraints as well.

  Update

  I agree with Sybrand warnings. You will need to make sure you are the only user of the database when you perform this loading.

  Cheers, APC

  Published by: APC on 28 March 2013 13:59

• Unable to activate the constraints!

  Hello
  We have in our user triggers, resulting in that we are not able to activate the constraints, once the import is done, therefore all we must ask our team of dba to disable triggers to activate the constraints, without disabling the triggers can we use NOVALIDATE command to ALTER enable constraint command?, will it have an impact?

  This looks like a duplicate of your other thread: must have updated sql!

• Priority of the constraints &amp; keys

  Hello
  
  
  10.2.0.1.0 Oracle
  
  I have the table containing the primary key and check constraints. Now I am entering data in the table (say from a procedure). When I try to handle exceptions as constraint of unuique etc. What is the priority of exceptions that arise and how they are handled and how should I organize my exception block.
  
  
  

  CREATE TABLE tab11(a NUMBER PRIMARY KEY , b NUMBER CHECK (b!=0))
  DESC tab11
  INSERT INTO tab11 VALUES(1,0) --check constraint voilated
  INSERT INTO tab11 VALUES(NULL,0) --can't insert null
  INSERT INTO tab11(b,a) VALUES(0,NULL) --can't insert null
  CREATE TABLE tab12(a NUMBER CHECK (a!=0),b NUMBER PRIMARY KEY)
  INSERT INTO tab12 VALUES(0,NULL) --can't insert null

  Help, please.
  
  Published by: 804282 on January 19, 2011 06:07
  
  Published by: 804282 on January 19, 2011 06:11

  Ideally Oracle would be forced to validation in an order which is a growing scope of data covered by constraints. It is:
  -Dealing with a CHECK constraint involving a single column first.
  -Deal with the constraints of the AUDIT covering more than one column after
  -Treat with primary/unique keys after that.
  -Treat foreign keys after that.

  Let's do a little test:

  create table emp
  (empno     number not null
  ,ename     varchar2(10) not null
  ,job       varchar2(10) not null
  ,sal       number not null
  ,mgr       number
  ,constraint c_ename check(ename = upper(ename))
  ,constraint c_job_sal check(job != 'CLERK' or sal < 5000)
  ,constraint c_emp_pk primary key(empno)
  ,constraint c_emp_emp_fk foreign key(mgr) references emp(empno)
  );
  
  insert into emp values(1,'TOON','MANAGER',10000,null);
  commit;
  

  So now, we have a table emp with four constraints (one for each class above) and a line.
  Let's try and insert a row that violates all four constraints.

  SQL> insert into emp values(1,'Tom','CLERK',7000,42);
  insert into emp values(1,'Tom','CLERK',7000,42)
  *
  ERROR at line 1:
  ORA-02290: check constraint (TOON.C_JOB_SAL) violated
  

  Hmm. apparently the logical order described above is not what is happening behind the scenes when dealing with a CHECK constraint. Personally, I suspect that they are posted in the order that some internal (recursive) queries on the data dictionary returns them.

  Now let's disable this constraint and raise the insert.

  SQL> alter table emp disable constraint c_job_sal;
  
  Table altered.
  
  SQL> insert into emp values(1,'Tom','CLERK',7000,42);
  insert into emp values(1,'Tom','CLERK',7000,42)
  *
  ERROR at line 1:
  ORA-02290: check constraint (TOON.C_ENAME) violated
  

  It was the another CHECK constraint. We will disable this one too and try again.

  SQL> alter table emp disable constraint c_ename;
  
  Table altered.
  
  SQL> insert into emp values(1,'Tom','CLERK',7000,42);
  insert into emp values(1,'Tom','CLERK',7000,42)
  *
  ERROR at line 1:
  ORA-00001: unique constraint (TOON.C_EMP_PK) violated
  

  Okay, all right. Primary/unique keys are probably always validated before moving on to foreign keys.
  Disable the key obviously fails in this case...

  SQL> alter table emp disable constraint c_emp_pk;
  alter table emp disable constraint c_emp_pk
  *
  ERROR at line 1:
  ORA-02297: cannot disable constraint (TOON.C_EMP_PK) - dependencies exist
  

  So, let's fix the violation of primary key:

  SQL> insert into emp values(2,'Tom','CLERK',7000,42)
    2  /
  insert into emp values(2,'Tom','CLERK',7000,42)
  *
  ERROR at line 1:
  ORA-02291: integrity constraint (TOON.C_EMP_EMP_FK) violated - parent key not found
  

  Disable the fk, finally will allow us to make the insertion.

  SQL> alter table emp disable constraint c_emp_emp_fk;
  
  Table altered.
  
  SQL> insert into emp values(2,'Tom','CLERK',7000,42);
  
  1 row created.
  

  So in summary, I would go the next order being wired into the kernel:
  -CHECK the constraints are first validated (in some order).
  -Primary and unique keys are validated after that.
  -Foreign keys are validated at the last.

  It is of course not at all conclusive research. It is just a bit of fun at the end of a day filled.

  Oh, and of course that postponed any changes whenever certain constraints are declared as may be delayed initially...

  :-)

• How temporary disable the security for the ADF?

  Hi, OTN,.
  I have developed security policies in my ADF application. Now I want to disable temporary for development to accelerate.
  Development guide suggests only pass authentication ADF - I still need to enter my credentials each redeployment - or safely remove - I should not really remove all my development security.
  
  Is there a way to disable temporary real?
  
  Thank you.
  11.1.1.3 JDev

  Security is controlled by two attributes (authorizationEnforce and authenticationRequire) in the ADF - config.Xml. look at this tag in adf - config.xml:

  Set the false values and allows you to disable the authentication and authorization. Note that if you disable authentication you may still have problems with authentication due to security constraints defined in the web.xml file.

  A more standard approach is to keep security settings intact, but to use the role of ADF fail-safe "test-all." Configure the security of the ADF to use test-all role and grant it to all objects. This way developers will have access to all objects secured without giving any privileges explicitly.

  Dimitar

• Problem on the constraints and validation

  Hello
  I want to add a new unique constraint in a table. But the current data do not match the coercion.
  My constraint is like this:
  
  ALTER TABLE T_STUDENT ADD
  CONSTRAINT UNIQ_STUDENT
  UNIQUE (STUDENT_NUMBER, NAME, FIRST NAME)
  DISABLE
  VALIDATE;
  
  I want to add the constraint, and I don't want to update the data. So, how can I add constraint without validating the current data?

  user4030266 wrote:
  Hello

  Hello

  I want to add a new unique constraint in a table. But the current data do not match the coercion.
  I want to add the constraint, and I don't want to update the data. So, how can I add constraint without validating the current data?

  Try like this:

  ALTER TABLE t_student ADD
   CONSTRAINT uniq_student
    UNIQUE (student_number, NAME, surname)
  DEFERRABLE INITIALLY DEFERRED
    NOVALIDATE;
  

  +
  It might be interesting for you
  http://www.Oracle.com/technology/oramag/Oracle/03-Nov/o63asktom.html

• How to defer the constraint to a diagram to another diagram

  Hi all
  
  I have a requirement of data migration of a schema (SCHEMA_A) to another schema (SCHEMA_B). So I tried to implement the same using PL/SQL.
  
  Because of the foreign key constraint all in child table, Oracle migration throws an error message as parent key is not available.
  
  So I tried to set constraints all deferred benefits, and after the completion of the migration, I had planned to affect immediate constraints.
  
  But here I am running schema procedure (SCHEMA_C) that has access rights to the SCHEMA_A and SCHEMA_B.
  
  How could I defer the constraint in SCHEMA_B of SCHEMA_C?
  
  Thanks in advance,
  BSP.

  Try
  the link

  http://code.techinterviews.com/Oracle-disable-all-constraints-referencing-the-table/109