sql - 异常 ORA-08103: 使用 Hibernate 的 setfetchsize 时对象不再存在

Question

我正在使用休眠。我需要获取大约 1000000 条记录，这会导致超时异常。所以我使用setfetchsize了 6000 条记录，以便它将操作分配到 6000 条记录中的每个事务中的多个事务中。

全部取走大约需要 21 小时。

但与此同时，如果有人删除要获取的记录之一，则检索记录，然后我得到ORA-08103: object no longer exists。

现在我想跳过检索时删除的那个对象。我怎样才能做到这一点？

Answer 1

游标很可能是基于使用ON COMMIT DELETE ROWS选项创建的全局临时表 (GTT) 打开的。ORA-08103: object no longer exists错误的原因是紧跟在该语句commit之后的delete语句。这是一个简单的例子：

 SQL> declare
  2    type t_recs is table of number;
  3    l_cur sys_refcursor;    -- our cursor
  4    l_rec t_recs; 
  5  
  6  begin
  7  
  8    -- populating a global temporary table GTT1 with sample data  
  9    insert into GTT1(col)
 10      select level
 11        from dual
 12     connect by level <= 1000;
 13  
 14   open l_cur         -- open a cursor based on data from GTT1
 15    for select col
 16          from GTT1;
 17  
 18    -- here goes delete statement
 19    -- and
 20    commit;  <-- cause of the error. After committing  all data from GTT1 will be
 21              -- deleted and when we try to fetch from the cursor
 22    loop      -- we'll face the ORA-08103 error
 23      fetch l_cur    -- attempt to fetch data which are long gone.
 24       bulk collect into l_rec;
 25      exit when l_cur%notfound;
 26    end loop;
 27  
 28  end;
 29  /


ORA-08103: object no longer exists
ORA-06512: at line 24

使用子句重新创建全局临时表on commit preserve rows将允许从基于该表的游标中安全地获取数据，而不必担心遇到 ORA-08103:错误。

Answer 2

经过一周的努力，我终于解决了这个问题：

解决方案：游标很可能是基于全局临时表 (GTT) 打开的，该临时表是使用 ON COMMIT DELETE ROWS 选项创建的。ORA-08103：对象不再存在错误的原因是紧跟在删除语句之后的提交语句。DBA 团队不同意将 GTT 更改为提交保留行，所以最后我在 Java 服务层中添加了代码库[实现 Spring - 程序化事务]

package com.test;

import java.util.List;
import javax.sql.DataSource;

import org.springframework.dao.DataAccessException;
import org.springframework.jdbc.core.JdbcTemplate;
import org.springframework.transaction.PlatformTransactionManager;
import org.springframework.transaction.TransactionDefinition;
import org.springframework.transaction.TransactionStatus;
import org.springframework.transaction.support.DefaultTransactionDefinition;

public class StudentJDBCTemplate implements StudentDAO {
   private DataSource dataSource;
   private JdbcTemplate jdbcTemplateObject;
   private PlatformTransactionManager transactionManager;

   public void setDataSource(DataSource dataSource) {
      this.dataSource = dataSource;
      this.jdbcTemplateObject = new JdbcTemplate(dataSource);
   }
   public void setTransactionManager(PlatformTransactionManager transactionManager) {
      this.transactionManager = transactionManager;
   }
   public void create(String name, Integer age, Integer marks, Integer year){
      TransactionDefinition def = new DefaultTransactionDefinition();
      TransactionStatus status = transactionManager.getTransaction(def);

      try {
         String SQL1 = "insert into Student (name, age) values (?, ?)";
         jdbcTemplateObject.update( SQL1, name, age);

         // Get the latest student id to be used in Marks table
         String SQL2 = "select max(id) from Student";
         int sid = jdbcTemplateObject.queryForInt( SQL2 );

         String SQL3 = "insert into Marks(sid, marks, year) " + "values (?, ?, ?)";
         jdbcTemplateObject.update( SQL3, sid, marks, year);

         System.out.println("Created Name = " + name + ", Age = " + age);
         transactionManager.commit(status);
      } 
      catch (DataAccessException e) {
         System.out.println("Error in creating record, rolling back");
         transactionManager.rollback(status);
         throw e;
      }
      return;
   }
   public List<StudentMarks> listStudents() {
      String SQL = "select * from Student, Marks where Student.id=Marks.sid";
      List <StudentMarks> studentMarks = jdbcTemplateObject.query(SQL, 
         new StudentMarksMapper());

      return studentMarks;
   }
}