Wednesday, October 2, 2013

oracle.repackaged.ucp.jdbc.oracle.RACCallbackGuard

today we saw this in the logs:

####<Oct 2, 2013 8:47:23 AM CEST> <Warning>
 <oracle.repackaged.ucp.jdbc.oracle.RACCallbackGuard> <acme111>
 <osbpr1ms4> <Thread-100> <<anonymous>> <> 
<0000K5o7QgvE4Uk5ozS4yY1IIgWK000003> <1380696443473> <BEA-000000> 
<RAC callback: guarded method threw exception>



no idea what happened.... it could be a RAC instance dead and TX being switched to another instance... still under investigation...

Ok, what happened is that the DBA team started the second node of the RAC cluster, and the JDBCDrivers somehow got the notification, but something must have gone wrong.


No comments: