Update on primary key in indexed table

I need to update an ID# in a table that has been indexed on ID# (and two other columns) using the indextype is ctxsys.context method. Oracle 10g is throwing the following errors:
ORA-20000 "failed in the execution of the ODCINDEXUPDATE routine"
DRG-50857 "oracle error in textindexmethods.ODCIndexUpdate
ORA-20000 "Oracle Text error:
DRG-10602 "failed to queue DML change to column ID# for pimary key AAAMlpAABAAAPy3AAA"
DRG-50857 "oracle error in drekqkd(execute k-stmt)
ORA-00942 "table or view does not exist"
ORA-06512 at "CTXSYS.DRUE", line 160
ORA-06512 at "CTXSYS.TEXTINDEXMETHODS", line 678
Any help would be appreciated as to what I can do to accomplish the update.
Larry

hi,
can you plz post your update statement...
thanks,
baskar.l

Similar Messages

Updation of Primary Key in HR Table(PA2001)

Can anyone please tell me how to update a primary key field in HR Tables (PA2001 and PA2002).
I need to update <b>sprps</b> field in both the tables. I used HR_Infotype_Operation function module, but still it is not updating the field.
Pls find the following code snippet for the table PA2001 and let me know if any discrepancies :
TABLES: pa2001.
DATA: it_pa2001 TYPE TABLE OF pa2001,
      wa_pa2001 LIKE LINE OF it_pa2001,
DATA: date TYPE d.
date = sy-datum - 100.
SELECT pernr sprps begda endda FROM PA2001 INTO CORRESPONDING FIELDS OF TABLE it_pa2001
WHERE begda BETWEEN date and sy-datum.
WRITE:/.
WRITE:/ 'PA 2001 Records'.
if sy-subrc <> 0.
WRITE:/ 'No Data Exists'.
else.
LOOP AT it_pa2001 INTO wa_pa2001.
WRITE:/ wa_pa2001-pernr, wa_pa2001-sprps, wa_pa2001-begda, wa_pa2001-endda.
ENDLOOP.
endif.
LOOP AT it_pa2001 INTO wa_pa2001.
wa_pa2001-sprps = 'X'.
                                 CALL FUNCTION 'HR_INFOTYPE_OPERATION'
                                   EXPORTING
                                     infty                  = '2001'
                                     number                 = wa_pa2001-pernr
                                   SUBTYPE                =
                                   OBJECTID               =
                                   LOCKINDICATOR          =
                                   VALIDITYEND            =
                                   VALIDITYBEGIN          =
                                   RECORDNUMBER           =
                                     record                 = wa_pa2001
                                     operation              = 'MOD'
                                   TCLAS                  = 'A'
                                   DIALOG_MODE            = '0'
                                   NOCOMMIT               =
                                   VIEW_IDENTIFIER        =
                                   SECONDARY_RECORD       =
                                 IMPORTING
                                   RETURN                 =
                                   KEY                    =
ENDLOOP.
if sy-subrc = 0.
write:/ 'SY-subrc is zero'.
write:/ ' Rows modified = ', sy-dbcnt.
else.
write:/ 'No Record(s) updated'.
endif.
commit work.
WRITE: / 'Updated Records in the Internal Table IT_PA2001'.
SELECT pernr sprps begda endda FROM PA2001 INTO CORRESPONDING FIELDS OF TABLE it_pa2001
WHERE begda BETWEEN date AND sy-datum..
LOOP AT it_pa2001 INTO wa_pa2001.
WRITE:/ wa_pa2001-pernr, wa_pa2001-sprps, wa_pa2001-begda, wa_pa2001-endda.
ENDLOOP.

Thanks Kiran.
But I need to change this field as we need to lock the records, as soon as the employee fills his/her time sheets which will be sent for HR Payroll, later on.
When I am updating directly the field the database table PA2001, its not updating but for table PA2002, only few records are being updated.
Is there any other alternative for this problem?
Pls reply.
Thanks,
Harish

Cascade update of primary key in child tables

