Mailing List
Home
Forum Home
MySQL General - General MySQL discussion
MaxDB - Everything about MaxDB, formerly known as SAP DB
MySQL++ - Programming with the C++ API to MySQL
ODBC - ODBC with the MySQL Connector/ODBC driver
MySQL on Win32 - Runing MySQL on Windows 9x/Me/NT/2000/XP
Java Help - Mostly related to the MySQL Connector/J driver
Perl - Perl support for MySQL with DBI and DBD::mysql
GUI - MySQL GUI Tools
Announcement
Subjects
mysql openssl Question
mysql:it 's a db not a dbms how it 's possible?!
Does the binary log enabling affect the MySQL performances?
Strange behavior, Table Level Permission
FULLTEXT query format question
Preventing Duplicate Entries
Comparing and writing out BLOBS
Executing MySQL Commands From Within C Program
Can 't access mysql after kernel upgrade
Mysql 4 0 Oracle Stored Procedure Trigger Conversion
Downgrade Mysql from 4 to 3 23
MySQL Cluster Software
mysql test 4 1 fails with the gis test
ERROR 2002: Can 't connect to local MySQL server through socket
Getting Identity after INSERT
Update one field with more fields from another table
ERROR 1045: Access denied for user: 'root@localhost ' (Using
password: NO)
mysql have same function mthod as Oracle decode()
 
Error -3007: Invalid sequence for DML and DDL statements - on Linux-Vs 7.6, wher

Error -3007: Invalid sequence for DML and DDL statements - on Linux-Vs 7.6, wher

2006-11-24       - By Michael Neuber

 Back

Hi to all,
I am doing some tests on mass uploads based on batch runs on the WinXP
variant of MaxDB (Vs 7.5.00.38) as well as with shell scripts written
for the Linux variant (Vs 7.6.00.34).
Meanwhile, I am doing pretty well although lots of scripts are executed.

However, for the first time (!) in quite some months of work with MaxDB,
I stumbled across a very strange bug:

On the Linux system (2 Dual Opteron ? 1.8GHz, 4GB RAM) Memory, in a
certain command such as

Insert into table(..)
  select attribute1,attribute2,...attribute9
  from table2
  where attribute10 in (2222)

the DB on the Linux system prompts this:

Error -3007: Invalid sequence for DML and DDL statements .


This Insert-Into-Select statement is structurally completely ok,
as are more than ~3000 other insert statements of the same kind
(all are created via script), which have indeed been successfully executed.

On the WinXP laptop (MaxDB Vs 7.5.00.38, Pentium-M 1.7GHz, 1.256GB),
this error does not occur.

The where-condition '... where attribute10 in (2222) ...'
looks a bit strange at 1st sight, I know, but it is due to the way the
plenty of similar commands are created: I just have many of them with
more than one number in the in-clause.

Could anybody give me a valuable hint for the reason of this strange and
hardly explicable error, and maybe some recommendation on possible
work-arounds, too?
Do I maybe witness some hitherto unseen bug in Vs 7.6.00.34?

Regards

Michael Neuber


--
MaxDB Discussion Mailing List
For list archives: http://lists.mysql.com/maxdb
To unsubscribe:    http://lists.mysql.com/maxdb?unsub=mysql@(protected)