Issues moving from cento6 jira 7.9 to centos7 jira 7.12

[Grant Griffith]

I am working to upgrade and move our Jira instance to a new server running the newest version of Jira software.  I have been following the directions provided here but get an error when importing the XML backup.

https://confluence.atlassian.com/adminjiraserver079/backing-up-data-950288961.html

Anyone offer any assistance?  Also, once I get this tested and working.  I need to import new database and data files to update things.  Clues on how to best do that?

Error Details:

Error importing data: org.xml.sax.SAXException: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Action][updateauthor,albdavis][issue,10980][author,albdavis][created,2013-03-12 14:58:24.0][id,11213][type,comment][body,Thank you for your time on the call today! Here is summary of what we had discussed: • Replace current Funeral Home Finder with Search functionality: o Default to show all Members listed o Search box to search by Name  Results to show any Funeral home name that matches criteria (i.e. when searching for David J. Weber, if only “Weber” is typed in the box, David J. Weber would show as a result) o Search box to search by City o Search box to search by State  Would we want this to be a drop box? They currently have funeral homes in Maryland, Pennsylvania, and Delaware. • RCB: I concur with drop box. o Search box to search by Zip Code ACTION ITEM: - Would Karen have the ability to add/update/delete members? o RCB: Just need to add/remove a location. Already have this functionality in SiteMaker. - How do we classify District of Columbia funeral homes (by State)? o RCB: “District of Columbia” is a “state/province” already in our dropdown lists. The easiest, and probably most proper way to accomplish what MSFDA wants is to use the sitemaker.users and sitemaker.account_locations tables. If we got a CSV of needed data from MSFDA, we could bulk-import into site_locations, and do searches off of that quite easily. Bonus points for other funeral homes could use the same feature. General WLC: • 6h – RCB HTML templates for search page with required fields. Possibly include a Google Maps integration as well if time. • 6h – RCB WLC Application coding for site location search. • 3h – ??? Create Auto-Generate page for “site location search”. Optional, but why not give other customers the benefits, or “sell” it to other customers? • 6h – QA QA for new changes to site MSFDA-Specific: • 5h – RCB Import site location data from MSFDA’s CSV dump into sitemaker.site_locations table. o *Company Name o *Address 1 o Address 2 o *City o *State o *Zip o County o *Phone o Fax o *Email o Contact Name o Latitude/longitude if known. I still think that long term, customers will want the ability to search by “closeness”, which entails the addition of geo-spatial extentions into MySQL server as well as the sitemaker.users and sitemaker.account_locations tables. This is the way people search for businesses these days, and BI will be falling by the wayside if we do not provide “spatial” search capabilities of sites and funeral homes at some point. (IMO). Without Geo-Spatial capabilities, you CANNOT do the “find a funeral home 5/10/25 miles away from ZIPCODE/MyAddress”. A customer might search for a FH in their town, and fail to find a FH in the town next to theirs without being able to search “closeness.” However, I have quoted as requested per listed requirements.][updated,2013-03-12 14:58:24.0] (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\x82\xA7 Re...' for column 'actionbody' at row 1)) java.lang.Exception: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericEntityException: while inserting: [GenericEntity:Action][updateauthor,albdavis][issue,10980][author,albdavis][created,2013-03-12 14:58:24.0][id,11213][type,comment][body,Thank you for your time on the call today! Here is summary of what we had discussed: • Replace current Funeral Home Finder with Search functionality: o Default to show all Members listed o Search box to search by Name  Results to show any Funeral home name that matches criteria (i.e. when searching for David J. Weber, if only “Weber” is typed in the box, David J. Weber would show as a result) o Search box to search by City o Search box to search by State  Would we want this to be a drop box? They currently have funeral homes in Maryland, Pennsylvania, and Delaware. • RCB: I concur with drop box. o Search box to search by Zip Code ACTION ITEM: - Would Karen have the ability to add/update/delete members? o RCB: Just need to add/remove a location. Already have this functionality in SiteMaker. - How do we classify District of Columbia funeral homes (by State)? o RCB: “District of Columbia” is a “state/province” already in our dropdown lists. The easiest, and probably most proper way to accomplish what MSFDA wants is to use the sitemaker.users and sitemaker.account_locations tables. If we got a CSV of needed data from MSFDA, we could bulk-import into site_locations, and do searches off of that quite easily. Bonus points for other funeral homes could use the same feature. General WLC: • 6h – RCB HTML templates for search page with required fields. Possibly include a Google Maps integration as well if time. • 6h – RCB WLC Application coding for site location search. • 3h – ??? Create Auto-Generate page for “site location search”. Optional, but why not give other customers the benefits, or “sell” it to other customers? • 6h – QA QA for new changes to site MSFDA-Specific: • 5h – RCB Import site location data from MSFDA’s CSV dump into sitemaker.site_locations table. o *Company Name o *Address 1 o Address 2 o *City o *State o *Zip o County o *Phone o Fax o *Email o Contact Name o Latitude/longitude if known. I still think that long term, customers will want the ability to search by “closeness”, which entails the addition of geo-spatial extentions into MySQL server as well as the sitemaker.users and sitemaker.account_locations tables. This is the way people search for businesses these days, and BI will be falling by the wayside if we do not provide “spatial” search capabilities of sites and funeral homes at some point. (IMO). Without Geo-Spatial capabilities, you CANNOT do the “find a funeral home 5/10/25 miles away from ZIPCODE/MyAddress”. A customer might search for a FH in their town, and fail to find a FH in the town next to theirs without being able to search “closeness.” However, I have quoted as requested per listed requirements.][updated,2013-03-12 14:58:24.0] (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\x82\xA7 Re...' for column 'actionbody' at row 1))

[KellyW]

Hi Grant,

The error "Incorrect string value: '\xEF\x82\xA7 Re...' for column 'actionbody' at row 1" seems to suggest issue with the database encoding.

Check out this KB -- SQL Exception while updating issues or importing data in JIRA applications with MySQL due to encoding and confirm if this is applicable to your use case.

Regards,
Kelly

[Grant Griffith]

This doesn't appear to be the issue as I checked the database and all looks ok.  Can I use mysql msdump to backup data and import it that way to finish my move to a new server?