Hi,
We have a typical scenario in which the primary key has to propage to the child table into 3 levels. We are getting the no parent key exception if we create new data into the three tables using 3 level master detail relationship and execute commit operation. The following is the structure of the tables.
Parent_table (sno number primary key, name varchar2(100));
Child_table (fk_sno number primary key, name varchar2(100), foreign key (fk_sno) references parent_table(sno));
GrandChild_table (sno number primary key, fk_sno number, name varchar2(100), foreign key (fk_sno) references Child_table(fk_sno));
The requirement is to update fk_sno in child_table and grandchild_table with the trigger generated primary key sno in the parent_table.
The application module is having the following structure
parenttable
|
----------childtable
|
-----------grandchild_table
If we create new records into parent_table and child_table it is working fine when we commit the data. If we create another record into grandchild_table and commit data we are getting the foreign key violation exception. We are using composition in the association to update the modified values to refresh the data.
Is there any problem in the data model to use fk_sno as primary key and foreign key in child_table.
Thanks and Regards,
S R Prasad

Hmm, another example is CSKS, this logic was probably designed already in the 1980s...maybe it was seen beneficial to be able to select the currently valid record by using the primary key only (the first record where DATBI is larger than system date, not possible when DATAB is the key instead).
Maybe there are better explanations. Why do you need to know this, just curious?
Thomas

Updation of Primary Key field in HR Tables (PA2001 and PA2002) - Urgent

Can anyone please tell me how to update a primary key field in HR Tables (PA2001 and PA2002).
I need to update sprps field in both the tables. I used HR_Infotype_Operation function module, but still it is not updating the field.
Pls find the following code snippet for the table PA2001 and let me know if any discrepancies :
TABLES: pa2001.
DATA: it_pa2001 TYPE TABLE OF pa2001,
wa_pa2001 LIKE LINE OF it_pa2001,
DATA: date TYPE d.
date = sy-datum - 100.
SELECT pernr sprps begda endda FROM PA2001 INTO CORRESPONDING FIELDS OF TABLE it_pa2001
WHERE begda BETWEEN date and sy-datum.
WRITE:/.
WRITE:/ 'PA 2001 Records'.
if sy-subrc <> 0.
WRITE:/ 'No Data Exists'.
else.
LOOP AT it_pa2001 INTO wa_pa2001.
WRITE:/ wa_pa2001-pernr, wa_pa2001-sprps, wa_pa2001-begda, wa_pa2001-endda.
ENDLOOP.
endif.
LOOP AT it_pa2001 INTO wa_pa2001.
wa_pa2001-sprps = 'X'.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = '2001'
number = wa_pa2001-pernr
SUBTYPE =
OBJECTID =
LOCKINDICATOR =
VALIDITYEND =
VALIDITYBEGIN =
RECORDNUMBER =
record = wa_pa2001
operation = 'MOD'
TCLAS = 'A'
DIALOG_MODE = '0'
NOCOMMIT =
VIEW_IDENTIFIER =
SECONDARY_RECORD =
IMPORTING
RETURN =
KEY =
ENDLOOP.
if sy-subrc = 0.
write:/ 'SY-subrc is zero'.
write:/ ' Rows modified = ', sy-dbcnt.
else.
write:/ 'No Record(s) updated'.
endif.
commit work.
WRITE: / 'Updated Records in the Internal Table IT_PA2001'.
SELECT pernr sprps begda endda FROM PA2001 INTO CORRESPONDING FIELDS OF TABLE it_pa2001
WHERE begda BETWEEN date AND sy-datum..
LOOP AT it_pa2001 INTO wa_pa2001.
WRITE:/ wa_pa2001-pernr, wa_pa2001-sprps, wa_pa2001-begda, wa_pa2001-endda.
ENDLOOP.

Thanks Kiran.
But I need to change this field as we need to lock the records, as soon as the employee fills his/her time sheets which will be sent for HR Payroll, later on.
When I am updating directly the field the database table PA2001, its not updating but for table PA2002, only few records are being updated.
Is there any other alternative for this problem?
Pls reply.
Thanks,
Harish

Assigning primary key and index for a table

