blocking because of the primary key constraint

Similar Questions

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

• Order columns (which make up the primary key constraint) matter in where clause of DML query for use of indexing mechanism to operate.

  Version of DB: database Oracle 11 g Enterprise Edition Release 11.2.0.3.0 - 64 bit Production

  
  I have a table my_table as below:
  create table my_table
  (
  my_code varchar2 (6).
  my_id varchar2 (24).
  forced pk_1 primary key (my_code, my_id)
  );

  
  Primary_key here's a composite key that contains columns 1 (my_code) and 2 (my_id).
  Is there that a difference in the way below queries is executed in terms of performance (use of indexing in the extraction).

  (a) select * from my_table where my_code = '123' and my_id = "456";
  (b) select * from my_table where my_id = '456' and my_code = '123';

  
  The understanding I have the order of the column in the where clause should be identical to the sequence in
  What primary key draws for indexing to be used by oracle in oracle other DML queries ignores indexing
  However when I used explain plain both show the same query cost with single scan with index rowid.
  so I don't know if I'm wrong in the concept that I have. Kindly help.

  Thanks in advance,
  Gerard

  Your question is answered in the Performance Tuning Guide

  Using indexes and clusters

  14.1.4 choosing composite indexes

  A composite index contains several key columns. Composite indexes can provide additional benefits compared to the index to single column:

  • Improved selectivity

    Sometimes the two or more columns or expressions, each with a low selectivity can be combined to form a composite with a high selectivity.

  • Reduced IO

    If all columns selected by a query are a composite index, then Oracle may return these values in the index without access to the table.

  A SQL statement can use a path on a composite index if the statement contains constructions that use a main part of the index.

  Note:

  This is no longer the case with the skip index scans. See "Index Skip Scans".

  A main part of an index is a set of one or more columns that have been specified first and consecutively in the list of columns in the CREATE INDEX statement that created the index.

• creating a unique index of instaed of using the primary key index

  Hello
  
  I heard in a debate sometimes it is better to create a unique index on a column and use it instead of using the primary key index in oracle. I did not understand what that the reason propely.
  
  Can someone please help me in this topic if it is valid.
  
  Thanks in advance

  On the surface, which does not seem reasonable... Volume of the DML is irrelevent to determine which column is the primary key for a table.

  My wild speculation a bit at a reasonable time could someone do...

  If you use synthetic primary keys (i.e. the keys generated by sequence) and that your tables are subject to large volumes of inserts such as there is a danger that the block "to the right" will be the source of contention block and worry not about analysis of beach on the column, you can create a reverse on this column (unique or non-unique) key index before creating the primary key constraint and to indicate Oracle to use this existing index to respect the primary key constraint.

  Obviously, however, this involves a lot of assumptions to arrive at a reasonable point. There may well be another set of assumptions that could also lead to a valid argument. Or it could be a myth that someone has heard and just repeats.

  Justin

• The index of the primary key in a different tablespace.

  Hello
  
  I have a user PROD. It has received a tablespace PROD_TBS default.
  There is a separate table for all indexes space in the diagram, PROD_IDX.
  
  I want to create a TEST table as follows,
  
  CREATE TABLE TEST
  (TEST_ID, NUMBER (1),)
  NAME VARCHAR2 (10));
  
  It must be a primary key on the column test_id, but such that the corresponding unique index created by default because of the primary key must be created in the PROD_IDX tablespace.
  
  How to do this?

  Alternative solution:

  CREATE TABLE TEST
  (TEST_ID NUMBER(1),
  NAME VARCHAR2 (10),
  constraint test_pk primary key (test_id)
  using index tablespace prod_idx
   );
  

  Cheers, APC

  blog: http://radiofreetooting.blogspot.com

