We have exactly the same problem. We use Hibernate to map our objects and we occassionaly saw this error in production affecting our internet clients. We also had a query our internal customers could run over the database and our testing indicated the query running in a WebSphere transaction would lock rows in the same file. We couldn't see how thae same rows would be affected but once we removed the ability to execute the query, the problem went away. We couldn't see any way to run the query using Hibernate either without a transaction or with an isolation level allowing other users to update the same rows. ----- Original Message ---- From: Todd Allen <tballen@xxxxxxxxxx> To: java400-l@xxxxxxxxxxxx Sent: Thursday, 25 January, 2007 2:42:30 PM Subject: SQL0913 error I have a Java application that is throwing an SQL0913 error when running on the production system but runs fine on our test system. The error text is: Row or object FILEX in LIBRARYX type *FILE in use There are no object locks on the file. The application is straightforward. SQL select do some processing SQL update of same record Given that the exact same application runs fine on the test system, I figured there must be some setting that is different on the production system. Is there any way around this error by setting the transaction isolation JDBC property or something like that? This has me absolutely stumped so ANY assistance is greatly appreciated. Thanks, Todd
As an Amazon Associate we earn from qualifying purchases.
Operating expenses for this site are earned using the Amazon Associate program and Google Adsense.