This deadlock _could_ be due to defect 31907 that I have seen and fixed for DB2. The fix was in non-DB2 specific modules so it may fix this issue too. The problem was due to the same thread attempting to make two sql calls but not within the same transaction. The transaction code at the start of the request locks the row and the second attempt to access the same table within the same thread is waiting on the lock it already holds.
Warwick > -----Original Message----- > From: Frank Li [mailto:[EMAIL PROTECTED] > Sent: Thursday, November 04, 2004 10:54 AM > To: Slide Users Mailing List > Subject: Re: Anyone able to use Slide 2.1B2 with Oracle store ? > > > I tried a little with Oracle 10g (Slide 2.1B1). > I had experienced slow down and kind of dead lock > when I made about 70 (one by one) copies of a > Collection (5M) using copyMethod. So I have to switch > back to Slide with FS. > > From Oracle's enterprise manager console, I can see two > sql statement blocking each other: > > o insert into URI (URI_STRING) values (:1) > o select l.EXPIRATION_DATE, l.IS_INHERITABLE, > l.IS_EXCLUSIVE, u2.URI_STRING > as LCK, u3.URI_STRING as SUBJECT, u4.URI_STRING as TYPE, > l.OWNER from LOCKS > l, URI u, URI u2, URI u3, URI u4 where l.OBJECT_ID=u.URI_ID and > u.URI_STRING=:1 and l.LOCK_ID=u2.URI_ID and > l.SUBJECT_ID=u3.URI_ID and > l.TYPE_ID = u4.URI_ID > > > The following report might explain the reason of slow down. > DETAILED ADDM REPORT FOR TASK 'ADDM:486994704_1_1366' WITH ID 1373 > > ------------------------------------------------------------------ > > Analysis Period: 21-OCT-2004 from 18:00:39 to 19:00:58 > Database ID/Instance: 486994704/1 > Database/Instance Names: LKIT/lkit > Host Name: learning-kit > Database Version: 10.1.0.3.0 > Snapshot Range: from 1365 to 1366 > Database Time: 2629 seconds > Average Database Load: .7 active sessions > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~~~~~~~~~~~~~~~~ > > > FINDING 1: 100% impact (3056 seconds) > ------------------------------------- > SQL statements consuming significant database time were found. > > RECOMMENDATION 1: SQL Tuning, 94% benefit (2480 seconds) > ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID > "99tuu8t2rn5xd". > RELEVANT OBJECT: SQL statement with SQL_ID 99tuu8t2rn5xd and > PLAN_HASH 1 > insert into URI (URI_STRING) values (:1) > > RECOMMENDATION 2: SQL Tuning, 22% benefit (576 seconds) > ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID > "a5zxmwhm0j9ba". > RELEVANT OBJECT: SQL statement with SQL_ID a5zxmwhm0j9ba and > PLAN_HASH 205428933 > insert into BINDING (URI_ID, NAME, CHILD_UURI_ID) > select :1, :2, > URI_ID from URI where URI_STRING = :3 > > FINDING 2: 65% impact (1720 seconds) > ------------------------------------ > SQL statements were found waiting for row lock waits. > > RECOMMENDATION 1: Application Analysis, 65% benefit (1720 seconds) > ACTION: Trace the cause of row contention in the > application logic. > Use > given blocked SQL to identify the database objects involved. > Investigate application logic involving DML on these objects. > RATIONALE: The SQL statement with SQL_ID > "99tuu8t2rn5xd" was blocked > on > row locks. > RELEVANT OBJECT: SQL statement with SQL_ID 99tuu8t2rn5xd > insert into URI (URI_STRING) values (:1) > > SYMPTOMS THAT LED TO THE FINDING: > Wait class "Application" was consuming significant > database time. (65% > impact [1720 seconds]) > > FINDING 3: 22% impact (574 seconds) > ----------------------------------- > Time spent on the CPU by the instance was responsible for a > substantial part of database time. > > RECOMMENDATION 1: SQL Tuning, 22% benefit (574 seconds) > ACTION: Run SQL Tuning Advisor on the SQL statement with SQL_ID > "a5zxmwhm0j9ba". > RELEVANT OBJECT: SQL statement with SQL_ID a5zxmwhm0j9ba and > PLAN_HASH 205428933 > insert into BINDING (URI_ID, NAME, CHILD_UURI_ID) > select :1, :2, > URI_ID from URI where URI_STRING = :3 > > FINDING 4: 4.6% impact (122 seconds) > ------------------------------------ > Soft parsing of SQL statements was consuming significant > database time. > > RECOMMENDATION 1: Application Analysis, 4.6% benefit (122 seconds) > ACTION: Investigate application logic to keep open the > frequently used > cursors. Note that cursors are closed by both cursor > close calls > and > session disconnects. > > RECOMMENDATION 2: DB Configuration, 4.6% benefit (122 seconds) > ACTION: Consider increasing the maximum number of open > cursors a > session > can have by increasing the value of parameter "open_cursors". > ACTION: Consider increasing the session cursor cache size by > increasing > the value of parameter "session_cached_cursors". > > FINDING 5: 4.3% impact (114 seconds) > ------------------------------------ > Wait class "Other" was consuming significant database time. > > NO RECOMMENDATIONS AVAILABLE > > ADDITIONAL INFORMATION: Database latches in the "Other" > wait class were > not > consuming significant database time. > > FINDING 6: 2.1% impact (55 seconds) > ----------------------------------- > Wait event "class slave wait" in wait class "Other" was consuming > significant > database time. > > RECOMMENDATION 1: Application Analysis, 2.1% benefit (55 seconds) > ACTION: Investigate the cause for high "class slave > wait" waits. Refer > to Oracle's "Database Reference" for the description > of this wait > event. Use given SQL for further investigation. > RATIONALE: The SQL statement with SQL_ID "NULL-SQLID" was found > waiting > for "class slave wait" wait event. > RELEVANT OBJECT: SQL statement with SQL_ID NULL-SQLID > > > RECOMMENDATION 2: Application Analysis, 2.1% benefit (55 seconds) > ACTION: Investigate the cause for high "class slave > wait" waits in > Service "SYS$BACKGROUND". > > > ~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~~ > ~~~~~~~~~~~~~~~~ > > ADDITIONAL INFORMATION > ---------------------- > > Wait class "Administrative" was not consuming significant > database time. Wait class "Cluster" was not consuming > significant database time. Wait class "Commit" was not > consuming significant database time. Wait class "Concurrency" > was not consuming significant database time. Wait class > "Configuration" was not consuming significant database time. > Wait class "Network" was not consuming significant database > time. Wait class "Scheduler" was not consuming significant > database time. Wait class "User I/O" was not consuming > significant database time. > > The analysis of I/O performance is based on the default > assumption that the average read time for one database block > is 10000 micro-seconds. > > An explanation of the terminology used in this report is > available when you run the report with the 'ALL' level of detail. > > > ----- Original Message ----- > From: "Nick Longinow" <[EMAIL PROTECTED]> > To: "'Slide Users Mailing List'" <[EMAIL PROTECTED]> > Sent: Thursday, November 04, 2004 6:34 AM > Subject: RE: Anyone able to use Slide 2.1B2 with Oracle store ? > > > > Thanks, I'll try this driver. > > > > -----Original Message----- > > From: Roman Novak [mailto:[EMAIL PROTECTED] > > Sent: Thursday, November 04, 2004 9:33 AM > > To: Slide Users Mailing List > > Subject: Re: Anyone able to use Slide 2.1B2 with Oracle store ? > > > > Yes, I am using it and it works. > > > > I use ojdbc14.jar + a Oracle9i DB (didn't test with 8i) > > > > Roman > > > > Am Do 04.11.2004 15:08, Nick Longinow > > <[EMAIL PROTECTED]> > > schrieb: > > > >> Hi > >> > >> > >> > >> I'm using a simple Oracle store, and am unable to get it > to even do a > >> put > > of > >> a file. > >> > >> Can anyone help me ? > >> > >> > >> > >> java.sql.SQLException: Io exception: End of TNS data channel > >> > >> at > > oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:189) > >> > >> at > > oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:231) > >> > >> at > > oracle.jdbc.dbaccess.DBError.throwSqlException(DBError.java:345) > >> > >> at > >> > >> > oracle.jdbc.driver.OracleStatement.close(OracleStatement.java:855)at > >> > >> > > > oracle.jdbc.driver.OraclePreparedStatement.privateClose(OraclePrepared > > Statem > >> > >> > > > oracle.jdbc.driver.OraclePreparedStatement.close(OraclePreparedStateme > > nt.jav > >> > >> > > > org.apache.commons.dbcp.DelegatingStatement.close(DelegatingStatement. > > java:1 > >> > >> > > > 65)org.apache.slide.store.impl.rdbms.StandardRDBMSAdapter.close(Standa > > rdRDBM > >> > >> > > > org.apache.slide.store.impl.rdbms.CommonRDBMSAdapter.storeContent(Comm > > onRDBM > >> > >> > > > org.apache.slide.store.impl.rdbms.StandardRDBMSAdapter.storeRevisionCo > > ntent( > >> > >> > > > org.apache.slide.webdav.method.PutMethod.executeRequest(PutMethod.java > > :392) > >> > >> > >> > >> Domain.xml is > >> > >> > >> > >> <store name="OracleStore" > > >> > >> <nodestore > >> classname="org.apache.slide.store.impl.rdbms.JDBCStore"> > >> > >> <parameter > >> > > > name="adapter">org.apache.slide.store.impl.rdbms.OracleRDBMSAdapter</p > > aramet > >> er> > >> > >> <parameter > >> name="driver">oracle.jdbc.driver.OracleDriver</parameter> > >> > >> <parameter > >> name="url">jdbc:oracle:thin:@xx.xx.x.xx:1524:mysid</parameter> > >> > >> <parameter name="user">username</parameter> > >> > >> <parameter > name="password">password</parameter> > >> > >> <parameter > name="dbcpPooling">true</parameter> > >> > >> <parameter > > name="maxPooledConnections">10</parameter> > >> > >> <parameter > > name="isolation">READ_COMMITTED</parameter> > >> > >> <parameter name="compress">false</parameter> > >> > >> </nodestore> > >> > >> <contentstore> > >> > >> <reference store="nodestore" /> > >> > >> </contentstore> > >> > >> <securitystore> > >> > >> <reference store="nodestore" /> > >> > >> </securitystore> > >> > >> <lockstore> > >> > >> <reference store="nodestore" /> > >> > >> </lockstore> > >> > >> <revisiondescriptorsstore> > >> > >> <reference store="nodestore" /> > >> > >> </revisiondescriptorsstore> > >> > >> <revisiondescriptorstore> > >> > >> <reference store="nodestore" /> > >> > >> </revisiondescriptorstore> > >> > >> </store> > >> > >> Nick > >> > >> > >> > >> > >> > >> > >> > > > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > > > > > --------------------------------------------------------------------- > > To unsubscribe, e-mail: [EMAIL PROTECTED] > > For additional commands, e-mail: [EMAIL PROTECTED] > > > > > --------------------------------------------------------------------- > To unsubscribe, e-mail: [EMAIL PROTECTED] > For additional commands, e-mail: [EMAIL PROTECTED] > --------------------------------------------------------------------- To unsubscribe, e-mail: [EMAIL PROTECTED] For additional commands, e-mail: [EMAIL PROTECTED]
