On Fri, 2010-03-05 at 13:41 -0600, Steve Ebersole wrote: > Not sure about "SQUIRREL_GET_ERROR_OFFSET". You use Squirrel?
Yes, Squirrel SQL Client probably created that. I'll try dropping the tables/plsql and try again. > > The rest come from tests in the testsuite, org.hibernate.test.sql > > On 03/05/2010 12:47 PM, Scott Marlow wrote: > > On Fri, 2010-03-05 at 09:12 -0600, Steve Ebersole wrote: > >> odd. were you able to fix this by cleaning up db? We do use some > >> triggers as part of other tests; could it maybe be an issue with schema > >> export not able to cleanup those tables? But even there the error is > >> strange because we do not commit nor rollback as part of the trigger. > > > > Is it okay if I clean up the database? > > > > Looking at the test user in the database, I see the following: > > > > Tables: > > > > "HIBBRTRU"."HT_ANIMAL", "HIBBRTRU"."HT_CHILD", > > "HIBBRTRU"."HT_FILTER_HQL_JOINED_CUST", > > "HIBBRTRU"."HT_FILTER_HQL_JOINED_EMP", > > "HIBBRTRU"."HT_FILTER_HQL_JOINED_PERSON", > > "HIBBRTRU"."HT_FILTER_HQL_JOINED_USER", "HIBBRTRU"."HT_FOOS", > > "HIBBRTRU"."HT_HUMAN", "HIBBRTRU"."HT_ITEMS", "HIBBRTRU"."HT_JCUSTOMER", > > "HIBBRTRU"."HT_JEMPLOYEE", "HIBBRTRU"."HT_JOINER", > > "HIBBRTRU"."HT_JPERSON", "HIBBRTRU"."HT_LEAFSUBSUBCLASS", > > "HIBBRTRU"."HT_MAMMAL", "HIBBRTRU"."HT_PRODUCT_TABLE", > > "HIBBRTRU"."HT_TRUCK", "HIBBRTRU"."HT_VEHICLE", "HIBBRTRU"."POINT" > > > > stored procedures: > > > > "HIBBRTRU"."CREATEENTITYE", "HIBBRTRU"."CREATEENTITYP", > > "HIBBRTRU"."DELETEENTITYE", "HIBBRTRU"."UPDATEENTITYE" > > > > stored functions: > > > > "HIBBRTRU"."DELETEENTITYP", "HIBBRTRU"."SQUIRREL_GET_ERROR_OFFSET", > > "HIBBRTRU"."UPDATEENTITYP" > > > > Triggers owned by this user: > > > > None > > > > > > Anyone recognize the stored procedures/functions? > > > > > >> > >> basically i have no clue; this sounds 'off'. > >> > >> On 03/04/2010 08:14 PM, Scott Marlow wrote: > >>> I ran org.hibernate.ejb.test.lock.LockTest and get a weird "ORA-04092: > >>> cannot COMMIT in a trigger" failure in: > >>> > >>> testLockOptimistic(org.hibernate.ejb.test.lock.LockTest) > >>> testLockWrite(org.hibernate.ejb.test.lock.LockTest) > >>> testLockWriteOnUnversioned(org.hibernate.ejb.test.lock.LockTest) > >>> testLockPessimisticForceIncrement(org.hibernate.ejb.test.lock.LockTest) > >>> testLockOptimisticForceIncrement(org.hibernate.ejb.test.lock.LockTest) > >>> testContendedPessimisticReadLockTimeout(org.hibernate.ejb.test.lock.LockTest) > >>> testContendedPessimisticWriteLockTimeout(org.hibernate.ejb.test.lock.LockTest) > >>> testContendedPessimisticWriteLockNoWait(org.hibernate.ejb.test.lock.LockTest) > >>> testQueryTimeout(org.hibernate.ejb.test.lock.LockTest) > >>> > >>> test failures are here http://pastebin.com/F07aBFvm > >>> > >>> Did anyone commit changes that could impact the above tests? I'm also > >>> wondering if my oracle test database is hosed somehow (using > >>> -Poracle11gRAC). > >>> > >>> Thanks for any advice. This is blocking me from fixing HHH-4972. > >>> > >>> Scott > >>> > >>> _______________________________________________ > >>> hibernate-dev mailing list > >>> hibernate-dev@lists.jboss.org > >>> https://lists.jboss.org/mailman/listinfo/hibernate-dev > >> > > > > > _______________________________________________ hibernate-dev mailing list hibernate-dev@lists.jboss.org https://lists.jboss.org/mailman/listinfo/hibernate-dev
