Updating primary key problem

Here is my scenario:
I have inserted 5 rows in mobile client with primary key 1, 2, 3, 4,5
Then deleted 3rd row and updated the primary key for 4th and 5th row to make the primary key sequential.
But when I sync, I get conflict error with DML Operation update
Does oracle lite support primary key update or primary key reshuffle?
Thanks

Hi,
can you apply this one-off patch 7337669 Oracle Database Lite: Patch
CONSOLIDATED ONEOFF FOR CUSTOMER BUGS TILL AUG 19 2008 10.3.0.1.0 19-AUG-2008
and tell me if you are still able to reproduce this behavior?
The Patch is available on metakink.oracle.com
Regards.
Marc

Similar Messages

Update primary key in replication environment.

Hello all,
I would appreciate, if you could answer for my question.
I am using oracle9i advanced asynchronous replication. What would be the issue if we update the primary key. Is it going to create any problem ?. What is the drawback on updating Primary key.
Thanks
Govind

Are you using DDL propagartion?
You should not have any problems if you have unconditional supplement logging for all columns.
But, probably it is good idea to do it in this way:
1 stop capture
2 change session tag
3. change table defenition on both sides
4. enable capture.
5. perform capture checkpoint right after step 4.
Regards,
Sergey

Update primary key/delete and reinsert records

Hi, I have been told to update some fields. The database is new to me, and now I see the field is the primary key (and it has child tables with that as foreign key). The person who told me isn't reachable until next week...
...wasn't a bad idea to update pk's? I see it's possible, deferring constraints...
update primary key
Re: Update Primary Key
...but it's better/safer the script deletes and later re-insert the records, right?
Thanks

Always is better be able to undo any change .
But ¡, why would you update pk's? it's possible but you colud find few problems like:
- many levels of foreign keys exists.
- not validate pk
Look at:
Re: Novalidate primary key

Replication for Data on DEV and QA - bad idea - primary key problem now

I goofed. I tried to use replication to keep the data on my dev machine up to date with the live server. Now when I try to work on the database, adding new stuff, it fails. It says there is a primary key problem every time I try to add
a new item to a table with my program. I should have realized this would happen! Now, even though I've removed the replication, I'm having the problem. Can anyone help me get my database functional again :/ Or should I resort to a database
restore. Thanks!

So you have an IDENTITY column in your table? Run a
DBCC CHECKIDENT (Transact-SQL) command with option RESEED to fix the current identity value to see if it works then.
Olaf Helper
[ Blog] [ Xing] [ MVP]

Primary key problem - Urgent! PLEASE, HELP!