I have a database consisting of only one table with 10 million rows which mostly looks like this:
RECORDDATE                     ID     CLASS     VALUE
24-JAN-12 10.52.47.000000 AM     96     3     0
24-JAN-12 10.52.48.000000 AM     96     10     156
24-JAN-12 10.52.48.000000 AM     96     3     0
24-JAN-12 10.52.48.000000 AM     96     3     0
24-JAN-12 10.52.48.000000 AM     96     3     0
24-JAN-12 10.52.48.000000 AM     96     3     0
24-JAN-12 10.52.48.000000 AM     96     10     156
24-JAN-12 10.52.48.000000 AM     96     3     0
24-JAN-12 10.52.48.000000 AM     96     3     0
24-JAN-12 10.52.48.000000 AM     96     6     38
24-JAN-12 10.53.05.000000 AM     253     16     197
24-JAN-12 10.53.06.000000 AM     98     10     150
24-JAN-12 10.53.06.000000 AM     98     0     0
24-JAN-12 10.53.06.000000 AM     98     4     0
24-JAN-12 10.53.06.000000 AM     98     11     33As you can see there are several entries that look exactly the same. Currently, I don't have primary key or index for any column and have a lot of performance issues. For example this query takes more than 10 seconds to run:
select distinct      ID
from      scdatabase4
where ID < 253
order by 1Since database is not my primary job and have no background of it, I'm really confused about what to do to fix my issues. Could someone please help me in assigning primary key and index if you agree that this is the problem?!

Execute the query below to help decide what column to index:
SELECT COLUMN_NAME, NUM_DISTINCT, NUM_NULLS, NUM_BUCKETS, DENSITY
FROM DBA_TAB_COL_STATISTICS
WHERE TABLE_NAME = 'your_table_name'
ORDER BY COLUMN_NAME;
The important columns are:
1) NUM_DISTINCTS: Indicates the number of distinct values. If this number is very low for a column, it indicates that this column is not a very good candidate for a B-Tree index.
2) NUM_NULL: Indicates the number of null values for each column. A column with few null values is a good candidate for a index
But be aware, this is not a rule, it's just a method to help decide which column will have the most benefit of index creation.

How to define Composite primary key for a Table

Hi ,
I am basically more into Java Programming , with little bit knowledge on Oracle as DataBase .so please excuse for my silly doubts .
Can anybody please tell me how to define a Composite Primary Key on a Table .
Thanks in advance .
Edited by: user672373773 on Sep 25, 2009 8:54 AM

Here is an example right out of the Oracle documentation and the syntax for adding PK since you mention adding a composite PK.
Example creating composite index
http://download.oracle.com/docs/cd/B19306_01/appdev.102/b14251/adfns_indexing.htm#sthref594
Syntax for adding a PK (composite or not)
alter table oooooooo.tttttttt
add constraint tttttttt_PK
primary key (sample_column2,
sample_column1)
using index
tablespace IDXSPC
pctfree 05
initrans 04
maxtrans 08
storage (initial 16k
next 16k
maxextents 32
pctincrease 0);
-- dictionary management with restricted storage, change as desired.
HTH -- Mark D Powell --

How to get the PRIMARY KEY of a table at runtime ???

Hi everybody,
My requirement is to update a z-table at runtime according to the data given ata runtime. So the main difficulties for me is that whenever I tried to update the table based on the data given in UI many rows are getting updated as these fields are not unique. So I think if I can get the PRIMARY KEY along with these given fields then I can update only one row at a time.
So Can anyone suggest me how to get PRIMARY KEY of a table based on the data in UI..??
Any suggestions will be appreciated..
Thanks,
Sekhar

U will get primary keys of transparent tables using FM "REUSE_FIELDCALATLOG_MERGE".
pass tyour table name and u will get fieldcatalog filled. In tht their is a field called "KEY" if it has 'X' then tht field is a primary key of transparent tables & if it has "space" then it is not a primary key...
Or else you can try with 'DDIF_TABT_GET'
Or try this code
PARAMETERS: p_table TYPE tabname OBLIGATORY.
DATA: go_strucdescr   TYPE REF TO cl_abap_structdescr,
      gt_tab_fields   TYPE ddfields.
FIELD-SYMBOLS: <gwa_tab_field> TYPE dfies.
TRY .
*   Get the details of the DDIC table
    go_strucdescr ?= cl_abap_elemdescr=>describe_by_name( p_table ).
CATCH cx_sy_move_cast_error .
    MESSAGE 'Error while casting' TYPE 'S'. RETURN.
