• Community
  • Products
  • Jira
  • Questions
  • JIRA import error : Verify that Publisher will be able to insert accessible data tables for data and for layout, and cont

JIRA import error : Verify that Publisher will be able to insert accessible data tables for data and for layout, and cont

Hi Team,

I notice this error when I was importing a backup data xml file to my DEV box.

Current DEV box is installed with JIRA 4.2.1

Below are snapshot of error logs :

------------------------------------------------------------

2012-09-10 09:41:31,085 http-8080-7 INFO n100123 581x142x1 hc92cw 144.136.126.43 /secure/admin/XmlRestore.jspa jira.action.admin.DataImport Running JIRA Data Import...

2012-09-10 09:41:31,166 http-8080-7 INFO n100123 581x142x1 hc92cw 144.136.126.43 /secure/admin/XmlRestore.jspa jira.action.admin.DataImport Importing XML data...

2012-09-10 09:41:31,166 http-8080-7 INFO n100123 581x142x1 hc92cw 144.136.126.43 /secure/admin/XmlRestore.jspa jira.action.admin.DataImport Start parsing XML with SAX Parser.

2012-09-10 09:42:08,640 http-8080-7 INFO n100123 581x142x1 hc92cw 144.136.126.43 /secure/admin/XmlRestore.jspa jira.action.admin.DataImport XML successfully parsed.

2012-09-10 09:42:08,643 http-8080-7 INFO n100123 581x142x1 hc92cw 144.136.126.43 /secure/admin/XmlRestore.jspa jira.action.admin.DataImport Removing all entries from the database.

2012-09-10 09:42:09,507 http-8080-7 INFO n100123 581x142x1 hc92cw 144.136.126.43 /secure/admin/XmlRestore.jspa jira.action.admin.DataImport All entries removed.

2012-09-10 09:42:09,508 http-8080-7 INFO n100123 581x142x1 hc92cw 144.136.126.43 /secure/admin/XmlRestore.jspa jira.action.admin.DataImport Started storing 2247548 Generic Values.

2012-09-10 09:54:58,708 pool-5-thread-9 ERROR n100123 581x142x1 hc92cw 144.136.126.43 /secure/admin/XmlRestore.jspa jira.action.admin.OfbizImportHandler Exception importing entity: org.of

biz.core.entity.GenericEntityException: while inserting: GenericEntity:Issue summary,Verify that Publisher will be able to insert accessible data tables for data and for layout, and cont

rol:

⢠Table properties, (number Rows & columns, Width (%, px), Horizontal alignment, Border colour, size, cell padding, cell spacing, Background col... id,10344 project,10000 updated,2010-0422 14:04:37.0 created,2010-04-22 13:53:29.0 status,10000 workflowId,10777 votes,0 type,8 key,THP-345 (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, PR

OJECT, REPORTER, ASSIGNEE, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, TIMEORIGINALESTIMATE, TIMEESTIM

ATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (ORA-12899: value too large for column JIRADEV.J

IRAISSUE.SUMMARY (actual: 256, maximum: 255)

))

org.ofbiz.core.entity.GenericEntityException: while inserting: GenericEntity:Issue summary,Verify that Publisher will be able to insert accessible data tables for data and for layout, an

d control:

⢠Table properties, (number Rows & columns, Width (%, px), Horizontal alignment, Border colour, size, cell padding, cell spacing, Background col... id,10344 project,10000 updated,2010-0422 14:04:37.0 created,2010-04-22 13:53:29.0 status,10000 workflowId,10777 votes,0 type,8 key,THP-345 (SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, PR

OJECT, REPORTER, ASSIGNEE, issuetype, SUMMARY, DESCRIPTION, ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, TIMEORIGINALESTIMATE, TIMEESTIM

ATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VALUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (ORA-12899: value too large for column JIRADEV.J

IRAISSUE.SUMMARY (actual: 256, maximum: 255)

))

at org.ofbiz.core.entity.GenericDAO.singleInsert(GenericDAO.java:149)

at org.ofbiz.core.entity.GenericDAO.insert(GenericDAO.java:114)

at org.ofbiz.core.entity.GenericHelperDAO.create(GenericHelperDAO.java:63)

at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:480)

at org.ofbiz.core.entity.GenericDelegator.create(GenericDelegator.java:460)

at org.ofbiz.core.entity.GenericValue.create(GenericValue.java:77)

at com.atlassian.jira.action.admin.OfbizImportHandler$1.run(OfbizImportHandler.java:471)

at com.atlassian.jira.util.concurrent.BoundedExecutor$1.run(BoundedExecutor.java:42)

at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(Unknown Source)

at java.util.concurrent.ThreadPoolExecutor$Worker.run(Unknown Source)

at java.lang.Thread.run(Unknown Source)

org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:INSERT INTO jiraissue (ID, pkey, PROJECT, REPORTER, ASSIGNEE, issuetype, SUMMARY, DESCRIPTION,

ENVIRONMENT, PRIORITY, RESOLUTION, issuestatus, CREATED, UPDATED, DUEDATE, RESOLUTIONDATE, VOTES, TIMEORIGINALESTIMATE, TIMEESTIMATE, TIMESPENT, WORKFLOW_ID, SECURITY, FIXFOR, COMPONENT) VA

LUES (?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?, ?) (ORA-12899: value too large for column JIRADEV.JIRAISSUE.SUMMARY (actual: 256, maximum: 255)

)

1 answer

1 accepted

0 vote

That sounds like someone has been messing with the database in your old Jira - they've extended the length of the summary field and broken it. Or the xml is corrupt.

For corrupt xml, try exporting it again, but also, open the xml in a text editor and check it. Ideally, use an xml editor, as most of them will also be able to validate it and scan for errors.

If it's a hacked database, then you need to go back to your old installation and check what they've changed. Start with the entitengine.xml as that defines how Jira talks to the database. You'll also need to establish what code they've changed to allow the java to work with summaries over 255 characters.

Suggest an answer

Log in or Sign up to answer
How to earn badges on the Atlassian Community

How to earn badges on the Atlassian Community

Badges are a great way to show off community activity, whether you’re a newbie or a Champion.

Learn more
Community showcase
Posted Wednesday in Jira

Join our webinar: How 1B+ feature flag events helped us build the new Jira

Every time you release software, there's a bit of risk – that there's a bug, that something breaks, or that the feature doesn't resonate with customers. Feature flagging helps make high stakes s...

134 views 0 3
Join discussion

Atlassian User Groups

Connect with like-minded Atlassian users at free events near you!

Find a group

Connect with like-minded Atlassian users at free events near you!

Find my local user group

Unfortunately there are no AUG chapters near you at the moment.

Start an AUG

You're one step closer to meeting fellow Atlassian users at your local meet up. Learn more about AUGs

Groups near you