cancel
Showing results for 
Search instead for 
Did you mean: 

Oracle JDBC driver 10g and xMII

Former Member
0 Kudos

I have a BLS that tries inserting CLOB data into Oracle 10g database. Since Oracle 8 JDBC driver does not support that (I saw other SDN messages on the same issue), I have download and copied Oracle JDBC driver for 10g

ojdbc14.jar to

C:\ServletExec AS\se-xMII\webapps\default\Lighthammer\WEB-INF\lib

folder

I restarted Servlet exec engine and I'm still seeing the same error

that the value to be inserted is too large ( I'm inserting more than

4000 characters but much lesser than 4 GB which CLOB column can take)

1. I want to understand if there is something else that I need to

change in order for xMII to pickup the new driver.

2. Also, should I add it classpath?

3. Looking at some Oracle notes on using capability of 10g driver for

manipulating large data, the property SetBigStringTryClob=true should

be set. I saw examples of some non-xMII applications setting it in their

servers.xml. Similarly, in which file can I set this property in xMII

to force the driver to use this feature?

Is ServerDefaults.xml under C:\Lighthammer\Illuminator\SysConf the

right place? Since it is not recommended to modify the configuration

files manually rather than using admin console, I'm not sure on this

one.

Let me know

Thanks

Accepted Solutions (0)

Answers (1)

Answers (1)

Former Member
0 Kudos

Could anyone pls. respond to this question

Thanks

Deepa

Former Member
0 Kudos

Do you have a particular error number?ORA-xxxx. Maybe that'll be a good starting point for searching a solution

Former Member
0 Kudos

Udayan

I would like to know where to set this property"SetBigStringTryClob=true" in xMII dataserver connection for manipulating CLOBs

Without this property being set, I get a failure in inserting a CLOB to the table with the error that

"ORA-01704 - String literal too long:"

Thanks

Deepa

Former Member
0 Kudos

Are you really sure this "SetBig.." thing is the solution?

Searching for the ORA error you posted results in quite a few solutions in the way you write your SQL statement.

Maybe changing your statement might help.

If you don't mind can you post the SQL statement?

Another good test would be to see if the SQL statement goes through without any errors when used from a different SQL editor.I would suggest do that first if you haven't already.

Former Member
0 Kudos

xMII does not support CLOBs or BLOBs directly, particularly with Oracle. It will treat them as strings, with some limitations (sounds like the 4000 character limit is a hard limit of the JDBC driver, irregardless of version). To retrieve/insert large CLOBs/BLOBs with Oracle requires special JDBC calls that are not implemented/supported in xMII at present, as far as I know.

Former Member
0 Kudos

Thanks Rick.

I had posted a support ticket with SAP and they confirmed that the methods that are used to set CLOBS are not being invoked by xMII. So this is not supported.

Hope the xMII v12 supports this approach.