How Websphere 9 restart fixes database exception?

[Rohit Sam]

I am using websphere 9, Java (ejb) application(jpa 2.0). I got an intermittent issue "org.apache.openjpa.peraistence.PersistenceException DB2 SQLError =-530 , SQLSTATE =-23503 error

And not able to save.
But after restart my server from websphere console, the error gone. After few hours the error will be back..How server restart fix a database exception?

[Tim Holloway]

Welcome to the Ranch, Rohit!

Unfortunately, IBM's DB2 error codes can be particularly useless. What would serve us better is if you could copy-and-paste the stack trace of that failure from your DB2 log to this message thread. Please do a text copy, not a screen shot!

[Rohit Sam]

Org.apache.openjpa.jdbc.sql.DBDirectory.narrow(DBDictionary.java:4998)
at Org.apache.openjpa.jdbc.sql.DBDirectory.newstoreexception(DBDictionary.java:571)
at Org.apache.openjpa.jdbc.sql.QLExceptions.getStore(SQLExceptions.java:136)
at Org.apache.openjpa.jdbc.sql.QLExceptions.getStore(SQLExceptions.java:78)
at org.apache.openjp.jdbc.kernal.PreparedStatementManagerImpl.flushAndupdate(PreparedStatementManagerImpl.java:144)
org.apache.openjp.jdbc.kernal.PreparedStatementManagerImpl.lushInternal(PreparedStatementManagerImpl.java:100)
org.apache.openjp.jdbc.kernal.PreparedStatementManagerImpl.flush(PreparedStatementManagerImpl.java:88)
org.apache.openjp.jdbc.kernal.OperarionOrderUpdateManager.flushPrimaryRow(OperationOrderUpdateManager.java:203)
org.apache.openjp.jdbc.kernal.OperarionOrderUpdateManager.flush(OperationOrderUpdateManager.java:89)
org.apache.openjp.jdbc.kernal.abstractUpdateManager.flush(AbstractUpdateManager.java:105)
org.apache.openjp.jdbc.kernal.abstractUpdateManager.flush(AbstractUpdateManager.java:78)
org.apache.openjp.jdbc.kernal.elegatingStoreManager.flush(DelegatingStoreManager.java:131)
INSERT INTO TABLE(TESTNO,ADDEDBY,UPDATEDBY,CURRENTTIME,MODIFYTIME)VALUES(?,?,?,?,?)

[Tim Holloway]

Thanks!

The DB2 error codes you got are explained here: https://www.sqlerror.de/db2_sql_error_-530_sqlstate_23503.html

Basically, it says that you are attempting to insert a new row into TABLE, but there's a foreign key value in that data that has no corresponding value in the foreign table.

That's a bug in the database logic. The foreign table needs to have that value added before the data can be added to TABLE.

[Rohit Sam]

Yes. but how it fix after restarting the server. It is working fine without any issue for some hours. And issue came back and again fix after restart the server

[Tim Holloway]

Possibly because you had a pending commit for the foreign table that got posted when you shut the system down so that when it tried to insert again the foreign key was now already in the database.

It's still a bug in the application program, regardless.