We have a mysql cluster 7.4.6 with 4 data node on production environment. Last weekend we needed to change several tables, data type in particular. The first change (integer to smallint) Got error 4239 'Trigger with given name already exists' from NDBCLUSTER. We have set MaxNoOfTriggers to 100000.
We had read the metalink document
"What Are MySQL Cluster Triggers And How To Monitor Them? (Doc ID 2181749.1)"
when we run the next query on our production system
"SELECT * FROM ndbinfo.ndb$pools WHERE pool_name LIKE '%rigger%'"
Sorry, you can't reply to this topic. It has been closed.
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.