Thanks for the suggestion. I tried:

 <RecoveryLog driver="com.mysql.jdbc.Driver"
        url="jdbc:mysql://10.1.2.1:3306/ctl1log" login="user"
password="xxxx">
        <RecoveryLogTable tableName="RECOVERY" logIdColumnType="BIGINT NOT
NULL"
          vloginColumnType="VARCHAR(255) NOT NULL" sqlColumnName="sql_data"
sqlColumnType="TEXT NOT NULL"
          extraStatementDefinition=",PRIMARY KEY (log_id)"/>
        <CheckpointTable tableName="CHECKPOINT"
          checkpointNameColumnType="VARCHAR(255) NOT NULL"/>
        <BackendTable tableName="BACKEND"
          databaseNameColumnType="VARCHAR(255) NOT NULL"
          backendNameColumnType="VARCHAR(255) NOT NULL"
          checkpointNameColumnType="VARCHAR(255) NOT NULL"/>
        <DumpTable tableName="DUMP" dumpNameColumnType="VARCHAR(255) NOT
NULL"
          dumpDateColumnType="TIMESTAMP"
          dumpPathColumnType="VARCHAR(255) NOT NULL"
          dumpFormatColumnType="VARCHAR(255) NOT NULL"
          checkpointNameColumnType="VARCHAR(255) NOT NULL"
          backendNameColumnType="VARCHAR(255) NOT NULL"
          tablesColumnType="VARCHAR(255) NOT NULL"/>
      </RecoveryLog>

But it is still a no-go. Getting the same error message when I load this
xml. I also modified the sequoia.dtd and changed the sqlColumnName to
sql_data.

Are there any other logs I can look at or a way to get sequoia to show me
what the response from the mysql server is?

Thanks.

On Fri, Oct 3, 2008 at 3:49 PM, Emmanuel Cecchet <[EMAIL PROTECTED]>wrote:

> Miles,
>
> By default, Sequoia uses 'sql' as the column name to store SQL in the
> recovery table. As this is a reserved word in MySQL this is likely to fail.
> You can read
> https://forge.continuent.org/pipermail/sequoia/2006-December/004222.htmlto 
> see how to handle this.
> Also varchar(255) is likely to be too small for some SQL, you should use an
> unlimited string length by using the MySQL TEXT data type.
>
> Hope this helps,
> Emmanuel
>
>  I'm still having trouble getting sequoia to be happy with the recovery log
>> and I'm not sure what I'm doing wrong. If I'm understanding the
>> documentation correctly, all I have to do is create the database where the
>> logs will be stored, and set up the XML config for sequoia to connect to the
>> database and create all the tables. I've tried manually creating the tables
>> myself and starting from an empty database with no tables and I still can't
>> get it working. Anyone mind looking at my config?
>>
>> I'm using mysql as the backend database. I modified the sample config to
>> specify sizes for the VARCHAR columns since mysql requires that. But I've
>> also tried it without specifying the size and it still isn't working:
>>
>> <RecoveryLog driver="com.mysql.jdbc.Driver"
>>        url="jdbc:mysql://10.1.2.1:3306/ctl1log <
>> http://10.1.2.1:3306/ctl1log>" login="test" password="xxxxxxx">
>>        <RecoveryLogTable tableName="RECOVERY" logIdColumnType="BIGINT NOT
>> NULL"
>>          vloginColumnType="VARCHAR(255) NOT NULL"
>> sqlColumnType="VARCHAR(255) NOT NULL"
>>          extraStatementDefinition=",PRIMARY KEY (log_id)"/>
>>        <CheckpointTable tableName="CHECKPOINT"
>>          checkpointNameColumnType="VARCHAR(255) NOT NULL"/>
>>        <BackendTable tableName="BACKEND"
>>          databaseNameColumnType="VARCHAR(255) NOT NULL"
>>          backendNameColumnType="VARCHAR(255) NOT NULL"
>>          checkpointNameColumnType="VARCHAR(255) NOT NULL"/>
>>        <DumpTable tableName="DUMP" dumpNameColumnType="VARCHAR(255) NOT
>> NULL"
>>          dumpDateColumnType="TIMESTAMP"
>>          dumpPathColumnType="VARCHAR(255) NOT NULL"
>>          dumpFormatColumnType="VARCHAR(255) NOT NULL"
>>          checkpointNameColumnType="VARCHAR(255) NOT NULL"
>>          backendNameColumnType="VARCHAR(255) NOT NULL"
>>          tablesColumnType="VARCHAR(255) NOT NULL"/>
>>      </RecoveryLog>
>>
>> When I use the CLI to try and load my virtual DB config:
>> load virtualdatabase configuration
>> /usr/local/sequoia/config/virtualdatabase/test.xml
>>
>> I get:
>>
>> Loading of virtual databases configuration file failed (because of Failed
>> to check JDBC Recovery log tables.).
>>
>> tcpdump shows that it is at least connecting to the database server and
>> carrying on a conversation. Unfortunately, I'm having trouble getting mysql
>> to keep a query log so I can see exactly what query sequoia is building and
>> trying to run on the server.
>>
>> -Miles
>> ------------------------------------------------------------------------
>>
>> _______________________________________________
>> Sequoia mailing list
>> [email protected]
>> https://forge.continuent.org/mailman/listinfo/sequoia
>>
>
>
> --
> 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
>



-- 
Miles Stevenson
Credit Benefit Services
Senior Systems Engineer
Mobile: (571) 236-2379
Business: (571) 257-9095
_______________________________________________
Sequoia mailing list
[email protected]
https://forge.continuent.org/mailman/listinfo/sequoia

Reply via email to