Hello Emmanuel,Thank you for your answer. I have tried something but it has nothing to do with the ..BOLBs. Either with VARCHAR2 for the recovery log Table it's not working. But now i know the Problem (not the solution). It has nothing to do with my Client. It has to do with Transactions. Even if i try to use the sql client from Sequoia it doesn't work when i do the following: Type begin on prompt, then an update statement -> then it fails with this 911 Error from oracle. As i have understood you try to insert the transactions commands into the recovery table also ? As i don't see this insert command (can i trace it ?), maybe there is something wrong with the statement (Wrong type, not escaped)?
Do i something wrong or maybe ist a Configuration Problem?
Thank you , Regards Andreas
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 ZeichenThe 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
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