ENDTRY.
* Check if input is a DDIC table
CHECK go_strucdescr->is_ddic_type( ) = 'X'.
* Get the details of the table fields
gt_tab_fields = go_strucdescr->get_ddic_field_list( ).
* Display the Key fields of the table
LOOP AT gt_tab_fields ASSIGNING <gwa_tab_field> WHERE keyflag = 'X'.
WRITE: / <gwa_tab_field>-fieldname.
ENDLOOP.

What is the best practice for creating primary key on fact table?

what is the best practice for primary key on fact table?
1. Using composite key
2. Create a surrogate key
3. No primary key
In document, i can only find "From a modeling standpoint, the primary key of the fact table is usually a composite key that is made up of all of its foreign keys."
http://download.oracle.com/docs/cd/E11882_01/server.112/e16579/logical.htm#i1006423
I also found a relevant thread states that primary key on fact table is necessary.
Primary Key on Fact Table.
But, if no business requires the uniqueness of the records and there is no materilized view, do we still need primary key? is there any other bad affect if there is no primary key on fact table? and any benifits from not creating primary key?

Well, natural combination of dimensions connected to the fact would be a natural primary key and it would be composite.
Having an artificial PK might simplify things a bit.
Having no PK leads to a major mess. Fact should represent a business transaction, or some general event. If you're loading data you want to be able to identify the records that are processed. Also without PK if you forget to make an unique key the access to this fact table will be slow. Plus, having no PK will mean that if you want to used different tools, like Data Modeller in Jbuilder or OWB insert / update functionality it won't function, since there's no PK. Defining a PK for every table is a good practice. Not defining PK is asking for a load of problems, from performance to functionality and data quality.
Edited by: Cortanamo on 16.12.2010 07:12

Automatic row processing updating my primary key

Hi all!
In Apex 3.2, I've got an Interactive report with a DML form on a table. My table has a primary key which use a sequence (trigger based). When I created my forms, I specified that I wanted to use an existing trigger as the source type of the primary key.
When I try to create a record, it work. If I try to create a new record and save, my trigger give me an error message because the automatic row processing is trying to update the primary key too. (My trigger on the update specify that the primary key should not be updated).
So my question is : How can I make the automatic row processing update everything but the primary key ? (I noticed that I could have asked APEX to use my SEQUENCE directly instead of the trigger (in the creation Wizard). But I dont know how to change this now that my form is created.)
Is there a source type that I can change in my primary key item ?
Note : My primary key item (id_emp) is protected and hidden. If I display it as "Display only", the update works... But I dont need to see id_emp on my form.

OK,
From your first post, it sounds as though the process is trying to perform an INSERT rather than an UPDATE. It is, therefore, trying to create a new record using a primary key that already exists on the table.
If that is the case, then we need to go through the points along that route:
1 - when you load a record into the page, the primary key page item should be given a value. So, firstly, check the link is populating the correct page item. And then, when the page has loaded, click the Session button on the Developer's toolbar at the bottom of the screen and check that the value is there
2 - when the page loads, one, and only one, page item should have the primary key value. This should be P3_NO_EMPLOYE*. Check other page items to make sure that their source is not NO_EMPLOYE. Again, check with using the Session button to see if the value appears anywhere else on the page
3 - when the page loads, the "SAVE" button should become visible. Check that this is conditional on P3_NO_EMPLOYE being NOT NULL
4 - there should be one, and only one, button that triggers the SAVE action. Check that there are no other buttons that either (A) are called SAVE or (B) trigger the INSERT SQL database action
5 - when the SAVE button is clicked, the "Process Row of..." process should be triggered and, because the button is SAVE and, therefore, sends "SAVE" as the REQUEST value, the process identifies this request as an Update database action. Check that you have Update ticked on the process and that you only have one process that can perform the update
6 - it is possible to change the value of the Request after a button has been clicked, so check that you have no computations or processes that run before the "Process Row of..." process
Andy

Prob with Updation of Primary Key field '' SPRPS '' in PA2001. Plz HELP