• primary key constraint...

  Hi all
  
  I have a table 'employees' on 'hr' scheme, now, I created a user 'rahul' on the same database and pulling a request by logging in with the user "rahul" which is:
  
  create table rahul.employees
  as (select * from hr.employees); -ps: I have the privilege to read data from hr.employees
  
  Now, the above query works fine, the only issue is that employe_id is the primary key for the table hr.employees and when I check the table of rahul.employees, the pruimary key constraint is missing, however the structure of the table and the data is there according to my expectations.
  
  I so want to know how to create a table with data using the definition of schema_name.table_name as well as the primary key constraint.
  
  Concerning
  Rahul karou

  Mac_Freak_Rahul wrote:
  Thanks for the reply, but this query returns me nothing, is it a question of privilege?

  Concerning
  Rahul

  Are you an error? Otherwise, the result will be CLOB, just copy from your clint tool and paste it into a Notepad...

  between it's table

  CREATE TABLE "HR"."EMPLOYEES1"
     (     "EMPLOYEE_ID" NUMBER(6,0),
       "FIRST_NAME" VARCHAR2(20),
       "LAST_NAME" VARCHAR2(25) CONSTRAINT "EMP_LAST_NAME_NN" NOT NULL ENABLE,
       "EMAIL" VARCHAR2(25) CONSTRAINT "EMP_EMAIL_NN" NOT NULL ENABLE,
       "PHONE_NUMBER" VARCHAR2(20),
       "HIRE_DATE" DATE CONSTRAINT "EMP_HIRE_DATE_NN" NOT NULL ENABLE,
       "JOB_ID" VARCHAR2(10) CONSTRAINT "EMP_JOB_NN" NOT NULL ENABLE,
       "SALARY" NUMBER(8,2),
       "COMMISSION_PCT" NUMBER(2,2),
       "MANAGER_ID" NUMBER(6,0),
       "DEPARTMENT_ID" NUMBER(4,0),
        CONSTRAINT "EMP_SALARY_MIN" CHECK (salary > 0) ENABLE,
        CONSTRAINT "EMP_EMAIL_UK" UNIQUE ("EMAIL")
    USING INDEX  ENABLE,
        CONSTRAINT "EMP_EMP_ID_PK" PRIMARY KEY ("EMPLOYEE_ID")
    USING INDEX ENABLE,
        CONSTRAINT "EMP_MANAGER_FK" FOREIGN KEY ("MANAGER_ID")
         REFERENCES "HR"."EMPLOYEES" ("EMPLOYEE_ID") ENABLE,
        CONSTRAINT "EMP_JOB_FK" FOREIGN KEY ("JOB_ID")
         REFERENCES "HR"."JOBS" ("JOB_ID") ENABLE,
        CONSTRAINT "EMP_DEPT_FK" FOREIGN KEY ("DEPARTMENT_ID")
         REFERENCES "HR"."DEPARTMENTS" ("DEPARTMENT_ID") ENABLE
     ) 
  

• Direct path SQLLDR allows duplicates in the primary key

  I would use sqlldr path direct to charge millions of records in the table but direct way allows duplicates on the primary key constraints.
  
  inserts of duplicates
  sqlldr control deploy_ctl/deploy_ctl@dba01mdm = direct ctl_test.ctl = true
  primary key is enabled
  
  I do not understand the behavior that's why the primary key is always enabled--(logiquement il doit avoir désactivé que doublons insérés)
  
  Inserts no duplicates
  sqlldr control = ctl_test.ctl deploy_ctl/deploy_ctl@dba01mdm
  primary key is enabled
  
  Please can I know if there is any work around to use direct path with constraints of primary school in place.

  The only solution is to not use direct load, if your dataset contains records in duplicate, of the documentation:

  /*
  A record that violates a UNIQUE constraint is not rejected (the file is not available in the memory when the constraint violation is detected).
  */

