Same problem here. I can add that my application is widely deployed, and 
each instance created a db for its internal configuration. Now everyone of 
them is failing, so I think it's not a problem of corruption... maybe the 
start parameters? The jdbc url with which it was created is: 

jdbc:h2://amp_db;LOCK_MODE=0;UNDO_LOG=0;TRACE_LEVEL_FILE=0;FILE_LOCK=SOCKET;AUTO_SERVER=TRUE
 


You can find a failing db here: 

https://www.dropbox.com/s/h0i9ys98dz5xp88/amp_db.h2.zip

Opening it with version 1.3.176 will give the error. Latest 1.4.* version 
doesn't.

Please advise here. I can't upgrade if this is not solved somehow... 
anyhow, thanks for the excellent work you're doing! 

       Germano 

Il giorno giovedì 10 aprile 2014 12:11:22 UTC+2, Joerg Z. ha scritto:
>
> Hi,
> same problem here.
> After upgrade h2-1.3.174.jar to h2-1.3.176.jar and connect to my exist db 
> file I get to following trace: (without any executed statement, just 
> connect)
>
> 04-10 11:50:39 database: ALTER TABLE PUBLIC.REL_USERS_RIGHTS ADD 
> CONSTRAINT PUBLIC.REL_USERS_RIGHTS_FK_ID_USER FOREIGN KEY(ID_USER) 
> REFERENCES PUBLIC.TBL_USERS(ID) NOCHECK
> org.h2.jdbc.JdbcSQLException: Eindeutiger Index oder Primärschlüssel 
> verletzt: "PRIMARY KEY ON """".PAGE_INDEX"
> Unique index or primary key violation: "PRIMARY KEY ON """".PAGE_INDEX"; 
> SQL statement:
> ALTER TABLE PUBLIC.REL_USERS_RIGHTS ADD CONSTRAINT 
> PUBLIC.REL_USERS_RIGHTS_FK_ID_USER FOREIGN KEY(ID_USER) REFERENCES 
> PUBLIC.TBL_USERS(ID) NOCHECK [23505-176]
>
> A post repair with 
> backup/restore<http://www.h2database.com/html/tutorial.html#upgrade_backup_restore>
>  doesn't 
> help and run into same issue.
> Regards,
> Joerg
>

-- 
You received this message because you are subscribed to the Google Groups "H2 
Database" group.
To unsubscribe from this group and stop receiving emails from it, send an email 
to h2-database+unsubscr...@googlegroups.com.
To post to this group, send email to h2-database@googlegroups.com.
Visit this group at http://groups.google.com/group/h2-database.
For more options, visit https://groups.google.com/d/optout.

Reply via email to