Can anyone please tell me how to update a primary key field in HR Tables (PA2001 and PA2002).
I need to update sprps field in both the tables. I used HR_Infotype_Operation function module, but still it is not updating the field.
Pls find the following code snippet for the table PA2001 and let me know if any discrepancies :
TABLES: pa2001.
DATA: it_pa2001 TYPE TABLE OF pa2001,
wa_pa2001 LIKE LINE OF it_pa2001,
DATA: date TYPE d.
date = sy-datum - 100.
SELECT pernr sprps begda endda FROM PA2001 INTO CORRESPONDING FIELDS OF TABLE it_pa2001
WHERE begda BETWEEN date and sy-datum.
WRITE:/.
WRITE:/ 'PA 2001 Records'.
if sy-subrc <> 0.
WRITE:/ 'No Data Exists'.
else.
LOOP AT it_pa2001 INTO wa_pa2001.
WRITE:/ wa_pa2001-pernr, wa_pa2001-sprps, wa_pa2001-begda, wa_pa2001-endda.
ENDLOOP.
endif.
LOOP AT it_pa2001 INTO wa_pa2001.
wa_pa2001-sprps = 'X'.
CALL FUNCTION 'HR_INFOTYPE_OPERATION'
EXPORTING
infty = '2001'
number = wa_pa2001-pernr
SUBTYPE =
OBJECTID =
LOCKINDICATOR =
VALIDITYEND =
VALIDITYBEGIN =
RECORDNUMBER =
record = wa_pa2001
operation = 'MOD'
TCLAS = 'A'
DIALOG_MODE = '0'
NOCOMMIT =
VIEW_IDENTIFIER =
SECONDARY_RECORD =
IMPORTING
RETURN =
KEY =
ENDLOOP.
if sy-subrc = 0.
write:/ 'SY-subrc is zero'.
write:/ ' Rows modified = ', sy-dbcnt.
else.
write:/ 'No Record(s) updated'.
endif.
commit work.
WRITE: / 'Updated Records in the Internal Table IT_PA2001'.
SELECT pernr sprps begda endda FROM PA2001 INTO CORRESPONDING FIELDS OF TABLE it_pa2001
WHERE begda BETWEEN date AND sy-datum..
LOOP AT it_pa2001 INTO wa_pa2001.
WRITE:/ wa_pa2001-pernr, wa_pa2001-sprps, wa_pa2001-begda, wa_pa2001-endda.
ENDLOOP.

Thanks Kiran.
But I need to change this field as we need to lock the records, as soon as the employee fills his/her time sheets which will be sent for HR Payroll, later on.
When I am updating directly the field the database table PA2001, its not updating but for table PA2002, only few records are being updated.
Is there any other alternative for this problem?
Pls reply.
Thanks,
Harish

Update a primary key and Fk

Hello
I have to update a primary key (PK) which is referenced by many foreign keys (FK).
The primary key columns cannot be updated as this would orphan the dependant tables,
and the dependant tables cannot be updated prior to the parent table as this would also make them orphans.
I think this problem was solved by disabling the foreign key constraints or deleting the original records and recreating them.
Since neither of these solutions is particularly satisfactory for me I read about 'deferred constraints'.
My question is:
Can I use(modify to) 'INITIALLY DEFERRED' keyword on constraints's table already created with The default, INITIALLY IMMEDIATE ,
that is, update my primary key and foreign keys, and then re-set to
'INITIALLY IMMEDIATE'? Or another trick exists ?
Thanks in advance for your attention

