Skip to content

Spring-jdbc 5.0.5 NamedParameterJdbcTemplate.batchUpdate ORA-01000 [SPR-16814] #21354

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Closed
spring-projects-issues opened this issue May 11, 2018 · 1 comment
Assignees
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) status: declined A suggestion or change that we don't feel we should currently apply

Comments

@spring-projects-issues
Copy link
Collaborator

spring-projects-issues commented May 11, 2018

Fedor opened SPR-16814 and commented

After migrating from Spring 4.1.7 to Spring 5.0.5 we have ORA-01000: maximum open cursors exceeded when using with Oracle 12c and ojdbc7-driver.

Exception raised after following code

@SuppressWarnings("unchecked")
private void updateHiddenOffers(Map<String, Object>[] updateBatchParams) {
 int[] updateResults = namedJdbcTemplate.batchUpdate(UPDATE_HIDDEN_OFFER_SQL, updateBatchParams);

The issue is very similar to #20687

But we dont have ability to update ojdbc driver.

Is it fixed in 5.0.6 version?


Affects: 5.0.5

Issue Links:

@spring-projects-issues
Copy link
Collaborator Author

Juergen Hoeller commented

There hasn't been any recent work on this. Since this is effectively a bug in the Oracle JDBC driver, I'm afraid we won't be introducing a workaround for an older driver at this point.

You could try setting spring.jdbc.getParameterType.ignore=true as a system property on in a spring.properties file in the root of your classpath, or use spring-jdbc-4.3.17 for the time being... with all other jars set to 5.0.6 (which isn't officially supported but should work fine in practice). I strongly recommend upgrading the JDBC driver though.

@spring-projects-issues spring-projects-issues added type: bug A general bug status: declined A suggestion or change that we don't feel we should currently apply in: data Issues in data modules (jdbc, orm, oxm, tx) labels Jan 11, 2019
@spring-projects-issues spring-projects-issues removed the type: bug A general bug label Jan 12, 2019
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
in: data Issues in data modules (jdbc, orm, oxm, tx) status: declined A suggestion or change that we don't feel we should currently apply
Projects
None yet
Development

No branches or pull requests

2 participants