2 Replies Latest reply on Feb 2, 2017 2:26 AM by hchiorean

PrimaryKey violation on restoreRepository() while migrating form 4.6.x to 5.3.x

timoschaz Jan 31, 2017 5:07 AM

Hello,

i made a backup from an existing 4.6.x repository using the backupRepository() functionality of modeshape.

When i want to restore the backup to the new 5.3 repository i get the following exception:

There was unexpected problem during the restore operations: org.h2.jdbc.JdbcBatchUpdateException: Eindeutiger Index oder Primärschlüssel verletzt: "PRIMARY_KEY_4 ON PUBLIC.MODESHAPE_REPOSITORY(ID) VALUES ('xxxx', yyyy)"

Unique index or primary key violation: "PRIMARY_KEY_4 ON PUBLIC.MODESHAPE_REPOSITORY(ID) VALUES ('xxxx', yyyy)"; SQL statement:

INSERT INTO MODESHAPE_REPOSITORY (ID, CONTENT) VALUES (?, ?) [23505-191]

When the backup is on the same version backup and restore has no problems.

1. Re: PrimaryKey violation on restoreRepository() while migrating form 4.6.x to 5.3.x

timoschaz Jan 31, 2017 7:21 AM (in response to timoschaz)

Additional Information:

restoreRepository() creates a backup where one entry doubles. that causes the problem.

Is there a tool that can cleanup backups of repositories in a proper way?
Actions
2. Re: PrimaryKey violation on restoreRepository() while migrating form 4.6.x to 5.3.x

hchiorean Feb 2, 2017 2:26 AM (in response to timoschaz)

restoreRepository() creates a backup where one entry doubles. that causes the problem.

not sure I understand what you mean. Can you provide an example and/or test case for this particular issue ?

Is there a tool that can cleanup backups of repositories in a proper way?
again, not sure what you mean: if the backup is corrupt, then there is no tool which can "fix" the backup since the corruption can be any number of things.

Since your backup was created using 4.6.x, did you make sure to use 4.6.2.Final ? This is the last 4.6 release which specifically fixes some backup issues around an entry being exported twice in the backup - see ModeShape 4.6.2.Final is available | ModeShape
Actions

Go to original post