Hi all,
I'm new here, and I have a stupid problem, I think. If someone could help me, I'll be grateful.
I have to build a very simple JSP application using a few database tables, providing the base functionality: insert, update, delete, search.
I'm using Oracle 8.1.7, and JDeveloper 9.0.3
One table looks like that:
CREATE TABLE TEST (
     sPrimaryKey varchar2(30) not null,
     sField varchar2(100)
ALTER TABLE TEST
ADD ( CONSTRAINT test_id_pk
          PRIMARY KEY (sPrimaryKey)
I'm using a sequence for generating primary key...
CREATE SEQUENCE test_seq
START WITH 100
INCREMENT BY 1
NOCACHE
NOCYCLE;
... and a trigger before insert for seting the new value of the primary key.
CREATE OR REPLACE TRIGGER BI_TEST
BEFORE INSERT ON TEST
FOR EACH ROW
DECLARE
     new_id integer;
BEGIN
     select test_seq.nextval into new_id from dual;
     :new.sPrimaryKey := 'AAA' || new_id;
END;
I have created a BC4J. How can I insert a new row into that table without providing the primary key, by hand, and let the trigger and sequence do that?
Thank you!
Razvan

In the attribute settings editor for the Attribute TestIdPk in Entity Test:
select Updateable Never
deselect Mandatory
select Refresh After Update & Refresh After Insert
HTH.
Thanks, George

Who can I update primary key field in master block

Hi,
I want to update the primary key field in master block when there are some records are present in detail block, when I edit the primary key filed there is an error FRM-40509 unable to update record. The primary key is also referred by the detail table.
So kindly give me the solution who can I update the primary key in master block when there is child records exists in detail block?.
Best regard,
shahzad

pls tell us a little more about, why you want to update a PK in a master block.
I haven't done that my whole time. Maybe you need something different.
The problem is, that your child-data references to the master-pk, so there is the point you have to go deep into the codings. But better don't do it. Tell us first why. I think there are other solutions for that.
try it
Gerd

Updating primary key with jdbc

Trying to update a primary key with:
public static void updateTAXID(String coid,String accountnumber,String oldTAXID,String fundname,String newTAXID){ Properties props = TradeHelper.loadProperties(); Connection conn = null; PreparedStatement st = null; String sql ="update FinancialAccount set taxid=? " + "where dealernumber=? and " + "taxid=? and " + "fundname=? and " + "accountnumber=?"; try{ Class.forName(props.getProperty("driver")); conn = DriverManager.getConnection(props.getProperty("brokerageurl"), props.getProperty("user"),props.getProperty("password")); st = conn.prepareStatement(sql); st.setString(1, newTAXID); st.setString(2, coid); st.setString(3, oldTAXID); st.setString(4, fundname); st.setString(5, accountnumber); st.executeUpdate(); System.out.println("Update: new tx:"+newTAXID+":"+"Ol tx: "+oldTAXID+" act:"+accountnumber); conn.close(); st.close(); }catch(Exception e){ e.printStackTrace(); } }
I keep getting this error:
com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException: Duplicate entry '02673025561-QA-SLFCA-' for key 'PRIMARY' at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1011) at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491) at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423) at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936) at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060) at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2542) at com.mysql.jdbc.PreparedStatement.exe
Am I not able to update a single field of a composit key with jdbc? Whay is my update failing telling that there is a duplicate when I am trying to update?

iketurner wrote:
I keep getting this error:
com.mysql.jdbc.exceptions.MySQLIntegrityConstraintViolationException: Duplicate entry '02673025561-QA-SLFCA-' for key 'PRIMARY'
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1011)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2542)
at com.mysql.jdbc.PreparedStatement.exeAm I not able to update a single field of a composit key with jdbc? Whay is my update failing telling that there is a duplicate when I am trying to update?If you take the error message at its word then the problem is not that you are not permitted to update a primary key but that the values you are trying to use is already in use.
I'll leave it you DBA and/or Data Modeler/Architech to decide if it is a good idea to update the value or not.

Update primary key

Hi
I am using weblogic 7.0 and ejb 2.0
I have a requirement where i would want to update my primary key. If i understand right , In ejb you are not allowed to update one of the primary key column of composite primary key.
Now if i have to update this what are the work arounds. Aslo say if i update that row through stored proc, will my ejb state in cache be in sync with latest data. Is ejb load called for sure beofre any method is called on bean.
Please give me some inputs on this
Thanks

