Hello Emanuel, Sorry i didn't saw that the statements where in another file ;-). Attached the request log.
Thank you regards Andreas
Hola Emmanuel,Thank you for such a quick answer. I have configured log4j with Debug, but i didn't saw the statements. Attached my log4j, recoverylog and a trace ouput of the error. My Problem is thaht i don't see the statements, maybe i have configured wrong ?Thank you regards AndreasHi Andreas,It looks like the error you get is either a problem with a column name (could you post your recovery log config?) or some encoding of the PreparedStatement that needs to be logged into the recovery log. Could you post the PreparedStatement that you are trying to execute? If you set log4j.logger.org.continuent.sequoia.controller.virtualdatabase.request to DEBUG in log4j.properties, that should log the encoded PreparedStatement that are sent to the recovery log.Thanks for your interest in Sequoia, EmmanuelI was testing a Sequoia setup with one Controller and two Database Backends. All configured with an Oracle 10g Database, also the Recovery Instanz. During my tests if have used the DbVisualizer Version 5.1.1 (License Version) to manipulate the Virtual Database. When i was using the Sql-Window to send update, delete, insert commands everyting works fine. But when i have tried to work with the mouse to select what i want, the following update on Sequoia failed at the Recovery Table. What i have done was to choose inside the Object Menue all Tables. Then i have choosen one Table with "script select all" from this Table. I new sql windows was opened to select everything from the Table [select * from Andreas]. Inside the window the results were shown and on this result i have changed a String Parameter and commited the value. The update on all Databases were done, but with the Recovery i have got the following error message:java.sql.SQLException: ORA-00911: invalid character.The command is stored inside the Recovery Table but it seems that a following update fails? I have switched to Debug Level so see more whats happening, but i didn't saw the sql statements. The only thing i knew is that a perpared statement was send.Well the result is, that sequoia says that the Recovery is corrupted. Is there a possibility to avoid this error ?If not is it possible to find out what sql statements were send to the Recovery Table ?Am i doing something wrong ? Best Regards Andreas Staab ------------------------------------------------------------------------ _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia------------------------------------------------------------------------ _______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
-- ___________________ Andreas Staab Dolivostrasse 11 D-64293 Darmstadt Germany Telefon: (+49) (0) 61 51 / 81 93 15 Telefax: (+49) (0) 61 51 / 81 93 43 eMail: [email protected] WWW: http://www.mtg.de media transfer AG Firmensitz: Dolivostraße 11, 64293 Darmstadt Registergericht: Amtsgericht Darmstadt, HRB 8901 Vorstand: Dr. Hans-Detlef Schulz, Andrea Klenk, Jürgen Ruf Aufsichtsratsvorsitzender: Dr. Thomas Milde
15:22:08,594 myoracleDB S 0 0 select * from ANDREAS/ 15:23:46,335 myoracleDB S 1 0 select * from ANDREAS/ 15:24:26,327 myoracleDB S 2 0 select count(*) from ANDREAS where H_BEG_TYPE = ?/<!%1|1|!%> 15:24:26,357 myoracleDB B 0 15:24:26,360 myoracleDB W 3 0 update ANDREAS set NIXDA = ? where H_BEG_TYPE = ?/<!%S|change|!%><!%1|1|!%> 15:24:26,375 myoracleDB C 0 15:25:32,018 myoracleDB S 4 0 select count(*) from ANDREAS where H_BEG_TYPE = ?/<!%1|1|!%> 15:25:32,021 myoracleDB B 1 15:25:32,022 myoracleDB W 5 1 update ANDREAS set NIXDA = ? where H_BEG_TYPE = ?/<!%S|change2|!%><!%1|1|!%> 15:25:32,028 myoracleDB C 1
smime.p7s
Description: S/MIME Cryptographic Signature
_______________________________________________ Sequoia mailing list [email protected] https://forge.continuent.org/mailman/listinfo/sequoia