It is very popular the idea that the updates on primary key columns are a very bad thing.
Oracle supports this idea and that's why they don't give the "on update cascade" clause on foreign keys.
So in this case I suggest you to define a master table like this.
create table master_table (
     key_id number primary key,
     your_primary_key varchar2 not null unique
/Then you must use that key_id column as foreign key in place of your original primary key. In this way don't even need to update referencing rows when updating the original primary key because the foreign key value doesn't change and everything is always fine as before.
So instead to lose time implementing some strange sort of cascade triggers plain to do something like this on your schema.
insert into master_table (id_key,primary_key) (
     select rownum,primary_key
     from your_main_table
alter table your_main_table add (
     id_key number,
update your_main_table a
set id_key = (
          select b.id_key
          from master_table
          where b.primary_key=a.primary_key
     Drops foreign keys
alter table your_main_table drop primary key cascade
alter table your_main_table add constraint pk
     primary key(id_key)
alter table your_main_table add constraint fk
     foreign key(id_key) references master_table
alter table your_main_table drop (
     your_primary_key
alter table a_referencing_table add (
     id_key number,
update a_referencing_table a
set id_key = (
          select b.id_key
          from master_table
          where b.primary_key=a.primary_key
alter table a_referencing_table add constraint fk_2
     foreign key(id_key) references master_table
alter table a_referencing_table drop (
     your_primary_key
/If you have many objects referencing those tables I suggest you to rename the tables and to create views with the original name of the renamed tables that show data as it was before with a join on master_table. in this way you don't need to change the code of the application referencing them but you just need to recompile invalidated objects.
Bye Alessandro

PRIMARY KEY PARTITIONED INDEXES 생성방법 (ORA-2429, ORA-1408)

제품 : ORACLE SERVER
작성날짜 : 2004-08-13
PRIMARY KEY PARTITIONED INDEXES 생성방법 (ORA-2429, ORA-1408)
============================================================
PURPOSE
primary key partitioned indexes 를 생성하는 방법을 알아 봅니다.
SCOPE
Oracle Partitioning Option은 8~10g Standard Edition에서는 지원하지
않는다.
Example:
SQL> -- 먼저 partitioned table TEST_A 를 생성합니다.
SQL>
SQL> CREATE TABLE test_a (col1 number, col2 number, col3 varchar2(20))
2 PARTITION BY RANGE (col1, col2)
3 (partition part_test_a_1 values less than (10, 100),
4 partition part_test_a_2 values less than (20, 200),
5 partition part_test_a_3 values less than (30, 300),
6 partition part_test_a_4 values less than (40, 400));
Table created.
SQL> -- partitioned table TEST_B 를 생성합니다.
SQL>
SQL> CREATE TABLE test_b (col1 number, col2 number, col3 varchar2(20))
2 PARTITION BY RANGE (col1, col2)
3 (partition part_test_b_1 values less than (10, 100),
4 partition part_test_b_2 values less than (20, 200),
5 partition part_test_b_3 values less than (30, 300),
6 partition part_test_b_4 values less than (40, 400));
Table created.
SQL> -- TEST_A 테이블에
SQL> -- non-unique local partitioned index, IX_TEST_A 를 생성합니다.
SQL>
SQL> CREATE INDEX ix_test_a ON test_a(col1, col2)
2 LOCAL
3 (partition ix_test_a_1,
4 partition ix_test_a_2,
5 partition ix_test_a_3,
6 partition ix_test_a_4);
Index created.
SQL> -- TEST_B 테이블에
SQL> -- unique global partitioned index, IX_TEST_B 를 생성합니다.
SQL>
SQL> CREATE UNIQUE INDEX ix_test_b1 ON test_b(col1, col2)
2 GLOBAL PARTITION BY RANGE (col1, col2)
3 (partition ix_test_b1_1 values less than (20, 200),
4 partition ix_test_b1_2 values less than (maxvalue, maxvalue));
Index created.
SQL> -- TEST_A 테이블에 rimary key constraint (PK_TEST_A) 를 추가 합니다.
SQL>
SQL> ALTER TABLE test_a ADD CONSTRAINT pk_test_a
2 PRIMARY KEY (col2, col1);
Table altered.
SQL> -- index IX_TEST_A 를 drop 하려고 하면 다음 에러가 발생합니다.
SQL>
SQL> DROP INDEX ix_test_a;
drop index ix_test_a
ERROR at line 1:
ORA-02429: cannot drop index used for enforcement of unique/primary key
SQL> -- TEST_B 테이블에 partition IX_TEST_B1 에서 사용된 같은 columns 들을 사용해서
SQL> -- 새로운 두번째 index (IX_TEST_B2) 를 생성하려고 하면
SQL> -- 다음 에러가 발생합니다.
SQL>
SQL> CREATE INDEX ix_test_b2 ON test_b(col1, col2)
2 LOCAL;
create index ix_test_b2 on test_b(col1, col2)
ERROR at line 1:
ORA-01408: such column list already indexed
SQL> -- TEST_B 테이블에 primary key constraint (PK_TEST_B) 를 추가 합니다.
SQL>
SQL> ALTER TABLE test_b ADD CONSTRAINT pk_test_b
2 PRIMARY KEY (col1, col2);
Table altered.
SQL> -- index IX_TEST_B1 를 drop 하려고 하면 다음 에러가 발생합니다.
SQL>
SQL> DROP INDEX ix_test_b1;
drop index ix_test_b1
ERROR at line 1:
ORA-02429: cannot drop index used for enforcement of unique/primary key
SQL> -- indexes 들과 각 indexes 이 걸려있는 tables 의 목록입니다.
SQL>
SQL> SELECT index_name, partition_name, status
2 FROM user_ind_partitions
3 ORDER BY index_name, partition_name;
INDEX_NAME PARTITION_NAME STATUS
IX_TEST_A IX_TEST_A_1 USABLE
IX_TEST_A IX_TEST_A_2 USABLE
IX_TEST_A IX_TEST_A_3 USABLE
IX_TEST_A IX_TEST_A_4 USABLE
IX_TEST_B1 IX_TEST_B1_1 USABLE
IX_TEST_B1 IX_TEST_B1_2 USABLE
6 rows selected.
SQL> -- TEST_A 테이블에서 primary key constraint 를 drop 합니다.
SQL>
SQL> ALTER TABLE test_a DROP CONSTRAINT pk_test_a;
Table altered.
SQL> -- TEST_B 테이블에서 primary key constraint 를 drop 합니다.
SQL>
SQL> ALTER TABLE test_b DROP CONSTRAINT pk_test_b;
Table altered.
SQL> -- indexes 들과 각 indexes 이 걸려있는 tables 의 목록을 다시 봅니다.
SQL> -- 여기서 주의해서 보아야 할 것은 non-unique local partitioned index (IX_TEST_A)
SQL> -- 은 drop 되지 않고 USABLE 상태로 남아 있다는 것입니다.
SQL> -- 이렇게 되는 이유는 index (IX_TEST_A) 가 non-unique 이기 때문입니다.
SQL> -- 반면 unique global partitioned index (IX_TEST_B) 은 drop 되었습니다.
SQL>
SQL> SELECT index_name, partition_name, status
2 FROM user_ind_partitions
3 ORDER BY index_name, partition_name;
INDEX_NAME PARTITION_NAME STATUS
IX_TEST_A IX_TEST_A_1 USABLE
IX_TEST_A IX_TEST_A_2 USABLE
IX_TEST_A IX_TEST_A_3 USABLE
IX_TEST_A IX_TEST_A_4 USABLE
만일 index 가 primary key 에 정의되어 있는 columns 들과 같은 columns
을 사용해서 만들어 졌다면 primary key 는 그 underlying index 를 사용합니다.
이것은 index 가 unique 이건 non-unique 이건 또는 global 이건 local partioned index
이건 관계없이 적용됩니다.
위의 예제에서 primary key 가 non-unique index 위에 생성되었다는 것을
주의해 보시기 바랍니다. 이렇게 되는 이유는 index 안의 값들이 사실
모두 unique 하기 때문입니다. 그렇지 않을 경우 다음 에러가 발생하게 됩니다.
"ORA-02437: cannot enable (STEELY.PK_TEST_B) - primary key violated."
2개의 indexes 가 같은 순서의 같은 columns 을 사용해서 만들어 질 수는 없습니다.
위의 예제에서 TEST_B 테이블에 두번째 index (IX_TEST_B2) 를 만들려고
했을때 다음에러가 발생하는것을 확인할 수 있었습니다.
"ORA-01408: such column list already indexed."
하지만 columns 들의 순서를 바꾼다면 같은 columns 들을 사용하더라도
추가적으로 indexes 를 생성할 수 있습니다.
index (IX_TEST_A) 와 primary key (PK_TEST_A) 에 정의된 column 순서는
반대로 되어 있습니다. 그러나 primary key 는 IX_TEST_A 를 underlying index
로 사용하고 있습니다.
테이블에서 primary key constraint 가 drop 되었을때
만일 index 가 UNIQUE index 로 생성되었다면 대응하는 index 또한 drop 됩니다.
이 현상은 LOCAL 또는 GLOBAL partitioned indexes 모두에 적용됩니다.
partitioning 을 최대한 활용하기 위해서는 partitioned tables/indexes
를 생성할 때에 STORAGE clause 를 반드시 사용해야 합니다.
Reference Documents
<Note:74224.1>

First, thanks for posting the code that lets us reproduce your test. That is essential for issues like this.
Because the primary key is global you will not be able to use
INCLUDING INDEXES
WITH VALIDATION;And you will need to add the primary key to the temp table
ALTER TABLE DEMO_INTERVAL_DATA_LOAD_Y ADD CONSTRAINT IDX_DEMO_ROLL_Y PRIMARY KEY (ROLL_NUM);The the exchange will work. You will need to rebuild the primary key after the exchange.

How add new field as primary key for existing table

Hi,
There is table with name REVIEWER_REUSE_EFFORT and the table has 8000 rows in it.
Now the enhacement i must do on this table is there is no primary key on this table. so i must create a ID also add values to this table of ID
Table structure is like this
Create table REVIEWER_REUSE_EFFORT
PRO_ID number,
POBJ_ID number,
TASK_ID number,
POTENTIAL_EFFORT number,
COMMENTS varchar2(1200),
CREATED_BY varchar2(100),
CREATION_DATE sysdate
UPDATED_BY varchar2(1200),
UPDATED_DATE sysdate
Please suggest me how to add values in that 8000 rows
Thanks
Sudhir

Hi,
If you want to add a new column and update the new column with sequence of number
alter table REVIEWER_REUSE_EFFORT add (ID number);
update REVIEWER_REUSE_EFFORT set ID=rownum;Regards,
Prazy
Edited by: Prazy on Jun 21, 2010 3:13 PM

Is it possible to create many primary key for a table?

hello sir/mam.
i am selva, i am new to abap,
is it possible to create many primary key for a table?
please guide me.

Hi Selva,
Many Primary Keys = Composite Key.
i.e some set of columns will enable you to identify a unique row from a set of rows in the table.
This can be achieved by checking the primary key check box in se11.
Hope it helps.
Regards,
Maheswaran.B
Message was edited by: Maheswaran B

How can I obtain the primary key of a table for an entity relation?

hello everybody
I am doing a consultation to a table in my data base, good this table has alone two fields, the first one is the code or pk and the second one is the description, to be presisos they are names of city and code.
From the beginning!!: This method this one in another class that is a Dialog that is going to call to the class SelecPlace ();
SelecPlace sl = new SelecPlace();
public void capturarLugar(){ // Simple void method in the mentioned class
        String place = txtProcedencia.getText() ; // a JTextField
        sl.executeStatement(place) ;
    }ok, now we see part of the code of the class SelectPlace
public class SelecPlace extends AbstractTableModel{
    Connection con = null;
    Statement sentencia = null ;
    ResultSet rs = null;
    ResultSetMetaData rsmd = null ;
    String[] nameColum = {} ;
    Vector datos = new Vector() ;
    public SelecPlace() { }
    public void executeStatement(String query){
      try{
         con = DBManager.getConnection() ;
         sentencia = con.createStatement(rs.TYPE_SCROLL_INSENSITIVE,
                                                                      rs.CONCUR_UPDATABLE) ;
         String sql = "select * from Place where descripcion like %"+query+"%'";
          rs = sentencia.executeQuery(sql) ;
          rsmd = rs.getMetaData();
          int nroColumnas = rsmd.getColumnCount() ;
          nameColum = new String[nroColumnas] ;
          //obtengo los nombres de columnas en cache
           for(int colum = 0; colum < nroColumnas; columna++){
                nameColum[colum] = rsmd.getColumnLabel(columna + 1) ;
           datos = new Vector();
            while(rs.next()){
                Vector newRow = new Vector();
                for(int i = 0; i < getColumnCount(); i++){
                newRow.addElement(rs.getObject("place_ID"));
                newRow.addElement(rs.getObject("description"));
                datos.addElement(nuevaFila);
            fireTableChanged(null);
        }catch(SQLException e){
            System.err.println(e);
            e.printStackTrace(System.err);
            System.out.println("error in statement");
        }catch(ClassNotFoundException cnfe){
            System.err.println(cnfe);
    }Ok, this code me works and I obtain in this case the field description of the table Place
Now my question is, how can I obtain the primary field of my table?
I need this value of this field that in the base of information in a bigint, and to take it to the first class before mentioned, for that I am working with a data base related

Certain duffymo and everyone!!, good I give you my scheme:
And generalizing my question, I want to obtain the value of the primary key of a table in the database, I obtain more values of the same row, but I need the primary key, and you see one with the primary key I want to turn a Long and it to insert with code java in foreign clave in another table of the database
Good of this form I believe that it would not be breaking the integrity relacional of the tables

Update on primary key in indexed table

Similar Messages

Maybe you are looking for