Disabling contextual LOB creation as createClob() method threw error

Question

I am using Hibernate 3.5.6 with Oracle 10g. I am seeing the below exception during initialization but the application itself is working fine. What is the cause for this exception? and how it can be corrected?

Exception
Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException

Info
Oracle version: Oracle Database 10g Enterprise Edition Release 10.2.0.4.0 JDBC driver: Oracle JDBC driver, version: 11.1.0.7.0

"the application itself is working fine"... as long as you don't try using LOBs, I imagine. — Nyerguds, Nov 23 '15 at 12:05

Narayan Yerrabachu · Answer 1 · 2017-08-22T07:52:12.420

81

Disable this warning by adding property below.

For Spring application:

spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults=false

Normal JPA:

hibernate.temp.use_jdbc_metadata_defaults=false

edited Aug 22 '17 at 07:52

answered Feb 28 '17 at 12:33

Narayan Yerrabachu

1,714
1
19
31

1

Which java version did you try this with? Intellij is unable to find this property. – comiventor Dec 06 '17 at 08:53
We tried with eclipse as well as Intellij. In both cases its working.Actually, we tired with java 6, 7,8 and its working without any problem for us. Just debug your code or cross check your code. – Narayan Yerrabachu Dec 06 '17 at 15:42

score 67 · Answer 2 · answered Jan 04 '11 at 11:01

67

As you noticed, this exception isn't a real problem. It happens during the boot, when Hibernate tries to retrieve some meta information from the database. If this annoys you, you can disable it:

hibernate.temp.use_jdbc_metadata_defaults false

answered Jan 04 '11 at 11:01

jpkroehling

13,881
1
37
39

3

Thanks Partenon. I am aware of the option to disable it,but I am trying to find the reason for this exception. Any pointers? – GiriByaks Jan 04 '11 at 13:55
6

As far as I understand it, it's not a problem with your application, Hibernate is just verifying if the DB supports some features and adjusting itself in case it doesn't. I would verify if any mapping is triggering this (like a LOB field), but it's nothing to worry about. – jpkroehling Jan 04 '11 at 14:09
5

**WARNING**: Using this solution with Oracle is **dangerous**! It leads to **unexpected COMMITs**. When hibernate creates temporary tables it has to open a new transaction, since DDL statements in Oracle DB imply COMMIT. By setting this option to false you disable opening new transaction and DDL get issues within your transaction COMMITing it. – Boris Brodski Apr 04 '14 at 14:22
@BorisBrodski , are you sure the behavior you described is caused by setting this property to false? Looking at the code, I don't see anything extra being executed when this is false: https://github.com/hibernate/hibernate-orm/blob/f19c8e995a763fe7c31fbb7f5777ac6ff608c215/hibernate-core/src/main/java/org/hibernate/engine/jdbc/env/internal/JdbcEnvironmentInitiator.java#L76 . – jpkroehling Apr 07 '14 at 14:59
3

@jpkrohling Yes, I debugged hibernate4.2.7 and saw if myself: Setting `useJdbcMetadata` to `false` prevents `metaReportsDDLCausesTxnCommit` to be set and it stays `false`! http://grepcode.com/file/repo1.maven.org/maven2/org.hibernate/hibernate-core/4.1.2.Final/org/hibernate/engine/jdbc/internal/JdbcServicesImpl.java – Boris Brodski Apr 07 '14 at 15:43
Works fine. Put this line on file persistence.xml – Thiago Pereira May 21 '15 at 14:01

score 28 · Answer 3 · answered Jan 04 '11 at 13:52

28

Looking at the comments in the source:

Basically here we are simply checking whether we can call the java.sql.Connection methods for LOB creation added in JDBC 4. We not only check whether the java.sql.Connection declares these methods, but also whether the actual java.sql.Connection instance implements them (i.e. can be called without simply throwing an exception).

So, it's trying to determine if it can use some new JDBC 4 methods. I guess your driver may not support the new LOB creation method.

answered Jan 04 '11 at 13:52

Steve K

19,408
6
52
50

5

