You're on your way to the next level! Join the Kudos program to earn points and save your progress.
Level 1: Seed
25 / 150 points
Next: Root
1 badge earned
Challenges come and go, but your rewards stay with you. Do more to earn more!
What goes around comes around! Share the love by gifting kudos to your peers.
Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!
Join now to unlock these features and more
The Atlassian Community can help you and your team get more value out of Atlassian products and practices.
Hi,
We are trying to migrate JIRA from windows to linux, JIRA installation has done on linux machine JIRA version 7.
We have copied attachments directory from windows to linux server, facing issue while restoring XML backup zip formate getting below error please suggest.
As checked on windows JIRA "dbconfig.xml" it's using HSQL database, On linux JIRA using MYSQL.
Error importing data: org.xml.sax.SAXException: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Action][updateauthor,meenu][issue,14069][author,meenu][created,2015-02-24 18:57:53.037][id,14091][type,comment][body, Queue panel to be shifted upwards, below the NDNC panel.(Links in the admin panel would be displayed by priority.)---new Search option on click Enter--new On demand refresh button on the queue panel(Ph 2)--new Clickable are on the queue panel needs to be on the entire row.--New A call to be marked as missed Call Back in the queue panel.—New Pull time column too be added on the queue panel.----New ][updated,2015-02-24 18:57:53.037] (SQL Exception while executing the following:INSERT INTO jiraaction (ID, issueid, AUTHOR, actiontype, actionlevel, rolelevel, actionbody, CREATED, UPDATEAUTHOR, UPDATED, actionnum) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xEF\x83\x98\x09Qu...' for column 'actionbody' at row 1)) java.lang.Exception: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Action][updateauthor,meenu][issue,14069][author,meenu][created,2015-02-24 18:57:53.037][id,14091][type,comment][body, Queue panel to be shifted upwards, below the NDNC panel.(Links in the admin panel would be displayed by priority.)---new Search option on click Enter--new On demand refresh button on the queue panel(Ph 2)--new Clickable are on the queue panel needs to be on the entire row.--New A call to be marked as missed Call Back in the queue panel.—New Pull time column too be added on the queue panel.----New ][updated,2015-02-24 18:57:53.037] (SQL Exception while executing the following:INSERT INTO jiraaction (ID, issueid, AUTHOR, actiontype, actionlevel, rolelevel, actionbody, CREATED, UPDATEAUTHOR, UPDATED, actionnum) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (Incorrect string value: '\xEF\x83\x98\x09Qu...' for column 'actionbody' at row 1))
Regards,
Vivek Pal.
This is caused by an incorrect collation set in the database, please see https://confluence.atlassian.com/display/JIRAKB/SQL+Exception+while+updating+issues+or+importing+data+in+JIRA+applications+with+MySQL+due+to+encoding for the fix.
Thanks David, Now issue has been resolved we have recreated database with utf-8. it's working fine. Thanks.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
What if I have exactly same issue using MS SQL? All settings done same as provided on website guide.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Getting same error for PostgreSQL to MS SQL migration.
Error importing data: org.xml.sax.SAXException: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:IssueLinkType][inward,is duplicated by][id,10000][linkname,Duplicate][outward,duplicates] (SQL Exception while executing the following:INSERT INTO JiraProdSchema.issuelinktype (ID, LINKNAME, INWARD, OUTWARD, pstyle) VALUES (?, ?, ?, ?, ?) (Violation of PRIMARY KEY constraint 'PK_issuelinktype'. Cannot insert duplicate key in object 'JiraProdSchema.issuelinktype'. The duplicate key value is (10000).)) java.lang.Exception: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:IssueLinkType][inward,is duplicated by][id,10000][linkname,Duplicate][outward,duplicates] (SQL Exception while executing the following:INSERT INTO JiraProdSchema.issuelinktype (ID, LINKNAME, INWARD, OUTWARD, pstyle) VALUES (?, ?, ?, ?, ?) (Violation of PRIMARY KEY constraint 'PK_issuelinktype'. Cannot insert duplicate key in object 'JiraProdSchema.issuelinktype'. The duplicate key value is (10000).))
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Team
Once you delete something in Jira you have lost that data forever be it issues, attachments or any of the configuration objects.
Thats what inspired us at Revyz to build an app for simplifying backing up your cloud Jira instance which includes issues, attachments, comments, configuration objects and more.
Please visit our market place page to see all things we can help you with protecting your data in your Jira cloud instance - Revyz Backup & Restore
Additional information is also available at - Revyz Backup & Restore for Jira Software Cloud
Also note Atlassian recommends that you backup your data per the SaaS Shared responsibilities
I would love to get your feedback on what we are doing and how to improve given an opportunity.
Thank you
Vish
Reference -
Atlassian, Customer Shared Responsibilities - Very good reference doc
Atlassian Security Practices - An excellent reference of Atlassian Security practices
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
do you check the database user defined in dbconfig.xml exist in your MySQL server?
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.