Error creating repository in MySQL

Classic Servoy
1

I’m moving to mysql 5.0. I created the repository db in mysql. for some reason when prompted by servoy to create the repository I keep getting these errors. Passwords are correct.

I’m running Servoy 3.5.7
Mysql 5.0.67
latest java connector for mysql.

any ideas?

Servoy Display
com.servoy.j2db.persistence.RepositoryException: com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Can’t create table ‘.\servoy_repository\servoy_content_spec.frm’ (errno: 121)
com.servoy.j2db.persistence.RepositoryException: java.sql.SQLException: Can’t create table ‘.\servoy_repository\servoy_content_spec.frm’ (errno: 121)
java.sql.SQLException: Can’t create table ‘.\servoy_repository\servoy_content_spec.frm’ (errno: 121)

Log file

Caused by: java.sql.SQLException: Can’t create table ‘.\servoy_repository\servoy_content_spec.frm’ (errno: 121)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1055)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:956)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3491)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:3423)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1936)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2060)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2536)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2465)
at com.mysql.jdbc.StatementImpl.execute(StatementImpl.java:734)
at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
at sun.reflect.NativeMethodAccessorImpl.invoke(Unknown Source)
at sun.reflect.DelegatingMethodAccessorImpl.invoke(Unknown Source)
at java.lang.reflect.Method.invoke(Unknown Source)
at com.servoy.j2db.persistence.datasource.p.invoke(Unknown Source)
at $Proxy0.execute(Unknown Source)
at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:183)
at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:183)
at org.apache.commons.dbcp.DelegatingStatement.execute(DelegatingStatement.java:183)
… 18 more

2

Sorry
Java 1.6
Windows XP

3

Ok I figured it out.

I had physically moved db’s into my new install from another computer. Started MySQL then later removed them by deleting the folders - NOT DROPPING

Apparently there is some internal db that stores table names. when Servoy tried to run the repository create method MySQL thought the tables already existed. I could find where these values were kept. It was easiest to do a reinstall. Works like a champ now

4

kschuster:
I had physically moved db’s into my new install from another computer. Started MySQL then later removed them by deleting the folders - NOT DROPPING

Ouch.

kschuster:
Apparently there is some internal db that stores table names. when Servoy tried to run the repository create method MySQL thought the tables already existed. I could find where these values were kept. It was easiest to do a reinstall. Works like a champ now

Any RDBMS uses a ‘catalog’ to hold the meta data of your database. So your database names, table names, column names and properties, stored procedures, contrainsts and index settings, etc…
RDBMS’s like Sybase iAnywhere hold the catalog and data of a single database in 1 file so that is safe to move around like that but lots of other brands use a database folder that holds many directories and files, like your MySQL.
So when you upgrade (or downgrade) your RDBMS you in fact should dump all the data and schema (database meta data) to a file and import (restore) that into your new environment.
Moving whole database directories around from one version to another can work (it depends on the version changes) but is not recommendable when you don’t really know what you are doing.

Hope this makes things clearer.