Thanks Emmanuel, that helped. Although just placing the driver in the
drivers/ subdir of the sequoia tree didn't do it. I had to edit console.sh.
I guess I'm confused because if I'm using the console to connect to the
running server, and the server is explicitly told where the driver is, then
shouldn't the console pick that up from the server? Anyway, that problem is
fixed.
Is there a better source of documentation that the Install PDF manual on the
continuent website? I'm not getting an error when I try to load my virtual
db config:
Loading of virtual databases configuration file failed (because of Failed to
check JDBC Recovery log tables.).
So I'm guessing something is wrong with my <RecoveryLog> block. But I can't
find any actual documentation for this. It's included in the example xml
files, but doesn't seem to be documented very well in the install guide or
the administration guide. Do I need to pre-populate this recover log
database with the tables it needs or will sequoia do that when it connects?
Here is my config:
<RecoveryLog driver="com.mysql.jdbc.Driver"
url="jdbc:mysql://10.1.2.1:3306/test" login="test" password="test">
<RecoveryLogTable tableName="RECOVERY" logIdColumnType="BIGINT NOT
NULL"
vloginColumnType="VARCHAR NOT NULL" sqlColumnType="VARCHAR NOT
NULL"
extraStatementDefinition=",PRIMARY KEY (log_id)"/>
<CheckpointTable tableName="CHECKPOINT"
checkpointNameColumnType="VARCHAR NOT NULL"/>
<BackendTable tableName="BACKEND"
databaseNameColumnType="VARCHAR NOT NULL"
backendNameColumnType="VARCHAR NOT NULL"
checkpointNameColumnType="VARCHAR NOT NULL"/>
<DumpTable tableName="DUMP" dumpNameColumnType="VARCHAR NOT NULL"
dumpDateColumnType="TIMESTAMP"
dumpPathColumnType="VARCHAR NOT NULL"
dumpFormatColumnType="VARCHAR NOT NULL"
checkpointNameColumnType="VARCHAR NOT NULL"
backendNameColumnType="VARCHAR NOT NULL"
tablesColumnType="VARCHAR NOT NULL"/>
</RecoveryLog>
There is nothing curretntly in the "test" db on the database server, but I
can't find any docs on whether or not I'm supposed to put stuff into it.
On Thu, Oct 2, 2008 at 5:31 PM, Emmanuel Cecchet <[EMAIL PROTECTED]>wrote:
> Miles,
>
> The problem is once I start sequoia using the default controller.xml file.
>> It starts up correctly, but then when I try to load the driver from the CLI:
>>
>>
>> localhost:1090 > load driver com.mysql.jdbc.Driver
>> Failed to load driver com.mysql.jdbc.Driver
>> (java.lang.ClassNotFoundException: com.mysql.jdbc.Driver)
>>
> You are trying to load the MySQL driver in the console and not in the
> controller. If you want to use the console to connect to a MySQL database
> (without going through the controller), add the MySQL driver to the console
> classpath (edit console.sh or use the CLASSPATH_XTRA environment variable
> that is automatically appended to the CLASSPATH).
> Just copy the MySQL JDBC driver jar file in the controller's drivers/
> directory as indicated in the documentation if you want the driver to be
> accessible by the controller.
>
> So of course my real virtual database xml config isn't working because of
>> this. The log just shows:
>> ERROR Loading of virtual databases configuration file failed (because of
>> Failed to create JDBC RecoveryLog).
>>
> No, this is unrelated, you probably have a problem in your recovery log
> configuration. That is another issue.
>
> Thanks for your interest in Sequoia,
> 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
>
--
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
