MySQL error

Hi Experts,

We are getting below error while performing Bulk Insert operation on MySQL DB. Please suggest how to fix below error.

MySQL version : 5.1
NDB version: 7.3.2

Error:
[com.ericsson.reflection.app.dto.TxTaskTagRel]; uncategorized SQLException for SQL [insert into TX_TASK_TAG_REL (ACTIVE, APPEARANCE_MANDATORY, ENTRY_STATE, GUI_COLUMN, GUI_DISPLAY_ORDER, GUI_ROW, INPUT_MANDATORY, OTHER_VALUE, TAG_ID, TAG_LABEL, TAG_VALUE, TX_TASK_ID, VALUE_GROUP_ID, ID) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)]; SQL state [HY000]; error code [1297]; Got temporary error 899 'Rowid already allocated' from NDBCLUSTER; nested exception is java.sql.BatchUpdateException: Got temporary error 899 'Rowid already allocated' from NDBCLUSTER"

Please advise.
sqldba2013Asked:
Who is Participating?
I wear a lot of hats...

"The solutions and answers provided on Experts Exchange have been extremely helpful to me over the last few years. I wear a lot of hats - Developer, Database Administrator, Help Desk, etc., so I know a lot of things but not a lot about one thing. Experts Exchange gives me answers from people who do know a lot about one thing, in a easy to use platform." -Todd S.

chaauCommented:
Looks like a bug in MySQL. According to the bug report it has been fixed. Any chance for you to update your MySQl server?
0

Experts Exchange Solution brought to you by

Your issues matter to us.

Facing a tech roadblock? Get the help and guidance you need from experienced professionals who care. Ask your question anytime, anywhere, with no hassle.

Start your 7-day free trial
sqldba2013Author Commented:
We are getting above error when we execute Bulk insert command.

We are not getting error when we insert single row data using insert command
ex:
[insert into TX_TASK_TAG_REL (ACTIVE, APPEARANCE_MANDATORY, ENTRY_STATE, GUI_COLUMN, GUI_DISPLAY_ORDER, GUI_ROW, INPUT_MANDATORY, OTHER_VALUE, TAG_ID, TAG_LABEL, TAG_VALUE, TX_TASK_ID, VALUE_GROUP_ID, ID) values (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?)];

is this error is related to Bug in mysql?
0
chaauCommented:
According to the closing comments for the bug report:
- Error code 899 is considered a TEMPORARY error, clients should retry (potentially after a small delay) on encountering it (like with all temp errors)
- Error code 899 may be returned on INSERT operations during node recovery.
- Error code 899 may be returned on INSERT operations on DD tables in 6.3
- All other known causes of error 899 are fixed, but may still be present in older versions
- There may be currently unknown causes of error 899.
I guess the workaround is to retry (potentially after a small delay) on encountering it (like with all temp errors)
0
Ultimate Tool Kit for Technology Solution Provider

Broken down into practical pointers and step-by-step instructions, the IT Service Excellence Tool Kit delivers expert advice for technology solution providers. Get your free copy now.

sqldba2013Author Commented:
Once again Thanks for your suggestion.

We are facing below issue from past one month on prod server. Few days back we have retried and its successful and today again we got above error.

We need to fix this error permanently.  Can you share permanent solution for above error?
0
chaauCommented:
They say that they fixed it:
We fixed a couple of cases for 899 in 7.2.14. This maintenance version should come out any day from now. I'll be closing this bug now. If you still encounter 899 after the update then we are highly interested to hear from you.
Looks like it still exists. I recommend you contacting the MySQL team directly by logging the bug into their system. You can use the Bug #69938 as a reference to your log
0
gheistCommented:
How you got it working with MySQL 5.1?
https://dev.mysql.com/doc/relnotes/mysql-cluster/7.3/en/mysql-cluster-news-7-3-series.html - it is MySQL 5.6
0
sqldba2013Author Commented:
Please find Mysql version

5.6.11-ndb-7.3.2-cluster-gpl

Please advise on above error.
0
gheistCommented:
As spotted by other experts before - you should retry if 899 is returned
Also spotted that some 899 is fixed - so upgrade to 7.3.7 may help to avoid 899 but not in all cases
Choose action which is easiest for you.
0
It's more than this solution.Get answers and train to solve all your tech problems - anytime, anywhere.Try it for free Edge Out The Competitionfor your dream job with proven skills and certifications.Get started today Stand Outas the employee with proven skills.Start learning today for free Move Your Career Forwardwith certification training in the latest technologies.Start your trial today
MySQL Server

From novice to tech pro — start learning today.

Question has a verified solution.

Are you are experiencing a similar issue? Get a personalized answer when you ask a related question.

Have a better answer? Share it in a comment.