string literal too long in jdbc adapter

[Former Member]

Hi,

i got error message "ORA-01704 : string literal too long" in using receiver jdbc adapter,, this occur from clob type column in table. it did work if i send small sentence on clob type. i want to use only jdbc adapter to approach it.

thanks

dennis

[Former Member]

HI,

Its not the problem of XI adapter actually.

Please check the field length you have defined in the database for every attribute you are dealing with.

And try to make the lengths compatible in XI and DB table.

Thanks

Amitanshu

[Former Member]

this is clob type.. anybody has experience with clob type in using jdbc adapter, do i adjust size even if clob type there?

thanks

dennis

null

[MichalKrawczyk]

hi,

>>>>anybody has experience with clob type in using jdbc adapter

yes

>>>>do i adjust size even if clob type there?

no you don't

at first read thread: Welcome and Rules of Engagement

Regards,

michal

[Former Member]

Hi-

CLOB data type store character data with following size.

Max Size:Oracle 8 stores 4Gigabytes

Max Size:Oracle 9 stores 4Gigabytes

Are you passing data less then these size ?

[Former Member]

Hi,

this is one record in realtime. so this is not such a big size..

when i send small data on contents column, it did work, but more than this data on contents column, it did not work with error "string literal too long".

i do not want to use server java proxy,, does anyone has experience with CLOB?

thanks you

dennis

[Former Member]

Hi-

I think this is not an XI problem.

The problem is the size of the atribute in the database.The attribute in the database is not able to accept a lengthier string.

To solve this you need to alter the table in the database and increase the size of attribute.

[Former Member]

Hi ogawa,

This is not XI - Error... It is ORACALE exception....

Try this:

-

---

ORA-01704 string literal too long

Cause: The string literal is longer than 4000 characters.

Action: Use a string literal of at most 4000 characters. Longer values may

only be entered using bind variables.

regards,

Ansar.

[bhavesh_kantilal]

Hi dennis,

use the logSQLStatement in the Table in the receiver JDBC adapter and check the SQL query coming out of XI. Use thsi SQL query on your DB client and check if it works,

logSQLStatement --> value is True.

If it does not work on the DB Client you can contact your Database admin to help you out on this. If it works on the DB Client then maybe it is an XI issue.

Regards

Bhavesh