Haar 7.2 hard. . . . Do not know and see. I believe the. DB2 7.2 database, Java procedures so if applicable, as the ROWNUM DB2 did not like Java is open. I improved DB2 Pagination Use of the following SQL syntax Entertained seeking record number GR "SELECT count (1) FROM (select rownumber () OVER (Order BY" +pkField+ ")" + "AS SYSTEM_ROW_NEXT, splitpage_table.* from" + "(" +countSql.trim () + ") Splitpage_table) AS SYSTEM_SPLITPAGE_TEMP with hae Yi." /*** PkField : mainly Key. , ResultSQL : The author's words. **/ ===================== =[result]= ResultSQL= "SELECT * FROM (select rownumber () OVER (Order BY" +pkField+ ")" + AS SYSTEM_ROW_NEXT, splitpage_table.* from "+ "(" +resultSQL.trim () + ") Splitpage_table) AS SYSTEM_SPLITPAGE_TEMP" + "WHERE SYSTEM_ROW_NEXT BETWEEN" + ((currentPage-1) *pageSize+1) + "and" + (currentPage*pageSize) + "with hae Yi." ===================                   Encapsulation of the components into a single very satisfactory results after the implementation of quick, Pagination no wrong. However, I use the paging components So if there are other procedures at the same table Such as : ResultSQL= "select * from test" I made inquiries if the same phrase : "select * from test where a>;2" Then the entire list will be frozen. Symptoms : The table has been fixed to achieve the most number of specific description I remember unclear, because it is said. But this only son in the use of such inquiries Pagination there, if I do not use it no matter query (), which is directly used in the components of SQL Call Paging implementation of the original words, even without WITH UR, no problems. Since then it is not using DB2 pairs inquiries WITH UR, is WITH UR just stay in the outer query is exclusive lock. So what are these inquiries seed distribution UR lock, it is not written on the inside of SQL syntax support things happen. Incidentally, with 810 friends may not know that DB2 7.2, DB2 is the official driving without RESULT TYPE, the construction method Statement stat = conn.createStatement (ResultSet.TYPE_FORWARD_ONLY, ResultSet.CONCUR_READ_ONLY); This is not : Only Statement stat = conn.createStatement (); Therefore, only state. Is there any solution to Oracle Lane and the trip through the lock set ResultSet.CONCUR_READ_ONLY resolved. 0000000000 Older brother and sister deed, tell me. I seek your next meal. Haar 7.2 hard. . . . Do not know and see. I believe the. You may generally unique problem, because the thread, but I have a background in the process of running the same time, the circumstances prospects Pagination Haar 7.2 hard. . . . Do not know and see. I believe the. BY tape will use this problem. Haar 7.2 hard. . . . Do not know and see. I believe the. How nobody FOR ah, that is not clear? Haar 7.2 hard. . . . Do not know and see. I believe the. I have to ask this question over the DBA DB2, but that too could not answer why the certification will lock sets query results. Haar 7.2 hard. . . . Do not know and see. I believe the. Understand, Bangniding Haar 7.2 hard. . . . Do not know and see. I believe the. IBM][CLI Driver][DB2/NT] SQL0912N already the largest database lock Number of requests. For inquiries, but only in the time of the table, but do SELECT * FROM (select rownumber () OVER (Order BY pkField) AS SYSTEM_ROW_NEXT. splitpage_table.* from (SELECT * FROM TEST) splitpage_table) AS SYSTEM_SPLITPAGE_TEMPWHERE SYSTEM_ROW_NEXT BETWEEN ((currentPage-1) *pageSize+1) and (currentPage*pageSize) with hae Yi The inquiry Haar 7.2 hard. . . . Do not know and see. I believe the. Arab frustration No one answered the Internet to find information on the following, under the advice of others come to the following conclusions ： 1, may be LOCKLIST enough, before increasing, we should have no problem (in fact, there may be further increased points) 2, may be run out of table space. 3, may run out of log space. 4, but could be found in other reasons. 5, is not likely to commit, roolback, it may not have read carefully the procedures Check tomorrow to customers, the coroner's padding. Haar 7.2 hard. . . . Do not know and see. I believe the. Need to look at this table is a table lock or not to lock Bank; I think the problem probably lies with ur; Can see hae Yi, rr, rs ＝, the distinction between cs. Haar 7.2 hard. . . . Do not know and see. I believe the. Usually, unless the following conditions are true, the use of record level locks : 1. Choose hae Yi 2. Rr choice, without the need to visit the predicate scanning program; 3.locksize 82478 table; 4. Has been harvested table lock, lock escalation; 5. Admission through the lock table shown in Table lock. . . . [ Closed window ]