Does it mean that `Driver does not support LOB feature` or `Database does not support LOB feature` ? – Marek Sebera May 15 '12 at 09:55
@MarekSebera Driver. I'm having this problem because something is mysteriously overriding my C3P0 library with an ancient version. The database supports it just fine. – Nyerguds Nov 23 '15 at 12:10

score 24 · Answer 4 · answered Feb 05 '18 at 13:38

In order to hide the exception:

For Hibernate 5.2 (and Spring Boot 2.0), you can either use the use_jdbc_metadata_defaults property that the others pointed out:

# Meant to hide HHH000424: Disabling contextual LOB creation as createClob() method threw error 
spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults: false

Or, if you want to not have any side effects from the above setting (there's a comment warning us about some Oracle side effects, I don't know if it's valid or not), you can just disable the logging of the exception like this:

logging:
   level: 
      # Hides HHH000424: Disabling contextual LOB creation as createClob() method threw error 
      org.hibernate.engine.jdbc.env.internal.LobCreatorBuilderImpl: WARN

UdayKiran Pulipati · Answer 5 · 2020-02-14T11:40:59.950

21

To get rid of the exception

INFO - HHH000424: Disabling contextual LOB creation as createClob() method threw error :java.lang.reflect.InvocationTargetException

In hibernate.cfg.xml file Add below property

<property name="hibernate.temp.use_jdbc_metadata_defaults">false</property>

edited Feb 14 '20 at 11:40

answered Apr 09 '14 at 08:24

UdayKiran Pulipati

6,579
7
67
92

5

This is the same answer as from Steve K. Why do you answer it again? – Bevor Apr 25 '14 at 06:34
4

@Bevor he explain the problem but I gave answer. – UdayKiran Pulipati Apr 25 '14 at 07:05
2

You only want to command updates by copying an already given answer. Your answer doesn't distinguish from Steve K. – Bevor Apr 29 '14 at 07:27
2

Thanks. Based on this, I added `` to the `persistence.xml` file and it solved the issue for me. I use JPA with Hibernate. – dschulz Mar 21 '15 at 23:15
4

@Bevor to be honest for a novice like me this answer is much clearer in part where should i put this property – Anatoly Yakimchuk Aug 17 '16 at 10:38

Torsten Krah · Answer 6 · 2015-12-15T12:38:09.637

15

Update to this for using Hibernate 4.3.x / 5.0.x - you could just set this property to true:

<prop key="hibernate.jdbc.lob.non_contextual_creation">true</prop>

to get rid of that error message. Same effect but without the "threw exception" detail. See LobCreatorBuilder source for details.

edited Dec 15 '15 at 12:38

answered Dec 15 '15 at 12:15

Torsten Krah

368
3
9

set this in persistence.xml – user961954 Jul 15 '20 at 06:59
You can set it there, if you use e.g. spring to setup the PU you (can) set it in springs configuration space - so it depends ;). – Torsten Krah Apr 09 '21 at 07:59

score 10 · Answer 7 · edited Jun 08 '18 at 08:09

10

Just add below line in application.properties

spring.jpa.properties.hibernate.temp.use_jdbc_metadata_defaults: false

edited Jun 08 '18 at 08:09

slfan

8,950
115
65
78

answered Jun 08 '18 at 07:50

Rupesh Patil

153
3
9

score 10 · Answer 8 · answered May 22 '19 at 12:00

As mentioned in other comments using

hibernate.temp.use_jdbc_metadata_defaults = false

...will fix the annoying message, but can lead to many other surprising problems. Better solution is just to disable contextual LOB creation with this:

hibernate.jdbc.lob.non_contextual_creation = true

This will cause Hibernate (in my case, its 5.3.10.Final) to skip probing the JDBC driver and just output following message:

HHH000421: Disabling contextual LOB creation as hibernate.jdbc.lob.non_contextual_creation is true

So far it looks like this setting doesn't cause any problems.

Boris Brodski · Answer 9 · 2017-07-07T07:35:30.913

4

Updating JDBC driver to the lastest version removed the nasty error message.

You can download it from here:

http://www.oracle.com/technetwork/database/enterprise-edition/jdbc-112010-090769.html

