Bug #18867 MaxConcurrentTransactions Exceeded when doing big delete from table

Submitted: 6 Apr 2006 19:37 Modified: 6 Apr 2006 19:39
Reporter: Kris Buytaert (Candidate Quality Contributor) Email Updates:
Status: Not a Bug Impact on me:
None 
Category:MySQL Server Severity:S3 (Non-critical)
Version:5.1.6 alpha OS:Linux (Linux)
Assigned to: CPU Architecture:Any

[6 Apr 2006 19:37] Kris Buytaert
Description:
When testing ndb_cluster disk storage  I run into the following error when trying to delete everything a "big" table

(t1) as described in Michael 's blog entry.

ql> select count(*) from t1;
+----------+
| count(*) |
+----------+
|   394958 |
+----------+
1 row in set (0.00 sec)

mysql> delete from table t1;
ERROR 1064 (42000): You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near 'table  t1' at line 1
mysql> delete from t1;
ERROR 1297 (HY000): Got temporary error 233 'Out of operation records in transac tion coordinator (increase MaxNoOfConcurrentOperations)' from NDBCLUSTER

Simply dropping the table works

How to repeat:
Create table filled with single values  fill it with about 394958 entries,
then delete them..
[6 Apr 2006 19:39] Jonas Oreland
Hi,

This is not a bug.
It's documented in limitations section.

The work around is to use "truncate" instead.
[6 Apr 2006 19:42] Jonas Oreland
see
http://dev.mysql.com/doc/refman/5.0/en/mysql-cluster-limitations.html

and search for truncate (on this page only)

Portions of this website are copyright © 2001, 2002 The PHP Group

Page generated in 0.039 sec. using MySQL 8.4.7-u6-cloud

Timestamp references displayed by the system are UTC.
Content reproduced on this site is the property of the respective copyright holders.
It is not reviewed in advance by Oracle and does not necessarily represent the opinion of Oracle or any other party.