Heinrich,
I can't be sure if this is your problem, but in the past, I have
experienced strange behavior in Base when I upgraded MySQL without
saving and restoring the database. In other words, using the old MySQL
version database with the new MySQL version. At those times, I was
getting some complaints in the MySQL log about the database integrity.
However, running the MySQL-suggested database fixer made it worse, not
better. Since then, I have been using the policy to save the database
with mysqldump under the old version, renaming the MySQL database
directory to force a fresh install, upgrading MySQL, and then, after the
installation, restore the database with the new version's mysql. Since
I have been doing that process, I have not seen any database strangeness
and the log remains "clean", but verbose. So, if you have upgraded
MySQL at some time in the past and not "upgraded" the database at that
time, that may be your instability's "root cause".
You may try a save and restore. The conversion process of mysqldump
converting to SQL and mysql importing the resulting SQL can act as a
sort of filter to discard problem areas in the database. I don't think
it will do any harm, but always backup first.
For the record, I am using MySQL 5.5.36 and MySQL-connector-java-5.1.18
and they seem to work well together. (Slackware 14.0 (K3.2.29) Linux)
HTH.
Girvin Herr
On 05/16/2014 12:26 PM, Heinrich Stoellinger wrote:
Hello,
To start with - I am not certain that this belongs into THIS "forum"...
I run a MySQL-database which is stored at a
Linux-Debian-Squeeze-Server.
This DB consists of "dozens" of inter-related tables, views,
functions, procedures,
etc., etc.
I have been accessing the DB both through the the command-line client
and phpMyAdmin,
adding, updating, deleting tuples with no problems at all with ALL
tables.
Except - when accessing the DB through LO-Base, using the JDBC
connector from MySQL
(mysql-connector-java-5.1.30), there is just ONE table which I cannot
access. it is
defined like this:
CREATE TABLE inventar
(nummer INTEGER NOT NULL,
bezeichnung VARCHAR (255) not null default ' ',
stueckZahl INTEGER not null default 1,
anschDatum DATE not null DEFAULT '1999-09-01',/*
Anschaffungsdatum */
fvbNr INTEGER not null default 0, /* Firmennummer des
Lieferanten */
typBesch CHAR(1) not null default 'k', /* Miete, Kauf,
Leihe, Spende,... */
anschKosten FIXED (11,2) default 0, /* Anschaffungskosten
in EUR */
repKosten FIXED (11,2) default 0, /* aufgelaufene
Reparaturkosten in EUR */
abschreibung FIXED (11,2) default 0, /* aufgelaufene
Abschreibung in EUR */
datEliminiert DATE NOT NULL DEFAULT '2099-09-01',/* aus Inventar
ausgeschieden am... */
vorhanden SMALLINT NOT NULL default 1, /* Menge laut
Inventur */
invDat DATE not null default '1999-09-01', /* Inventur-Datum */
bemerkung VARCHAR (255) not null default ' ',
PRIMARY KEY (nummer),
UNIQUE INDEX (nummer),
INDEX (fvbNr),
INDEX (typBesch),
FOREIGN KEY (fvbNr) REFERENCES fvbPartner(nummer),
FOREIGN KEY (typBesch) REFERENCES invBeschTyp(code)
)
CHARACTER SET latin1 COLLATE latin1_german1_ci
ENGINE=InnoDB
;
I am sure that the problem lies with the JDBC-Connector itself or its
usage under LO-Base,
since I don't experience any problems when going either through the
command-line client,
phpMyAdmin or the native MySQL connector under LO-Base. There is NO
entry in any of the
MySQL-logs...
Has anybody experienced a similar situation?
Regards
H.S.