Updating related Records primary key and FK dependencies

Similar Questions

• Difference of path between primary key and a Unique Index

  Hi all
  
  Is there a specific way the oracle optimizer to treat differently the Primary key and Unique index?
  
  Oracle Version

  SQL> select * from v$version;
  
  BANNER
  --------------------------------------------------------------------------------
  Oracle Database 11g Enterprise Edition Release 11.2.0.3.0 - 64bit Production
  PL/SQL Release 11.2.0.3.0 - Production
  CORE    11.2.0.3.0      Production
  TNS for IBM/AIX RISC System/6000: Version 11.2.0.3.0 - Production
  NLSRTL Version 11.2.0.3.0 - Production
  
  SQL> 

  Sample data test for Index Normal
  

  SQL> create table t_test_tab(col1 number, col2 number, col3 varchar2(12));
  
  Table created.
  
  SQL> create sequence seq_t_test_tab start with 1 increment by 1 ;
  
  Sequence created.
  
  SQL>  insert into t_test_tab select seq_t_test_tab.nextval, round(dbms_random.value(1,999)) , 'B'||round(dbms_random.value(1,50))||'A' from dual connect by level < 100000;
  
  99999 rows created.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> exec dbms_stats.gather_table_stats(USER_OWNER','T_TEST_TAB',cascade => true);
  
  PL/SQL procedure successfully completed.
  
  SQL> select col1 from t_test_tab;
  
  99999 rows selected.
  
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 1565504962
  
  --------------------------------------------------------------------------------
  | Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
  --------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT  |            | 99999 |   488K|    74   (3)| 00:00:01 |
  |   1 |  TABLE ACCESS FULL| T_TEST_TAB | 99999 |   488K|    74   (3)| 00:00:01 |
  --------------------------------------------------------------------------------
  
  
  Statistics
  ----------------------------------------------------------
            1  recursive calls
            0  db block gets
         6915  consistent gets
          259  physical reads
            0  redo size
      1829388  bytes sent via SQL*Net to client
        73850  bytes received via SQL*Net from client
         6668  SQL*Net roundtrips to/from client
            0  sorts (memory)
            0  sorts (disk)
        99999  rows processed
  
  SQL> create index idx_t_test_tab on t_test_tab(col1);
  
  Index created.
  
  SQL> exec dbms_stats.gather_table_stats('USER_OWNER','T_TEST_TAB',cascade => true); 
  
  PL/SQL procedure successfully completed.
  
  SQL> select col1 from t_test_tab;
  
  99999 rows selected.
  
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 1565504962
  
  --------------------------------------------------------------------------------
  | Id  | Operation         | Name       | Rows  | Bytes | Cost (%CPU)| Time     |
  --------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT  |            | 99999 |   488K|    74   (3)| 00:00:01 |
  |   1 |  TABLE ACCESS FULL| T_TEST_TAB | 99999 |   488K|    74   (3)| 00:00:01 |
  --------------------------------------------------------------------------------
  
  
  Statistics
  ----------------------------------------------------------
            1  recursive calls
            0  db block gets
         6915  consistent gets
            0  physical reads
            0  redo size
      1829388  bytes sent via SQL*Net to client
        73850  bytes received via SQL*Net from client
         6668  SQL*Net roundtrips to/from client
            0  sorts (memory)
            0  sorts (disk)
        99999  rows processed
  
  SQL> 

  Examples of test when using primary key data
  

  SQL> create table t_test_tab1(col1 number, col2 number, col3 varchar2(12));
  
  Table created.
  
  SQL> create sequence seq_t_test_tab1 start with 1 increment by 1 ;
  
  Sequence created.
  
  SQL> insert into t_test_tab1 select seq_t_test_tab1.nextval, round(dbms_random.value(1,999)) , 'B'||round(dbms_random.value(1,50))||'A' from dual connect by level < 100000;
   
  99999 rows created.
  
  SQL> commit;
  
  Commit complete.
  
  SQL> exec dbms_stats.gather_table_stats('USER_OWNER','T_TEST_TAB1',cascade => true);
  
  PL/SQL procedure successfully completed.
  
  SQL> select col1 from t_test_tab1;
  
  99999 rows selected.
  
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 1727568366
  
  ---------------------------------------------------------------------------------
  | Id  | Operation         | Name        | Rows  | Bytes | Cost (%CPU)| Time     |
  ---------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT  |             | 99999 |   488K|    74   (3)| 00:00:01 |
  |   1 |  TABLE ACCESS FULL| T_TEST_TAB1 | 99999 |   488K|    74   (3)| 00:00:01 |
  ---------------------------------------------------------------------------------
  
  
  Statistics
  ----------------------------------------------------------
            1  recursive calls
            0  db block gets
         6915  consistent gets
            0  physical reads
            0  redo size
      1829388  bytes sent via SQL*Net to client
        73850  bytes received via SQL*Net from client
         6668  SQL*Net roundtrips to/from client
            0  sorts (memory)
            0  sorts (disk)
        99999  rows processed
  
  SQL> alter table t_test_tab1 add constraint pk_t_test_tab1 primary key (col1);
  
  Table altered.
  
  SQL> exec dbms_stats.gather_table_stats('USER_OWNER','T_TEST_TAB1',cascade => true); 
  
  PL/SQL procedure successfully completed.
  
  SQL> select col1 from t_test_tab1;
  
  99999 rows selected.
  
  
  Execution Plan
  ----------------------------------------------------------
  Plan hash value: 2995826579
  
  ---------------------------------------------------------------------------------------
  | Id  | Operation            | Name           | Rows  | Bytes | Cost (%CPU)| Time     |
  ---------------------------------------------------------------------------------------
  |   0 | SELECT STATEMENT     |                | 99999 |   488K|    59   (2)| 00:00:01 |
  |   1 |  INDEX FAST FULL SCAN| PK_T_TEST_TAB1 | 99999 |   488K|    59   (2)| 00:00:01 |
  ---------------------------------------------------------------------------------------
  
  
  Statistics
  ----------------------------------------------------------
            1  recursive calls
            0  db block gets
         6867  consistent gets
            0  physical reads
            0  redo size
      1829388  bytes sent via SQL*Net to client
        73850  bytes received via SQL*Net from client
         6668  SQL*Net roundtrips to/from client
            0  sorts (memory)
            0  sorts (disk)
        99999  rows processed
  
  SQL> 

  If you see here the same even as the statistics were gathered,
  * In the 1st table T_TEST_TAB, table always use FULL table access after creating indexes.
  * And in the 2nd table T_TEST_TAB1, table uses PRIMARY KEY as expected.
  
  Any comments?
  
  Kind regards
  BPat

  >
  * In the 1st table T_TEST_TAB, table always use FULL table access after creating indexes.
  * And in the 2nd table T_TEST_TAB1, table uses PRIMARY KEY as expected.
  >
  Yes - for the first table a full table scan will be used as the currently selected column is nullable and indexes do not include null values.

  The index can be used for the second query, since all the data (first column) is available between the index and there may be no NULL values because of the primary key. If you check constraints, you find that the there is now a CHECK constraint to ensure that the first column cannot be null.

  For a full and interesting discussion see the explanation of this and a related issue on the question I ask in this thread
  What SYS tables (not seen) contain the value NULL spec /not/ column definition? and my response he posted: 23 April 2012 09:02

  I ask the question is based on a question here which is similar to yours
  Columns becoming nullable after a fall of primary key?

• Problem with the primary key and indexes

  Hi all
  
  I'm looking a mess on one of our main tables.
  One of the developers here added an index on 3 columns in the table, thinking that it would speed up (not noticing that it had not a PK).
  
  Subsequently another developer has noticed there do not have a primary on key. So they added a touch of primry on the single column.
  
  The problem is that now the index created on 3 columns is bein used as the primary key index. As when the primary key is created a new index was not created.
  
  Is there anyway to get rid of this index/change it correct?
  
  This table is related to many many other tables, so when we tried to remove the index we could not due to the primary key and foreign key violations with other tables.
  
  Thanks in advance

  Oracle, as you found, is quite capable to use a column enformce multi index a single column primary key, as long as the pk column is the leader in the index. This should not cause performance issues for a search of PK and if the three indexed columns are often selected only may benefit from these types of queries.

  The only way to change that now, would be to drop all CF, drop and add the PK constraint and then add all the FK constraints. A long time and potentially dangerous (if you miss to add back of the FKs) endeavour. Certainly not worth the risk in my opinion.

  John

• manually assign primary key and copy to the detailed form

  Hi experts,

  Oracle Apex 4.2, 11g database, using windows 7.

  I created a form and created automatic product no. (not only sequence) with logic and SQL. SQL query produced good wise exercise, and exercise begin from 01 July and ends 30 June each year. This means if the 07/01/2015 start it will create a new voucher No.

  The main Table name is GL_PV and the columns are:

  Number of PV_No

  Date of PV_Date

  Number of CC_code

  number amount

  Remarks varchar2 (100)

  Created a process to submit before the calculations and validations.

  The codes are

  NVL SELECT (MAX (to_number (nvl(pv_no,0))) + 1, 1) AMENDMENTS

  IN: P15_pv_no

  OF GL_PV

  WHERE pv_date

  BETWEEN to_date (' 01-07-' |) (extract (year from to_date (: P15_pv_date, "dd-mm-yyyy")))

  + case when extracted (month of to_date (: P15_pv_date, "dd-mm-yyyy")) < = end of another 0, then 6-1), "dd-mm-yyyy")

  AND to_date (30 - 06-' |) (extract (year from to_date (: P15_pv_date, "dd-mm-yyyy")))

  (+ case when extracted (month of to_date (: P15_pv_date, "dd-mm-yyyy")) < = 6 then 0 otherwise 1 end), "dd-mm-yyyy")

  and cc_code =: P15_cc_code;

  and press the button when Conditions = Generate_Button

  In the form of master I put the data and click on create button is working well and generating good can result.

  Now that I've created a detail of my detail table is pv_detail and the columns are

  pv_voucher_no

  pv_date

  account_code

  Remarks

  amount

  I want to create the relationship of the master / detail form.

  I tried:

  • primary key and foreign key, but does not. column GL_PV table primary key (PV_NO, PV_DATE), PV_DETAIL (pv_voucher_no, pv_date) foreign key table columns: -.
  • has created one for master and 2nd 2 form for details, good master shape generates but not detail of.

  I want to assign pv_no, pv_date in both value table (master / detail), in other words copy value pv_no and pv_date of main table in detail table pv_voucher_no and pv_date.

  Please advise how I can solve this problem.

  Thank you forum oracle to solve my problems.

  
  

  error report: ORA-01790: expression must have the same type of data, matching expression

  Find the solution on this forum

  Solution:

  Attributes and the tabular form:

  Change the default type = PL/SQL Expression on the function

  Default = to_date(:P15_PV_DATE,'DD-MON-YYYY')

  
  

  
  

