Hi Andreas,
It's not a problem of PreparedStatement encoding because even a simple
string text like 'commit' fails:
2009-01-30 15:25:32,264 ERROR sequoia.controller.recoverylog Logger thread was
unable to log LogRequestEvent: Log entry: log id6 (T) transactionId:1
requestId:0 vlogin:user status: E sql:commit params:null because of
java.sql.SQLException: ORA-00911: Ungültiges Zeichen
The reason might be that you have a unicode character that does not match the
charset of oracle. You could try to use NCLOB instead of CLOB in your recovery
log definition. You might want to check your Locale settings on the Sequoia and
Oracle machine to make sure they are compatible.
I was also looking at
http://www.oracle.com/technology/sample_code/tech/java/codesnippet/jdbc/clob10g/handlingclobsinoraclejdbc10g.html
and they suggest that one can use the newly introduced |Connection| property|:
SetBigStringTryClob. The driver might have some additional options for handling
properly String conversions.
Keep me posted with your findings,
|
Emmanuel
--
Emmanuel Cecchet
FTO @ Frog Thinker
Open Source Development & Consulting
--
Web: http://www.frogthinker.org
email: [email protected]
Skype: emmanuel_cecchet
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia
