Corrupt database file

2004-04-08 Thread Tom O';Neil
I seem to have encountered a corrupt database file, and was wondering if anyone could shed some light onto how this occurred. I was able to restore from a backup, so I'm OK now, but I'd like to know how to avoid this in the future. I'm running MySql-max 4.0.18, using InnoDB tables. It looks like th

Error dropping databases

2004-03-25 Thread Tom O';Neil
I am trying to drop several InnoDB and am unable to do so. I login to the command line client and enter "drop database [db_name];" and then get this error: ERROR 1217: Cannot delete or update a parent row: a foreign key constraint fails Why am I unable to drop these databases? Tom = -- M

Re: Problems connecting to MySql on WebSphere 5.1

2004-03-23 Thread Tom O';Neil
t have changed in the 5.1 upgrade. Tom --- Mark Matthews <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Tom O'Neil wrote: > > > I've been running an application on WebSphere 5.0 > > (Linux) that uses the MySql Connector/J 3

Re: Problems connecting to MySql on WebSphere 5.1

2004-02-19 Thread Tom O';Neil
6I: JDBC driver version : mysql-connector-java-3.0.10-stable ( $Date: 2004/01/13 21:56:18 $, $Revision: 1.27.2.33 $ ) Tom --- Mark Matthews <[EMAIL PROTECTED]> wrote: > -BEGIN PGP SIGNED MESSAGE- > Hash: SHA1 > > Tom O'Neil wrote: > > > I've been running

Problems connecting to MySql on WebSphere 5.1

2004-02-19 Thread Tom O';Neil
I've been running an application on WebSphere 5.0 (Linux) that uses the MySql Connector/J 3.10 to connect to a MySql-max 4.0.15 database (also on Linux). All was working fine, until I recently installed WebSphere 5.1. Now my datasources (configured exactly as before) no longer work - WebSphere seem

MySql JDBC connection pooling in Websphere

2003-01-07 Thread Tom O';Neil
I have configured WAS Express 5.0 to connect to MySql 4.0, however I am unable to open any connections. I know that the connection to the MySql server works, because if I change any of the connection parameters (port, database name, login), the JDBC driver returns the appropriate error message. I h