• modify a primary key constraint

  Hello
  
  I start with oracle, and I have two doubts which cannot handle after a search on the internet.
  
  1. it is possible to do an ALTER TABLE for a DEFAULT CONSTRAINT?. Maybe you think that the question should be in a different way like this: oracle database takes the default condition as a constraint?. As far as I know, not done that.
  
  2. it is possible, with an ALTER TABLE to CHANGE a CONSTRAINT of a PRIMARY KEY, to add another field more?
  
  I searched the internet, but I have not found a clear answer. I use oracle 10g express edition.
  
  
  Thank you very much.
  
  P.D.:sorry for my English, it is not very good.

  #2-you can not 'add a column to the primary key of a table constraint' with a single ALTER, but you can delete and re-create the constraint primary key (including the additional column).

  13:25:26> create table t1 (a number primary key, b number, c number );
  
  Table created.
  
  Elapsed: 00:00:00.09
  13:25:46> alter table t1 drop primary key;
  
  Table altered.
  
  Elapsed: 00:00:00.06
  13:25:47> alter table t1 add primary key (a,b);
  
  Table altered.
  
  Elapsed: 00:00:00.09
  

  But you will not be able to drop the primary key of a table index.

  13:25:47> create table t2 (a number primary key, b number, c number ) organization index;
  
  Table created.
  
  Elapsed: 00:00:00.03
  13:25:59> alter table t2 drop primary key;
  alter table t2 drop primary key
  *
  ERROR at line 1:
  ORA-25188: cannot drop/disable/defer the primary key constraint for
  index-organized tables or sorted hash cluster
  
  Elapsed: 00:00:00.00
  13:25:59> 
  

  #1-I'm not sure I understand your question, but you can change a table column to have a default value. This isn't a "constraint", but a default value. It has an effect when you perform an insert which does not include this column.

  13:31:23> alter table t1 modify (c default 3.14);
  
  Table altered.
  
  Elapsed: 00:00:00.04
  13:31:24> insert into t1 (a,b,c) values (1,2,3);
  
  1 row created.
  
  Elapsed: 00:00:00.01
  13:31:24> insert into t1 (a,b,c) values (4,5,NULL);
  
  1 row created.
  
  Elapsed: 00:00:00.00
  13:31:24> insert into t1 (a,b) values(6,7);
  
  1 row created.
  
  Elapsed: 00:00:00.01
  13:31:24> select * from t1;
  
           A          B          C
  ---------- ---------- ----------
           1          2          3
           4          5
           6          7       3.14
  
  3 rows selected.
  
  Elapsed: 00:00:00.18
  

• Automatically fill the primary key

  We have Oracle database 10g. I've added a primary key column to my deo_language_resources_t of table with the following logic:
  
  -- 1. create sequences
  create sequences eod_lr_seq
  Start increment by 10 by 5
  MinValue 10 nomaxvalue
  NoCache;
  
  -- 2. Create the primary key column
  ALTER table deo_language_resources_t
  ADD NUMBER RESOURCE_ID;
  
  -- 3. Fill the pk
  Update deo_language_resources_t
  Set id_ressource = eod_lr_seq.nextval
  where id_ressource is null;
  
  -- 3. Create the primary key constraint
  ALTER table deo_language_resources_t
  Add constraint resource_id_pk key (resource_id) primary;
  
  insert into deo_language_resources_t
  (first_name, last_name, id_ressource)
  values ('John', 'Doe', eod_lr_seq.nextval);
  
  The last INSERT statement successfully a line inserted into the table and populated by id_ressource with the next number in the sequence eod_lr_seq. Ok.
  
  Is it possible to set a constraint on deo_language_resource_t so that when I INSERT a line the id_ressource is automatically set to eod_lr_seq.nextval? It is possible to define a trigger and resembling the logic of the trigger? The insert statement would be like:
  
  INSERT INTO deo_language_resources_t (first_name, last_name) VALUES ('John', 'Doe');

  create trigger deo_language_resources_trigger
  before insert on deo_language_resources_t
  for each row
  begin
  select eod_lr_seq.nextval into :resource_id from dual;
  end;
  

• Create the primary key on the target

  Y at - it no IKM which would create the primary key on target after having read the instructions for the source?
  
  Thank you
  Dinesh.

  Hi Dinesh,

  You can customize a KM to create a primary key on the target
  The target table will be created with the mention of the primary key constraint in the data target store.

  Steps: -.

  Customiuse creating target step of the table and I create $ step table.

  for example: -.

  original train target table KM walk (IKM Oracle Simple incremental update): -.

  create table< %="snpRef.getTable" ("l",="" "a",="" "targ_name")="" %="">
  (
       <%=snpRef.getTargetColList("", "[COL_NAME]\t[DEST_CRE_DT] NULL", ",\n\t", "")%>
  )

  custom STAGE: -.

  create table< %="snpRef.getTable" ("l",="" "a",="" "targ_name")="" %="">
  (
       <%=snpRef.getTargetColList("", "[COL_NAME]\t[DEST_CRE_DT] NULL", ",\n\t", "")%>

  CONSTRAINT constraint_name PRIMARY KEY (< %="snpRef.getColList" ("",="" "[column]",="" ",",="" "",="" "pk")="" %="">)
  )

  Note:- The code above described here is just a sample of reference. I did not test the syntax.

  Kind regards
  Its