Free registration is required though.

edited Jul 07 '17 at 07:35

answered Apr 04 '14 at 14:44

Boris Brodski

8,425
4
40
55

score 4 · Answer 10 · answered Feb 14 '18 at 13:15

If you set:

hibernate.temp.use_jdbc_metadata_defaults: false

it can cause you troubles with PostgreSQL when your table name contains reserved word like user. After insert it will try to find id sequence with:

select currval('"user"_id_seq');

which will obviously fail. This at least with Hibernate 5.2.13 and Spring Boot 2.0.0.RC1. Haven't found other way to prevent this message so now just ignoring it.

migueldoctor · Answer 11 · 2019-12-07T16:09:38.293

3

When working with Spring boot 2.1.x this warning message appears when starting up the application.

As indicated here, maybe this problem didn't show up in earlier versions because the related property was set to true by default and now it is false:

https://github.com/spring-projects/spring-boot/issues/12007

In consequence, solving this is as simple as adding the following property to the spring application.property file.

spring.jpa.properties.hibernate.jdbc.lob.non_contextual_creation = true

edited Dec 07 '19 at 16:09

answered Dec 07 '19 at 15:15

migueldoctor

31
7

Thanks for this. An exception trace in log INFO mode is really annoying! – Daniel Fernández Apr 29 '20 at 14:33

sami · Answer 12 · 2015-10-17T01:44:38.490

1

The problem occurs because of you didn't choose the appropriate JDBC. Just download and use the JDBC for oracle 10g rather than 11g.

edited Oct 17 '15 at 01:44

answered Oct 09 '15 at 20:12

sami

358
1
4
5

Huh. This completely contradicts the response of Boris Brodski. You sure this makes any difference? – Nyerguds Nov 23 '15 at 13:05

score 1 · Answer 13 · answered Oct 05 '20 at 07:39

1

I am using hibernate 5.3.17 and it works fine by adding given properties

hibernate.default_entity_mode=dynamic-map
hibernate.temp.use_jdbc_metadata_defaults=true
hibernate.jdbc.lob.non_contextual_creation = true

Thanks

answered Oct 05 '20 at 07:39

S K

11
1

score 0 · Answer 14 · answered Jan 04 '19 at 03:05

I hit this error when my web app was started in Linux by user logged in with insufficient access rights. This error

org.hibernate.engine.jdbc.internal.LobCreatorBuilder - HHH000424: Disabling contextual LOB creation as createClob() method threw error : java.lang.reflect.InvocationTargetException

usually preceded by other errors / exceptions, especially from your application server i.e for Tomcat:

org.apache.catalina.LifecycleException: Failed to initialize component ...

or

java.lang.UnsatisfiedLinkError: ... cannot open shared object file: No such file or directory

Solution:

Stop your web apps current instance.
Login with super user or those with sufficient access rights i.e root
Restart your web app or call previous function again.

score 0 · Answer 15 · answered Sep 30 '19 at 10:51

For anyone who is facing this problem with Spring Boot 2

by default spring boot was using hibernate 5.3.x version, I have added following property in my pom.xml

<hibernate.version>5.4.2.Final</hibernate.version>

and error was gone. Reason for error is already explained in posts above

score 0 · Answer 16 · answered Jun 26 '22 at 13:18

0

As mentioned by Jacek Prucia, setting the hibernate.temp.use_jdbc_metadata_defaults=false, will bring other "surprising problems", one of them is the batch inserts will stop working..

answered Jun 26 '22 at 13:18

FranKs

51
4

score -1 · Answer 17 · answered Feb 26 '16 at 04:30

-1

Remove @Temporal annotations if you use it with java.sql.* classes.

answered Feb 26 '16 at 04:30

Amr El-Demerdash

15
3

score -3 · Answer 18 · answered Mar 24 '15 at 19:10

-3

Check if you are not on a VPN. I had the same issue but realized the db I was connecting to remote!

answered Mar 24 '15 at 19:10

logixplayer

939
2
13
23

Disabling contextual LOB creation as createClob() method threw error

18 Answers18

Linked