Your problem lies within your database (datasource)structure. You need to have two primary keys for that particular entity. The first primay key is internal meaning it is the true key for any specific record in the table. The second "primary key" is external meaning it is not truely a primary key with regards to the formal contstraints of your database. Instead, this is the key your users will see. It is the responsibilty of the application layer to ensure that the external id is unique. This way, you always have a lasting primary key (the internal key), yet your users can change their "primary key" whenever they like.
As an example, I'm writing a J2EE application that provides our clients with a unique ID to access their records. My table definition would look something like:
CREATE TABLE Client (
clientId BIGINT AUTO_INCREMENT NOT NULL,
externalClientId VARCHAR(15) UNIQUE NOT NULL,
... another field,
... another field,
CONSTRAINT pk_foo PRIMARY KEY (clientId)
The unique constraint isn't really necessary because the application layer should check for this, but it's a good safety precaution.
On the application side, you would only expose the 'externalClientId' to the clients. This might force you to use BMP, but it keeps the user from ever changing the true Id and is fairly clean.
Hope this helps.

Primary Key problem in 11g - Known issue 6894412

Hi Everyone:
We are on JDeveloper 11.1.1.4, and JHeadstart 11.1.1.2.46. This thread originally started on the JHeadstart forum and can be seen at: Problem with LOV's in 11g
We are converting our 10g application to 11g. We have an established Oracle database that does not use pre-populated primary keys that are sequence number. Our database has composite keys and the integrity of those composite keys are established by foreign key constraints to edit tables. This approach has worked extremely well for us for over a decade, the logic of the database has been designed so that the database protects itself through the elimination of cascade deletes where necessary, and cascade deletes as the business logic dictates. This will not be changing.
In the database tables in which the 10g application has been displayed in the table format, after conversion to 11g, the LOV pop-ups are not working unless the SAVE button (or refresh of the browser) has been pressed. The first LOV pop-up will work, but as soon as you select a value from it, the next LOV pop-ups will not execute until the SAVE or REFRESH is done. This is only in table format. If the display format is form, our primary key LOV's work fine. In 10g, this functionality worked fine as long as we didn't use an "ADD ROW" button on a table format. The Add Row button caused the primary key values to be returned to the application, but not be displayed on the screen. A refresh would then show them.
From the initial investigation in the JHeadstart forum, I realize that we are hitting the "Primary Keys from Model" 6894412 problem that is listed in the 11.1.1.4 Release Notes. We have spent many, many hours establishing a re-usable .jar file of all of the entities of this very large database as suggested by JDeveloper Best Practises (http://download.oracle.com/docs/cd/B31017_01/web.1013/b25947/bcadvgen007.htm). This has worked very well for us in 10g - define all the entity specifics in one place, once, then every application can re-use them. Productivity at its finest. Therefore, we cannot make fake columns in our database in order to fix this "limitation" in 11g. We have many complex parent/child/child tables to put into our application which will not work unless our entities have the primary keys properly defined. I have tried to implement the workaround that was found in the release notes, but have been unable to get it to work.
I have created a testcase with the HRSchema by adding a table to that Schema that I can provide the SQL commands for, but I do not know who in Oracle support to send it to. Could someone please provide me with the information on who to contact. I have, I believe, taken all the steps as established in the release notes for this problem and have clearly documented the changes in the .jsff page, but the problem still exists. Clearly, I am doing something wrong, or need more information.
Thank you in advance
Mary
UofW

Frank:
I thank you for your reply.
I have been working on the JHeadstart forums for so long, I actually forgot how to submit things to Metalink, and now that I have done it again...SR #3-3101357281 for this issue....I realize why I blocked out using Metalink from my memory.
It took me an incredible amount of time to fill that SR in, then after completing everything, I was sent a request by the person assigned to the SR to repeat the instructions of how to run my testcase. I had already filled out all of the instructions on how to run the testcase in the "Notes to Oracle" section of the upload step. Almost every time I send something to Metalink, I have to repeat things. It seems as though they aren't read fully and any reason at all is used to send them back to the client.
My dealings with Metalink have been very, very frustrating. My colleagues share this sentiment.
Mary
UofW

CMP with Auto-increment Primary Key problem

I'm trying to set a column as IDENTITY in PointBase and have the app server utilize this in the CMP beans. I followed the instructions from the tutorial:
- In the deployment descriptor, the primary key class is defined as a java.lang.Object. The primary key field is not specified.
- In the home interface, the argument of the findByPrimaryKey method must be java.lang.Object.
- In the entity bean class, the return type of the ejbCreate method must be a java.lang.Object.
Below is (a fragment of) my deployment descriptor:
<?xml version="1.0" encoding="UTF-8"?>
<!DOCTYPE ejb-jar PUBLIC "-//Sun Microsystems, Inc.//DTD Enterprise JavaBeans 2.0//EN" "http://java.sun.com/dtd/ejb-jar_2_0.dtd">
<ejb-jar>
<display-name>CMPModule</display-name>
<enterprise-beans>
<entity>
<display-name>DocState</display-name>
<ejb-name>DocState</ejb-name>
<home>com.sun.itstar.j2ee.projectdocmgt.ejb.DocStateHome</home>
<remote>com.sun.itstar.j2ee.projectdocmgt.ejb.DocState</remote>
<local-home>com.sun.itstar.j2ee.projectdocmgt.ejb.LocalDocStateHome</local-home>
<local>com.sun.itstar.j2ee.projectdocmgt.ejb.LocalDocState</local>
<ejb-class>com.sun.itstar.j2ee.projectdocmgt.ejb.DocStateBean</ejb-class>
<persistence-type>Container</persistence-type>
<prim-key-class>java.lang.Object</prim-key-class>
<reentrant>False</reentrant>
<abstract-schema-name>DocState</abstract-schema-name>
<cmp-field>
<field-name>name</field-name>
</cmp-field>
<cmp-field>
<field-name>description</field-name>
</cmp-field>
<cmp-field>
<field-name>color</field-name>
</cmp-field>
</entity>
In the admin-serv/logs directory I get the follow message (bad place for the logs, took me a while to find where it was putting it!):
[24/Sep/2002:16:33:57] WARNING ( 4165): Validation error in bean DocumentType: Warning: All primary key columns in primary table DOCUMENT_TYPE of the bean corresponding to the generated class com.sun.itstar.j2ee.projectdocmgt.ejb.DocumentTypeBean_387898907_JDOState must be mapped to key fields.
Map the following primary key columns to key fields: DOCUMENT_TYPE.ID. If you already have fields mapped to these columns, verify that they are key fields.

Great! This worked. Here are some clear steps:
1. delete the field from the CMP
2. delete any business methods that you might have for the field
3. go to the properties of the bean, find the primary key property. Set the property to Unkown Primey Key Class (java.lang.Object)
Now there is a bigger problem. CMR fields. In ejbPostCreate() the bean gets its own pk and looks up other related beans. Now that I have removed the accessor to the pk field (and the pk field from the bean), how do I lookup the relationships?
I need some method that I can call from within ejbPostCreate() that will return the primary key...
I tried adding the field back in but not as the primary key. That generated an exception that said you cannot do that. If the field is the pk it must be marked as the pk.
Any ideas?

Tabular Form Page - Insert and Update Primary Key

Hi -
I am creating a Tabular Form page which will display 2 columns:
CODE (Text Field), DESCRIPTION(Field)
The *'CODE'* is a primary key to the table/view and *'DESCRIPTION'* is the corresponding detail information for the *'CODE'*.
I am trying to create an updateable report on this page which will show these columns and when a user wants to add a new row,they should be able to add a new row with CODE='somecode' and DESCRIPTION='description' but shouldn't be able to update (but should be displayed) the *'CODE'* value once inserted into the table or view.
Is there a way to do that? Please share your expertise.
Thanks,
-Seenu

I't a bit unclear what you want.
In your first post it seems that you don't want the user to change the PK.
In your second post the user can change the PK, but you get a db error.
Anyway, I guess you don't want the user to change the PK.
I have a few support tables, which are the source for some LOV's.
For those I also add records with a manual assigned PK, rather then via a sequence, just to improve consistency across applications.
The data is protected by foreign keys to the main tables.
You could further add a trigger to your table which throws an error the moment it detects a change on your PK.

How to update primary key column

Hi,
Can you suggest me best workaround/algorithm for below task:
(Oracle 10g, Solaris OS.)
Situation:
Table P has primary key column "Code", child tables F1, F2, ..., F15 reference with foreign key column "P_Code" column "P.Code", and we don't know which of the child tables has data for particular "P.Code" value.
Task:
Change "P.Code" value from 100 to 200. So that result would be that record P[Code = 100] should be updated as:
update P set
Code = 200
where Code = 100;And child tables column "P_Code" should be updated as:
update F1, F2, .., F15 set
P_code = 200
where P_code = 100;The best solution would be that one very easily can repeat that task.
Edited by: CharlesRoos on 28.12.2010 12:10

If you are looking for reusable and repetitive solution, then may be...
SQL> CREATE TABLE p (p_code NUMBER PRIMARY KEY);
Table created.
SQL> INSERT INTO p VALUES(100);
1 row created.
SQL> INSERT INTO p VALUES(300);
1 row created.
SQL> INSERT INTO p VALUES(500);
1 row created.
SQL> commit;
Commit complete.
SQL> CREATE TABLE F1 (p_code NUMBER REFERENCES p(p_code));
Table created.
SQL> CREATE TABLE F2 (p_code NUMBER REFERENCES p(p_code));
Table created.
SQL> CREATE TABLE F3 (p_code NUMBER REFERENCES p(p_code));
Table created.
SQL> INSERT INTO F1 VALUES(100);
1 row created.
SQL> INSERT INTO F3 VALUES(100);
1 row created.
SQL> INSERT INTO F2 VALUES(500);
1 row created.
SQL> commit;
Commit complete.
SQL> CREATE OR REPLACE PROCEDURE update_child_parent(pi_p_code_old NUMBER,
2                                                  pi_p_code_new NUMBER) IS
3    CURSOR table_to_update IS
4      SELECT table_name,
5             to_number(extractvalue(xmltype(DBMS_XMLGEN.getxml('SELECT count(*) c FROM ' ||
6                                                               table_name ||
7                                                               ' WHERE p_code=' ||
8                                                               pi_p_code_old)),
9                                    '/ROWSET/ROW/C')) cnt
10        FROM user_tables
11       WHERE table_name IN ('F1', 'F2', 'F3');
12
13 BEGIN
14    EXECUTE IMMEDIATE 'ALTER TABLE p DISABLE PRIMARY KEY CASCADE';
15    UPDATE p SET p_code = pi_p_code_new WHERE p_code = pi_p_code_old;
16    FOR i IN table_to_update LOOP
17      IF i.cnt > 0 THEN
18        EXECUTE IMMEDIATE 'UPDATE ' || i.table_name || ' SET p_code=' ||
19                          pi_p_code_new || ' WHERE p_code=' || pi_p_code_old;
20      END IF;
21    END LOOP;
22    EXECUTE IMMEDIATE 'ALTER TABLE p ENABLE VALIDATE PRIMARY KEY';
23 END update_child_parent;
24 /
Procedure created.
SQL> EXECUTE update_child_parent(100,200);
PL/SQL procedure successfully completed.
SQL> SELECT * FROM p;
    P_CODE
       200
       300
       500
SQL> SELECT * FROM F1;
    P_CODE
       200
SQL> SELECT * FROM F2;
    P_CODE
       500
SQL> SELECT * FROM F3;
    P_CODE
       200
SQL> INSERT INTO p VALUES(300);
INSERT INTO p VALUES(300)
ERROR at line 1:
ORA-00001: unique constraint (HR.SYS_C005931) violated
SQL> EXECUTE update_child_parent(500,900);
PL/SQL procedure successfully completed.
SQL> SELECT * FROM p;
    P_CODE
       200
       300
       900
SQL> SELECT * FROM F2;
    P_CODE
       900
SQL>

Primary key problem using with oc4j

Hi everyone
I have deployed my entity bean in the oc4j container without any problem.But when I use the search->primary key in the console,no results display.
detail:
Step1I open the oc4j console by typing java -jar orion.jar -console
the oc4j container is successfully built
and in the left part of my console I see my entity bean
step2 I click my entity bean and in the right of the console in the search->primary key I type the a number which exists in my table in the database.
but no results display.
the following is my datasource-file anf orion-ejb-jar file
data-sources.xml
<?xml version="1.0"?>
<!DOCTYPE data-sources PUBLIC "-//Evermind//- Data-sources configuration" "http://xmlns.oracle.com/ias/dtds/data-sources.dtd">
<data-sources>
     <data-source
          class="com.evermind.sql.DriverManagerDataSource"
          name="jdbc/OracleDSCore"
          location="jdbc/OracleDSCore"
          pooled-location="jdbc/OracleDSPooled"
          xa-location="jdbc/xa/OracleDSXA"
          connection-driver="oracle.jdbc.driver.OracleDriver"
          username="SCOTT"
          password="TIGER"
          url="jdbc:oracle:thin:@localhost:1521:b2b"
     />
</data-sources>
orion-ejb-jar.xml
<?xml version = '1.0' encoding = 'GBK'?>
<!DOCTYPE orion-ejb-jar PUBLIC "-//Evermind//DTD Enterprise JavaBeans 1.1 runtime//EN" "http://xmlns.oracle.com/ias/dtds/orion-ejb-jar.dtd">
<orion-ejb-jar>
<enterprise-beans>
<entity-deployment name="EMP" data-source="jdbc/OracleDSCore" table="EMP" >
<primkey-mapping>
<cmp-field-mapping>
<fields>
<cmp-field-mapping name="EMPNO"
persistence-name="EMPNO" persistence-type="VARCHAR2(4)"/>
</fields>
</cmp-field-mapping>
</primkey-mapping>
</entity-deployment>
</enterprise-beans>
<assembly-descriptor>
<default-method-access>
<security-role-mapping name="<default-ejb-caller-role>" impliesAll="true"/>
</default-method-access>
</assembly-descriptor>
</orion-ejb-jar>
Any answer is welcome. Thankou in advance!

Fernando,
I see you suffer a lot with ADF...write me at [email protected] and letÂ´s keep in touch.
Maybe we can do a Brazilian list for JDev/ADF.
Regards,
Marcelo Alcantara

Update primary key thats also a foreign key in another table

Hi Developers,
I need to update the primary key for a record but it's also the foreign key in another table.
Example,
Table 1 Details
Name : Parent_Table
Columns : ID, Name, Age
Primary Key : ID
Table 2 Details
Name : Child_Table
Columns : ID, Parent_ID, Name, Age
Primary Key : ID
Foreign Key : Parent_ID (Primary Key in Parent_Table)
Parent_Table
ID Name Age
1001 Sam 26
1002 George 25
Child_Table
ID Parent_ID Name Age
1010 1001 Sam 26
1020 1002 George 25
Now I want to update ID (1001) in Parent_table as 2001 and also, I want to update Parent_ID (1001) in Child_Table as 2001.
How we will write the java code to update these columns.
Thanks in advance.

dcminter wrote:
If you're looking at changing the primary keys in your data then there's probably something wrong with your data structure.Depends how you feel about business primary keys versus surrogates. Personally I prefer the latter so I'm with you in theory. In practice, however, a DB that uses a business PK may well find that it's a legitimate use case to change the key value (but then that's why I like surrogates in the first place!)Primary keys should not have meaning.

Updating primary key

HI ,
I want to update the primary (DATBI) key of SAP table a017 with new value. I am using update statement and giving all the primary keys for identifying the record, but lasting in short dump.
any pointers on how this can be done?
Regards
saurabh.

hi
chk this
<b>You cannot change the primary key when you UPDATE a table for which a synchronous matchcode is defined.</b>
another eason might b the CLIENT SPECIFIC condition needed
UPDATE sflight <b>CLIENT SPECIFIED</b>
               SET   seatsocc = seatsocc + 3
               WHERE mandt    = '002' AND
                     carrid   = 'LH'   AND
                     connid   = '0400' AND
                     fldate   = '20010228'.

Updating primary key problem

Similar Messages

Maybe you are looking for