• Not Null on the column of a primary key constraint

  I came across a table defined in the same way to...
  
  create table t (t_id int constraint nn_t_id not null constraint pk_t primary, data key number);
  
  Of course, the primary key is the is not null, then is there a reason to add the redundant constraint not null?

  There are two parts to your question, I think:

  (1) why add a NOT NULL if a primary key is also reported.
  (2) why is null is NOT a name defined by the user (in this case nn_t_id).

  1 > I think you are right: there is no difference in behavior in the way that Oracle is going to reject the creation of NULL in this column (whether through the direct insert or update with a NULL value). I personally always declares the NOT NULL for columns, I know to never have null, regardless of whether the column is (member of) a PK.

  It's pretty funny, btw, the SQL standard as chosen able to be the NULL default value. I think that we all type much less, if the SQL standard chose NOT NULL default value. But that's another story.

  2 > I don't see given nullability defined by the user of the explicit names now and then, because of some "coding guideline' which dictates that constraint names must never be generated System. This guideline is often presented as a result of the exception handling of "client-side", where the constraint name is filtered SQLERRM and then more personalized to be displayed to the end user. However for NOT NULL constraint violations, I think (does not fully to check) that you are always thrown an ORA-01400 is an ORA-01407. Who nowadays both will tell you exactly (in SQLERRM) which column of this table is currently in violation of a NOT NULL constraint.

  Toon

• need to based on the primary key of different table 2 foreign key constraint

  I'm using Oracle 11.2.0.3.

  I have 2 table invl with invl_pk as primary key and org with org_pk as the primary key.

  In the third table entity_list, I have entity_pk that can be indvl_pk or org_pk.   How can I create this constraint?

  Thanks for your time.

  Hello

  Assuming that your model is correct, then what you describe is a normal type of ER modeling construction known as a relationship of the CRA. It is characterized by an entity with two or more links that are mutually exclusive to each other (XOR). A typical example may be where a person entity and an entity of the Organization relate both to a bank account entity, but a bank account can only be used by a person or an organization in a mutually exclusive way. In order to serve this on a diagram, an arc is drawn between effective relationships on the side of the child, where the name of a relationship of the CRA.

  Google will be of multiple examples and explanations.

  In a perspective of physical databases, this can be implemented in general in two different ways.

  1. assuming that all parents in the relationship of the CRA have identical PK, that is to say, a number that is generated, the child may have a FK of the same type and an entity of type column that defines what entity the FK is. The advantage of this is that it is a bit more compact and is expandable without schema changes if you want to add more relationships. The downside of this is that the CF cannot be defined at the database level and will build on the code to be executed or both in the application and the database as a trigger.

  2. regardless of types PK for parent entities, the child has a separate optional FK appropriate for each relationship in the arc. Each FK is defined at the database level while maintaining the exclusivity of relationships, a constraint is defined on the table that prevents several FK being filled for a given instance. This can be a little messier that there must be a (column/s) FK for each relationship in the arc, but the relationship may be limited to the level of the object database with the help of FK constraints and a check constraint. This could also be considered to be more technically correct implementation.

  Hope this helps

  André

