Administrator
|
Some users noticed locks with Oracle database : http://www.nabble.com/Process-schedule-question-td14758838.html#a14773258.
The ticket is still open (http://jira.codehaus.org/browse/SONAR-139), but it seems that Attlassian experience similar problems. They recommend to use the driver 10.1.0.5 instead of last 10.2.x. We don't know if it fixes sonar, but you could give a try if you're using oracle. More details on http://www.atlassian.com/software/jira/docs/v3.12.1/databases/oracle.html Download Oracle drivers : http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html |
Ah, that really is interesting.
It turns out that I had placed ojdbc14-10.1.0.4.jar in Sonar's extensions directory. I replaced this with ojdbc14-10.2.0.jar and restarted the Sonar service. This has fixed the problem. I no longer have any locks on the DB, and Sonar's chunked through the pending snapshot data, and all appears well. So, I appear to have the direct opposite behaviour to Attlassian, in that upgrading to 10.2.0 from 10.1.0.4 has resolved the Oracle locks problem. I replaced the ojdbc jar in Sonar's client directory and fired off the maven task to submit more data, and that worked fine, too. So, everything's now working :) Thanks, Martin. On 21/01/2008, Simon Brandhof <[hidden email]> wrote: Some users noticed locks with Oracle database : <a href="http://www.nabble.com/Process-schedule-question-td14758838.html#a14773258" target="_blank" onclick="return top.js.OpenExtLink(window,event,this)"> http://www.nabble.com/Process-schedule-question-td14758838.html#a14773258. |
On 2008-01-21 14:03, Martin Gladdish wrote:
(...) > So, I appear to have the direct opposite behaviour to Attlassian, in that > upgrading to 10.2.0 from 10.1.0.4 has resolved the Oracle locks problem. > > I replaced the ojdbc jar in Sonar's client directory and fired off the maven > task to submit more data, and that worked fine, too. > > So, everything's now working :) Glad to here that at least with 10g version Sonar works properly. I tried to use a few different driver version, but with 10.2.0.2, 10.2.0.3 and 10.1.0.5 there are locks on a database and 9.2.0.8 results: SQL Error: 17090, SQLState: null 2008.01.21 14:25:12 ERROR o.h.u.JDBCExceptionReporter snapshot=10001, group=10000- operation not allowed: streams type cannot be used in batching Unfortunately we are using only Oracle 9i, because of our clients who use that version. Hopefully one day a company will upgrade some machine to 10g... Thanks for your effort anyway. Regards Marcin > On 21/01/2008, Simon Brandhof <[hidden email]> wrote: >> Some users noticed locks with Oracle database : >> http://www.nabble.com/Process-schedule-question-td14758838.html#a14773258. >> The ticket is still open (http://jira.codehaus.org/browse/SONAR-139), but >> it seems that Attlassian experience similar problems. They recommend to use >> the driver 10.1.0.5 instead of last 10.2.x. We don't know if it fixes >> sonar, but you could give a try if you're using oracle. >> >> More details on >> http://www.atlassian.com/software/jira/docs/v3.12.1/databases/oracle.html >> Download Oracle drivers : >> http://www.oracle.com/technology/software/tech/java/sqlj_jdbc/index.html >> > --------------------------------------------------------------------- To unsubscribe from this list, please visit: http://xircles.codehaus.org/manage_email |
Free forum by Nabble | Edit this page |