Error - Duplicate Entry in Primary Key

technopak

Hi,

My application is suddenly giving me an error which I haven't seen before.

It says - 'Error persisting business object OBJECTNAME Duplicate Entry ID_NUMBER Primary ' where OBJECTNAME is my BO and ID_NUMBER is the auto-generated BO.ID

I'm using a MySQL database and some research suggested that my database could be corrupted. However, even after all the recommended checking and re-building of the BASDB, the error still pops up intermittently.

Has anyone come across this before, or can anyone suggest what could be wrong ?

Thanks in advance,

Peter

ACDC

Somewhere along the way you got a duplicate ID number in the table that is referenced in the error. You should be able to find the duplicate record if you search the table with a suitable DB tool. - Delete the record and re-create it within AwareIM (remember to take care of any related records when you delete)

This kind of thing happens if you are inserting data into the table from outside the Aware application and not taking care to ensure the ID no is in sync with IDGEN.MAX.ID value, or you have restored data without restoring the IDGEN table.

Also it could occur if MAX_.ID in the IDGEN table is creating ID nos that have already been created as a result of the above. To resolve this, reset Max_ID in the IDGEN table to start allocating numbers above the current highest ID number in the DB

technopak

Thanks ACDC for the reply,

We have had to restore data on this particular site in the past few days, so it sounds like you are pointing me in the right direction.

I've checked the tables for the ID referenced in the error message and there is one record with that ID already existing, and it seems that Aware is trying to allocate that ID a second time.

Sounds like your MAX_.ID could be exactly my problem.

I'll check it out and post again later.

Thanks again,

Peter

technopak

ACDC,

You're a star !!

Manually setting the MAX_ID to a number well in excess of the number of records in the database has sorted the problem.

Looks like the IDGEN table didn't import correctly when we restored the data.

It was something which could have proved a major issue for us, even support said they didn't know what was causing it.

Thanks for the great help.

Peter