• How to refer to the primary key column of newly inserted rows of tabular form

  Hello

  I use APEX 4.2.0.00.27 with Oracle DB 11.2.0.3.0.

  I work with a tabular presentation wizard-created for insert and update a table using the integrated SRM process (sequence 10).  I'm trying to use a process of anonymous block of PL/SQL (sequence 30) to make another manipulation of table after the records were inserted or updated.  The manual process is associated with my tabular form and I use the variables of name of column binding in my program block.

  My (rsn_test) table has 3 columns: test_id (number), test_nbr (number), test_id2 (number).  Test_id column is identified as the primary key and the type of the source already exists a sequence rsn_test_seq.  Column test_id2 gets its default value 0 to a hidden page element.

  I would use my manual process for updating the value of the test_id2 column.  If it's 0 then I want to put the value of the column test_id.  If it is any other value, then it must remain at this value.  My logic works very well for an existing line, but I'm running into a problem with the newly added lines.  The new lines get inserted, but the test_id2 column remains the default value 0.  I can tell the debugger that the SRM process is triggered first and inserts the line, then my manual dealing with fires.  The problem seems to be that the connection variable: TEST_ID for the primary key column remains NULL after insertion.  I don't know how to get the value of the column test_id of my newly created line to use in my PL/SQL block to my update.

  Process of PL/SQL:

  DECLARE
  BEGIN
     :P7_SHOW := NULL;
     :P7_SHOW := NVL(:TEST_ID2,555) || ' and ' || NVL(:TEST_ID,787) || ' and ' || NVL(:TEST_NBR,9999);
     IF :TEST_ID2 = 0 AND :TEST_ID IS NOT NULL THEN
        UPDATE rsn_test
           SET test_id2 = :TEST_ID
         WHERE test_id = :TEST_ID;
     ELSE
        :TEST_ID2 := :TEST_ID2;
     END IF;
  END;
  
  

  Excerpt from the debugger:

  0.01625 0.00010 Processes - point: ON_SUBMIT_BEFORE_COMPUTATION
  0.01635 0.00008 Branch point: Before Computation
  0.01643 0.00003 Process point: AFTER_SUBMIT
  0.01646 0.00022 Tabs: Perform Branching for Tab Requests
  0.01668 0.00008 Branch point: Before Validation
  0.01676 0.00024 Validations:
  0.01700 0.00135 Perform basic and predefined validations:
  0.01835 0.00020 Perform custom validations:
  0.01855 0.00049 ...Validation "TEST_NBR must be numeric" - Type: ITEM_IS_NUMERIC
  0.01904 0.00007 ......Skip for row 1 because row hasn't changed
  0.01911 0.00016 ......Skip for row 2 because row hasn't changed
  0.01927 0.00012 ...Validation "TEST_ID2 must be numeric" - Type: ITEM_IS_NUMERIC
  0.01939 0.00007 ......Skip for row 1 because row hasn't changed
  0.01945 0.00018 ......Skip for row 2 because row hasn't changed
  0.01964 0.00005 Branch point: Before Processing
  0.01968 0.00004 Processes - point: AFTER_SUBMIT
  0.01972 0.00588 ...Process "ApplyMRU" - Type: MULTI_ROW_UPDATE
  0.02560 0.00154 ...Execute Statement: declare function x return varchar2 is begin begin for c1 in ( select "RSN_TEST_SEQ".nextval pk from sys.dual ) loop return c1.pk; end loop; end; return null; end; begin wwv_flow.g_value := x; end;
  0.02714 0.00140 ......Row 3: insert into "APPPCSRSN"."RSN_TEST" ( "TEST_ID", "TEST_NBR", "TEST_ID2") values ( :b1, :b2, :b3)
  0.02854 0.00011 ...Process "ApplyMRD" - Type: MULTI_ROW_DELETE
  0.02865 0.00004 ......Skip because condition or authorization evaluates to FALSE
  0.02869 0.00015 ...Process "Process Submit" - Type: PLSQL
  0.02884 0.00007 ......Skip for row 1 because row hasn't changed
  0.02891 0.00012 ......Skip for row 2 because row hasn't changed
  0.02903 0.00012 ......Process row 3
  0.02915 0.00429 ...Execute Statement: begin DECLARE BEGIN :P7_SHOW := NULL; :P7_SHOW := NVL(:TEST_ID2,555) || ' and ' || NVL(:TEST_ID,787) || ' and ' || NVL(:TEST_NBR,9999); IF :TEST_ID2 = 0 AND :TEST_ID IS NOT NULL THEN UPDATE rsn_test SET test_id2 = :TEST_NBR WHERE test_id = :TEST_ID; ELSE :TEST_ID2 := :TEST_ID2; END IF; END; end;
  0.03344 0.00013 ...Session State: Saved Item "P7_SHOW" New Value="0 and 787 and 1300"
  0.03356 0.00004 Branch point: After Processing
  0.03360 0.00048 ...Evaluating Branch: "AFTER_PROCESSING" Type: REDIRECT_URL Button: (No Button Pressed) Condition: (Unconditional)
  0.03407 0.00013 Redirecting to f?p=290:7:8717971109610:::::&success_msg=0%20row(s)%20updated%2C%201%20row(s)%20inserted.Success%2FEBD244168556408CBA714E3974918C09%2F
  0.03420 0.00012 Stop APEX Engine detected
  0.03432 0.00007 Stop APEX Engine detected
  0.03439 - Final commit
  
  

  Any suggestions?

  I have run tests on

  https://apex.Oracle.com/pls/apex/f?p=83488:1 demo/demo

  to see your problem.

  I have 2 solution for your problem.
  I add trial NOT tabular just usual block of PL/SQL

  	BEGIN
  	I'm IN (SELECT TEST_ID FROM RSN_TEST WHERE TEST_ID2 = 0)
  	LOOP
  	UPDATE RSN_TEST
  	SET test_id2 = TEST_ID
  	WHERE test_id = i.TEST_ID;
  	END LOOP;
  	END;

  and works very well, you can see in the sample.

  The other solution is to show new generated TEST_ID

  Adding a sequence as a default value for a column in a table field

  And to execute your procedure.

  I get how is with the good luck of time.

  By

