春批 - ORA-08177

时间:2016-11-28 07:39:33

标签: spring oracle spring-batch

org.springframework.dao.CannotSerializeTransactionException: PreparedStatementCallback; SQL [INSERT into BATCH_JOB_INSTANCE(JOB_INSTANCE_ID, JOB_NAME, JOB_KEY, VERSION) values (?, ?, ?, ?)]; ORA-08177: can't serialize access for this transaction
; nested exception is java.sql.SQLException: ORA-08177: can't serialize access for this transaction

        at org.springframework.jdbc.support.SQLErrorCodeSQLExceptionTranslator.doTranslate(SQLErrorCodeSQLExceptionTranslator.java:267)
        at org.springframework.jdbc.support.AbstractFallbackSQLExceptionTranslator.translate(AbstractFallbackSQLExceptionTranslator.java:73)
        at org.springframework.jdbc.core.JdbcTemplate.execute(JdbcTemplate.java:660)
        at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:909)
        at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:970)
        at org.springframework.jdbc.core.JdbcTemplate.update(JdbcTemplate.java:975)
        at org.springframework.batch.core.repository.dao.JdbcJobInstanceDao.createJobInstance(JdbcJobInstanceDao.java:115)
        at org.springframework.batch.core.repository.support.SimpleJobRepository.createJobExecution(SimpleJobRepository.java:135)
        at sun.reflect.GeneratedMethodAccessor147.invoke(Unknown Source)
        at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:43)
        at java.lang.reflect.Method.invoke(Method.java:497)
        at org.springframework.aop.support.AopUtils.invokeJoinpointUsingReflection(AopUtils.java:317)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.invokeJoinpoint(ReflectiveMethodInvocation.java:190)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:157)
        at org.springframework.transaction.interceptor.TransactionInterceptor$1.proceedWithInvocation(TransactionInterceptor.java:99)
        at org.springframework.transaction.interceptor.TransactionAspectSupport.invokeWithinTransaction(TransactionAspectSupport.java:281)
        at org.springframework.transaction.interceptor.TransactionInterceptor.invoke(TransactionInterceptor.java:96)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.batch.core.repository.support.AbstractJobRepositoryFactoryBean$1.invoke(AbstractJobRepositoryFactoryBean.java:172)
        at org.springframework.aop.framework.ReflectiveMethodInvocation.proceed(ReflectiveMethodInvocation.java:179)
        at org.springframework.aop.framework.JdkDynamicAopProxy.invoke(JdkDynamicAopProxy.java:207)
        at com.sun.proxy.$Proxy54.createJobExecution(Unknown Source)

我尝试了以下内容:

1)将隔离级别更改为ISOLATION_READ_COMMITTED

  @Bean(name="jobRepository")
public JobRepository getJobRepository() {
    JobRepositoryFactoryBean factoryBean = new JobRepositoryFactoryBean();
    factoryBean.setDataSource(configDataSource);
    factoryBean.setTransactionManager(transactionManager);
    factoryBean.setIsolationLevelForCreate("ISOLATION_READ_COMMITTED");
    try {
        factoryBean.afterPropertiesSet();
        return factoryBean.getObject();
    } catch (Exception e) {
        log.error("JobRepository bean could not be initialized");
        throw new BatchConfigurationException(e);
    }
}

2)改变所有弹簧批核心表的initrans

更新:我已经尝试过在其他问题中提供的可能解决方案。但是,我仍然会在一周内至少一次面对这个问题。

2 个答案:

答案 0 :(得分:1)

最后,我能够摆脱这个长期拖延的问题。

我没有使用作业存储库bean正确配置作业启动器。在那之后,我从来没有得到这个问题,代码在生产环境中成功运行没有任何问题。



//Overriding default configurer, since by default spring batch configuration allows only one datasource
	@Bean
    public BatchConfigurer configurer(){
      return new DefaultBatchConfigurer(configDataSource);
    }
	
	@Bean(name="jobRepository")
	public JobRepository getJobRepository() {
		JobRepositoryFactoryBean factoryBean = new JobRepositoryFactoryBean();
		factoryBean.setDataSource(configDataSource);
		factoryBean.setTransactionManager(configTxManager);
		factoryBean.setIsolationLevelForCreate("ISOLATION_READ_COMMITTED");
		factoryBean.setTablePrefix("BATCH_");
		try {
			factoryBean.afterPropertiesSet();
			return factoryBean.getObject();
		} catch (Exception e) {
			log.error("JobRepository bean could not be initialized");
			throw new BatchConfigurationException(e);
		}
	}
	
	@Bean
	public JobRegistryBeanPostProcessor jobRegistryBeanPostProcessor(JobRegistry jobRegistry) {
	    JobRegistryBeanPostProcessor jobRegistryBeanPostProcessor = new JobRegistryBeanPostProcessor();
	    jobRegistryBeanPostProcessor.setJobRegistry(jobRegistry);
	    return jobRegistryBeanPostProcessor;
	}
	
	@Bean
	public JobLauncher jobLauncher(){
		SimpleJobLauncher jobLauncher = new SimpleJobLauncher();
		jobLauncher.setJobRepository(jobRepository);
		return jobLauncher;
	}
	
	@Bean
    public JobOperator jobOperator() {
        SimpleJobOperator jobOperator = new SimpleJobOperator();
        jobOperator.setJobExplorer(jobExplorer);
        jobOperator.setJobLauncher(jobLauncher);
        jobOperator.setJobRegistry(jobRegistry);
        jobOperator.setJobRepository(jobRepository);
        return jobOperator;
    }




答案 1 :(得分:1)

我在我们的一个环境中配置时遇到了同样的问题,有趣的是我们已经在生产中使用了相同的作业。所以我认为这是因为我用来创建表的 DDL 导致了我们作业配置中的任何问题。

我们解决了在 BATCH_JOB_INSTANCE 上执行虚拟插入的问题,并且成功了。

相关问题