• Primary key and unique key not Null

  Hello gurus,
  
  Asked in an interview about the difference between primary and unique keys.
  I talked Unique keys can accept null values, but they are unique through should have the table. So, the next question asked me was "a Unique key NOT NULL can be treated as the primary key?
  
  Tricky question! :)
  I said yes! that it meets the requirement to be a primary key for this particular table, but since this isn't really a primary key, that it can't be covered in the foreign keys.
  
  The interviewer wanted just a Yes or no.
  
  Can someone please put some of this?
  
  Thanks in advance!

  Two things.
  1. unique can also be referenced as a foreign key. If your statement "but because this isn't really a primary key may not be seized key foreign." is not true.
  2. primary key and Unique key are different (for example you can have more than one UK in a table but PK's alone) and to know the difference, read some RDBMS concepts.

  I'm curious to know what is the outcome of your interview? ;)

• update of a primary key column

  Hello

  I have a problem I want to expose you for your opinion.

  In a table of the source, I have a primary key consisting of four columns (let's call them A, B, C and D).

  Columns D must be updated with a different value (a Mappin with another table)

  My ODI interface, I set the update keys a, B, C, but of course, it does not work because there is violation of the primary key

  I thought, the first value of D in a new column (D_OLD) and use as a 4th update key.

  What do you think?

  Please suggest me the right way to do it

  Thank you for your return

  Hello

  Maybe I did not understand your problem correctly, but you say that you want to update the value of col D what happens to the part b of your primary key. You cannot update the row using columns A, B and C, because they are not unique. Am I wrong? If this is the case, then how will you identify which line you want to update the value of col D for. Tell if you have 2 lines with the same value for columns A, B and C, and a different value of D so how do you know which line you want to update? If you have the answer to this question, then you should be able to update as well.

  Thank you

  Ajay

• Potential problems for tables without primary keys and unique keys

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

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

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

  It really depends on the data.

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

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

• What is the difference between primary key and unique indexes with forced not null?

  Primary key is = unique index + not null?

  The short answer is Yes.

  However, even if the primary key, applying both uniquness and not null, there is a notion of "special".

  You can only have one primary key in tables, but you can have multiple unique indexes and constraints not null.

  See: https://asktom.oracle.com/pls/asktom/f?p=100:11:0:P11_QUESTION_ID:8743855576462

• Primary key and foreign key between the different schemas

  Hi all;

  SCOTT user have a 'rank' of table-> it contains the primary key-> users tablespace

  The U1 user have a 'emp' table-> it contains the foreign key-> test tablespace

  U1 > select constraint_name, constraint_type, r_owner, owner, r_constraint_name of all_constraints where table_name = 'EMP ';

  OWNER CONSTRAINT_NAME C R_OWNER R_CONSTRAINT_NAME

  ------------ ------------------------------ - -------------------------- ----------------------- -----------------------------------------------------

  U1              EMP_EMPLEV_C12_FK R SCOTT GRADE_GRL_C1_PK

  If I have connection U1, no possibility to find the name of the primary key without connection scott table?

  Thank you

  Hello

  So, you want to know what picture of the SCOTT schema has the constraint that is named "GRADE_GRL_C1_PK." Isn't it?

  If so,.

  SELECT table_name

  Of all_constraints

  Owner WHERE = 'SCOTT '.

  AND the argument constraint_name = 'GRADE_GRL_C1_PK. '

  ;

• View of Materlized primary key and primary key in the master tables

  We use the Oracle 11 g 2 and I created a view on several paintings of master materlized. The paintings of masters all have the primary key, but I understand not all primary key columns in the query definition.
  According to Oracle manual e10592

  Specify WITH PRIMARY KEY to create a primary key materialized view. This is the default ....
  The master table must contain an enabled primary key constraint, and the defining query of the materialized view 
  must specify all of the primary key columns directly.

  My MV created OK and works. My question is what can be the impact on my MV? Could he hit to performance. It takes 40 minutes to the MV should be created and 5 minutes to refresh the one line insert in each table of mater. I would like to see it refresh in a few seconds.

  Retrieve the lines of the mview is purely a function of the number of lines and indexing on the mview himself. Mview refreshing at the time of the wall depends on the quality of the query used to refresh the mview. If you include the PKs of the source table in the mview matter or not, here. What matters is the execution of the refresh request path. Is it okay to indexation on the underlying tables to support the joints. Did you use mlog$ _s to allow a quick refresh - mlog$ _s are still usable for your mview. There are a number of possible causes for your problem and we do not have enough information to make an estimate of the problem.

  BTW, if the mview could refresh in a few seconds without mlog$ _s, probably unnecessary a mview.

• Primary key and foreign key

  Hi all
  
  I'm confused. If I create a primary key of table constraints, it willl create a unique index by default. If I create a foreign key, it also creates an index? of any kind?
  
  
  Thank you very much
  
  Kinz

  Laughing out loud. foreign key does not have a unique index on the table.

• Change in the merger of insert and create a procedure for updating the records after

  Hello
  
  I have a table that contains about 50 M lines of partition, and every day I have an application that performs a merge to insert records statement about 100 k per day and it's 300 M updates a day.
  
  Because I both update and insert the application performs a merge.
  I need to make at least 500 M, updated day by day, and for this reason this solution doesn't have enough performance for what I'm asking.
  
  I think another solution that I will try to implement now, and I just posted this in an attempt to get help on the option that I may have to do.
  
  I want to start putting in place:
  -Locations is updated 'last_record_date' using 'KEY1' and 'Key2' "KEY3";
  -Change the application to only inserts into a temporary table.
  -Have two procedures, one that takes the new records from the temporary table and inserts it into the final table, and another that selects records which is updated and perform an update.
  -This two procedures will choose the records and delete them from the temporary table (or mark them as updated\inserted).
  
  The volume is very large, so performance is a challenge! That's why I'm writing this, because a solution with enough performance for the intermediate stage will be difficult.
  My final table is partitioned by date and the date is the area that I need to update (instead of create daily partitions in order to reduce the frequency of the movement of the line, I create monthly partitions)!
  It is currently my table definition:

  CREATE TABLE MY_TEST_TABLE
      (KEY1                           VARCHAR2(50 BYTE) ,
      KEY2                         VARCHAR2(50 BYTE) NOT NULL,
      KEY3                           VARCHAR2(50 BYTE) ,
      last_record_date                    VARCHAR2(50 BYTE) NOT NULL)
    PCTFREE     10
    INITRANS    1
    MAXTRANS    255
     STORAGE   (
      BUFFER_POOL DEFAULT
    )
    NOCACHE
    MONITORING
    ENABLE ROW MOVEMENT
    PARTITION BY RANGE (last_record_date)
    (
    PARTITION MY_TEST_TABLE_201112 VALUES LESS THAN ('20120101')
    PCTFREE     10
    INITRANS    1
    MAXTRANS    255
    NOLOGGING,
    PARTITION MY_TEST_TABLE_201201 VALUES LESS THAN ('20120201')
    PCTFREE     10
    INITRANS    1
    MAXTRANS    255
    NOLOGGING,
    PARTITION MY_TEST_TABLE_201202 VALUES LESS THAN ('20120301')
    PCTFREE     10
    INITRANS    1
    MAXTRANS    255
    NOLOGGING,
    PARTITION def VALUES LESS THAN (MAXVALUE)
    PCTFREE     10
    INITRANS    1
    MAXTRANS    255
    NOLOGGING
    )
    NOPARALLEL
  /
  
  
  
  -- Constraints for MY_TEST_TABLE
  
  ALTER TABLE MY_TEST_TABLE
  ADD CHECK ("KEY1" IS NOT NULL)
  /
  
  ALTER TABLE MY_TEST_TABLE
  ADD CHECK ("KEY2" IS NOT NULL)
  /
  
  ALTER TABLE MY_TEST_TABLE
  ADD CHECK ("KEY3" IS NOT NULL)
  /
  ALTER TABLE MY_TEST_TABLE
  ADD CONSTRAINT pk_MY_TEST_TABLE PRIMARY KEY (KEY1, KEY2, KEY3)
  USING INDEX
    PCTFREE     10
    INITRANS    2
    MAXTRANS    255
  /

  Thank you
  Ricardo Tomas

  naoseionome wrote:
  Hello

  My version is:
  Oracle Database 11 g Enterprise Edition Release 11.2.0.2.0 - 64 bit Production

  It's the DOF I used to create the database.

  The merger is common during every day for about 10 M records.

  There are several methods to do the update, but they do sequencially to avoid deadlocks (because I can't control the source and each process can update the same keys.

  The update uses "KEY1, KEY2, KEY3" to update the value 'LAST_RECORD_DATE' have impact by being date or varchar2?

  I'm still waiting to receive permissions in order to follow up the matter, but in the meantime, in that I am trying to implement this work around in order to accelerate a development in the case where it would be necessary! Comments only I have at the moment, it is that he is not able to process the total amount of records timely (order book is generated).

  Thank you
  Ricardo

  Well, the first thing we do is to change the type of data type varchar to a date. The main impact is that a date is not a string, it's a date. If you are adding data processes in different date formats (which is possible when you use a character to store information) you're going to be very sad (good luck converting back an effective date).

  An example of how this can happen easily.

  ME_TUBBZ?select to_char(sysdate) from dual;
  
  TO_CHAR(SYSDATE)
  -----------------------------
  12-jan-2012 10 55:33
  
  1 row selected.
  
  Elapsed: 00:00:00.01
  ME_TUBBZ?alter session set nls_date_format = 'yyyy-mon-dd';
  
  Session altered.
  
  Elapsed: 00:00:00.01
  ME_TUBBZ?select to_char(sysdate) from dual;
  
  TO_CHAR(SYSDATE)
  --------------------
  2012-jan-12
  
  1 row selected.
  
  Elapsed: 00:00:00.00
  

  Assuming that the client passes the column as an Oracle DATE will make an (implicit) conversion to store the data as a string, which will be based on the current settings of the NLS for the session. This allows also for someone to completely non-jour the information in the column (super bad). It's just really bad form to use strings to store dates, numbers, anything that is not naturally a string.

  Based on the description of your problem, I can't imagine how your partitioning scheme performs one action in another that require more work in order to process the updates (which are most of your needs). Partitioning does not equate to increase performance. It is a tool that, like every tool has its place, but I do not think that this is justified for what you do (certainly not how you currently use it anyway).

  I say no partitioning can not be useful for you, but I don't think that on the column that you are currently using is 'good '.

  Something I would like to personally study (must be able to compare this approach to your course, if you need parameters for comparison) if I were you would be using a Table Index organized for it. It will take more time to perform the operations insertion, but that is a small part of all the work that you do for this process. For updates, it should eliminate a lot of IO, assuming that you are doing an INDEX seek followed by a table access by ROWID to perform updates. This recommendation assumes that everything you said is true. You have 4 columns in your table, of which 3 are components of the primary key and the 4th is a date (note I did not string :)) and that you refresh mainly, not fit.) Also that you have no 'secondary' on this entity index (and none are needed).

  I would investigate this approach before the solution of temporary table that you are currently studying.

  See you soon,.

• 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

• References and primary key

  Hello
  I'm trying to greate a new data store and the columns in my oracle Database 11 g. ODI-> new MODEL-> genereate DDL.
  Now, I want to create a new one with primary keys and references, but I can't find the option setting.
  Is it possible to choose this option?
  I work with the German version of ODI.
  
  Concerning
  Michael

  extend the store data, click constraints folder, right-click, and click new key. Now you can select the type of key and on the columns tab, the key columns can be selected.

• Primary key question

  Hello
  
  database version is GR 11, 2; We moved a large table of 12 million records from database 1 database 2. That's how the developers moved:
  
  create the table temp_engine in select * engine;
  
  Then re-named table temp_engine of the engine; but with this method, the primary key and the markings on table engine not copied. If we lose primary key and indexes on table engine. We want to add primary key and indexes, while the application is running. It's high system, busy with many inserts/updates / select on table engine; data are entered into the engine table every 10 minutes;
  
  Issues related to the:
  
  1 - the addition of pk would take time and can slow down the database?
  2 - what kind of locks, if any, we will have when adding the primary key and index?
  3. in the case, we will have the locks when adding the index/pk; the inserts will not happen until the locks to be released just?
  
  
  Thank you very much
  Diego
  
  Published by: Diego 16 April 2012 07:19

  In your first post, you said that your developer have moved (basically it's not moving, rather a copy) by:
  create the table temp_engine in select * engine; the first second db db and now wish you that this new temp_engine has same constraint, privileges, statistics as well as the right table engine? At the same time table is very used in the comic book then, it must avoid any lock or lack of temp straight segment like that?

  So, please check the example below, where you can use EMP as temp_engine and INT_TAB as table of this db engine... after the end of the process, you can simply file temp_engine, rename INT_TAB as an engine.

  Connected to:
  Oracle Database 11g Enterprise Edition Release 11.2.0.1.0 - 64bit Production
  With the Partitioning, OLAP, Data Mining and Real Application Testing options
  
  SQL> create table int_tab as select * from emp where 1=2;
  
  Table created.
  
  SQL> select grantee,privilege from user_tab_privs where table_name='EMP';
  
  GRANTEE                        PRIVILEGE
  ------------------------------ ----------------------------------------
  HR                             SELECT
  HR                             UPDATE
  
  SQL> begin
    2  DBMS_REDEFINITION.CAN_REDEF_TABLE('scott','emp',
    3  DBMS_REDEFINITION.CONS_USE_PK);
    4  end;
    5  /
  
  PL/SQL procedure successfully completed.
  
  SQL> alter session force parallel dml parallel 4;
  
  Session altered.
  
  SQL> alter session force parallel query parallel 4;
  
  Session altered.
  
  SQL> BEGIN
    2  DBMS_REDEFINITION.START_REDEF_TABLE(
    3  uname       => 'SCOTT',
    4  orig_table  => 'EMP',
    5  int_table   => 'INT_TAB');
    6  END;
    7  /
  
  PL/SQL procedure successfully completed.
  
  SQL> DECLARE
    2  num_errors PLS_INTEGER;
    3  BEGIN
    4  DBMS_REDEFINITION.COPY_TABLE_DEPENDENTS(
    5  'SCOTT','EMP','INT_TAB',DBMS_REDEFINITION.CONS_ORIG_PARAMS,
    6  TRUE, TRUE, TRUE, FALSE, num_errors, TRUE);
    7  END;
    8  /
  
  PL/SQL procedure successfully completed.
  
  SQL> BEGIN
    2  DBMS_REDEFINITION.SYNC_INTERIM_TABLE('SCOTT', 'EMP', 'INT_TAB');
    3  END;
    4  /
  
  PL/SQL procedure successfully completed.
  
  SQL> BEGIN
    2  DBMS_REDEFINITION.FINISH_REDEF_TABLE('SCOTT', 'EMP', 'INT_TAB');
    3  END;
    4  /
  
  PL/SQL procedure successfully completed.
  
  SQL> select grantee,privilege from user_tab_privs where table_name='INT_TAB';
  
  GRANTEE                        PRIVILEGE
  ------------------------------ ----------------------------------------
  HR                             SELECT
  HR                             UPDATE
  
  SQL> select constraint_name,constraint_type,table_name from user_constraints where table_name in ('EMP','INT_TAB');
  
  CONSTRAINT_NAME                C TABLE_NAME
  ------------------------------ - ------------------------------
  PK_EMP                         P EMP
  FK_DEPTNO                      R EMP
  TMP$$_PK_EMP0                  P INT_TAB
  TMP$$_FK_DEPTNO0               R INT_TAB
  

  So, at this point, my INT_TAB is just a clone of the EMP table. Even statistics, the privileges and the constraints of the EMP have been applied to INT_TAB. Now, at this point you can drop temp_engine table and can use INT_TAB as an engine.

  Hope I am clear in my answer, if it is not then please keep also close the message.

  Concerning
  Girish Sharma