Oracle 11g problem

[hakanskucuk]

Hi,

I have a Spring based application that uses Activiti. Currenty it uses mysql. Now i am trying to migrate to Oracle 11g
But i get an exception

### Cause: org.apache.ibatis.type.TypeException: Error setting null parameter.  Most JDBC drivers require that the JdbcType must be specified for all nullable parameters. Cause: java.sql.SQLException: Invalid column type: 1111

How can I overcome this problem?

Using ojdbc6 as jdbc driver.

[hakanskucuk]

any help appreciated

[ronald_van_kuij]

The best thing you can do if nobody can give you a direct answer (which is not strange with such a generic report) is to use a searchengine. Try it, I used the error you posted and the first link in google gives you a direction on how to find the cause of this

[hakanskucuk]

Please don't think that i haven't googled before posting. I know the cause but I haven't got a working solution yet.

Since the problem is a generic problem that anybody come across if they want to use oracle 11g, I thought somenone can across the problem and solve it.

Also I want the activiti developers to be informed about the problem.

[ronald_van_kuij]

Please don't think that i haven't googled before posting. I know the cause but I haven't got a working solution yet.

I'm no psychic with a glass ball so how could I know? Next time state what you did (read the 'how to ask smart questions). If you know the cause (meaning which column in what table causes the problem, then that is 99% of the solution…

Since the problem is a generic problem that anybody come across if they want to use oracle 11g, I thought somenone can across the problem and solve it.

Obviously not (yet) since it would have bean posted

Also I want the activiti developers to be informed about the problem.

Thanks

[sfcgroup]

Hi, this is my first post on the forums however I've been tracking the forum for a long time now.

We have came across the same problem and made our search for it but it didn't work for us.

I was disappointed unable to find any reasonable answer. If anyone wishes to make a helpful comment it's greatly appreciated.

[ronald_van_kuij]

My comment IS constructive. In the first post in google I referred to it mentions how to find out wich colum in which table is causing the problem. Since almost none of us have Oracle 11g running, you are the only ones that can do this.

[frederikherema1]

Our QA runs (green) against oracle 10g -> the version we support. As Ronald states, it should be good to know which column it's about and perhaps a patch or suggestion on how to fix it?