• Update fails because of a foreign key constraint

  Hello.
  
  I have several tables in my database but 3 are important. One of them is used (Employee_ID, Last_Name and other irrelevant columns name), dentist (employe_id, Qualifications) and Wizard (Employee_ID, Qualifications).
  I am applying in Oracle Application Express and trying to update a row in the Employee table, I get an ORA-20505: error in DML: p_rowid = 96, p_alt_rowid = employe_id, p_rowid2 =, p_alt_rowid2 is. ORA-02292: integrity constraint (DB. Dentist_CON) violated - book of the foundling
  
  Now, first of all, I had the same problems with the removal of lines, but I've solved that by adding a delete cascade on foreign keys.
  I have key constraints foreign both in my paintings dentist and Assistant in columns Employee_ID and these refer to Employee_ID in the Employee table.
  
  When I update anything in my Express request form, I've allowed users to do anything of my Employee table primary key (employe_id). Any changes that might occur therefore columns unrelated to the primary key. For example, if I change the name of a particular line column I can't update because I get the above error.
  
  I don't understand why this is happening.
  If I could get a glimpse, why this is happening or using any I would be very happy.
  
  Thanks in advance.

  982909 wrote:
  But it is not true. If I'm changing the name of the employee and update this line in employee WITHOUT changing the value of Employee_ID how can I possibly change the daughter line? This is what is confusing in that me and I have no idea on how to solve it.

  the code below shows above is NOT true

  CREATE OR REPLACE TRIGGER "Employee_T1".
  FRONT
  Insert or update on "employee."
  for each line
  Start
  Select employee_sequence.nextval in: double new.employee_id;
  end;
  /

  TRIGGER above changes EMPLOYEE_ID for all training update!

• best method to update the primary key

  Can someone tell me the best possible method to update the primary key so that the foreign key is also updated.
  Please explain with example

  940340 wrote:
  Can someone tell me the best possible method to update the primary key so that the foreign key is also updated.
  Please explain with example

  You're after a mechanism that lets you update the primary key sometimes on some lines, or did you just impossible, which means that you must update all the data because of some kind of change in the structural definition?

  If all you need is a rational method to change keys sometimes (and this isn't quite mortal sin that other posters have been suggesting) then recreate your foreign key as a constraint can be delayed may help.

  Oracle allows no you cascading updates automatically for primary keys, but if the foreign key is carried forward you can proceed as follows:

  set constraint {foreign key constraint name} deferred;
  update parent primary key;
  update child foreign key;
  set constraint {foreign key constraint name} immediate;
  

  Concerning
  Jonathan Lewis