Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Deleted user
0 / 0 points
Next:
badges earned

Your Points Tracker
Challenges
Leaderboard
  • Global
  • Feed

Badge for your thoughts?

You're enrolled in our new beta rewards program. Join our group to get the inside scoop and share your feedback.

Join group
Recognition
Give the gift of kudos
You have 0 kudos available to give
Who do you want to recognize?
Why do you want to recognize them?
Kudos
Great job appreciating your peers!
Check back soon to give more kudos.

Past Kudos Given
No kudos given
You haven't given any kudos yet. Share the love above and you'll see it here.

It's not the same without you

Join the community to find out what other Atlassian users are discussing, debating and creating.

Atlassian Community Hero Image Collage

Error on import to MySQL 8, "Row size too large": AO_78C957_CONFIG Edited

Hello,

I have an XML backup from Jira (v8.1.0) using an Oracle 12c database that I am trying to import into a new Jira Server (v8.16.1) with a MySQL 8.0.25 database.

The import fails on this SQL statement with this error message:

"Row size too large. The maximum row size for the used table type, not counting BLOBs, is 65535. This includes storage overhead, check the manual. You have to change some columns to TEXT or BLOBs"

CREATE TABLE AO_78C957_CONFIG (
ADDED_EMAIL_NAME_FORMAT VARCHAR(255),
ADD_ATTACH_FILE_LINKS BOOLEAN,
ADD_ATTACH_IMG_LINKS BOOLEAN,
ADD_EMAIL_TO_ISSUE BOOLEAN,
ADD_EMAIL_TO_ISSUE_COND VARCHAR(255),
ADD_ORIG_EMAIL_BODY_TO_ISSUE VARCHAR(255),
ADD_SENDER_AS_WATCHER BOOLEAN,
ALLOW_ANONYMOUS_COMMENTING BOOLEAN,
ALTERNATE_ID_PROVIDER_KEY VARCHAR(255),
ASSIGNEE_FIRST_VALID_USER BOOLEAN,
ASSIGN_JIRA_USER_EMAIL_CF VARCHAR(255),
ASSIGN_JIRA_USER_NAME_CF VARCHAR(255),
ASSIGN_NON_JIRA_USER_EMAIL_CF VARCHAR(255),
ASSIGN_NON_JIRA_USER_NAME_CF VARCHAR(255),
AUTO_FLUSH_MAIL_QUEUE BOOLEAN,
AUTO_JOIN_GROUPS LONGTEXT,
AUTO_JOIN_GROUP_COND VARCHAR(255),
BLACKLISTED_ATTACHMENT_TYPES LONGTEXT,
BLACKLIST_DIRECTIVES LONGTEXT,
BLACKLIST_HANDLING VARCHAR(255),
BLACKLIST_RECIPIENTS LONGTEXT,
BLACKLIST_SENDERS LONGTEXT,
BODY_CLEANUP_REGEXPS LONGTEXT,
BODY_DELIMITER_REGEXPS LONGTEXT,
BODY_FORMAT_PREFERENCE VARCHAR(255),
BULK_HANDLING_ACTION VARCHAR(255),
CATCH_EMAIL_ADDRESS LONGTEXT,
CCHANDLING VARCHAR(255),
CCHANDLING_JIRA_USERS_CF VARCHAR(255),
CCHANDLING_NON_JIRA_USERS_CF VARCHAR(255),
COMMENT_VISIBILITY VARCHAR(255),
COMMENT_VISIBILITY_FOR_GROUPS BOOLEAN,
COMPONENT VARCHAR(255),
CREATED DATETIME,
CREATED_BY VARCHAR(255),
CREATE_USERS BOOLEAN,
CREATE_USERS_EMAIL_BLACKLIST LONGTEXT,
CREATE_USERS_EMAIL_WHITELIST LONGTEXT,
CREATE_USERS_IDFROM VARCHAR(255),
CREATE_USER_SIGNUP_EMAIL BOOLEAN,
CUSTOM_EMAIL_FROM_ADDRESS VARCHAR(255),
CUSTOM_EMAIL_FROM_NAME VARCHAR(255),
CUSTOM_EVENT_ON_COMMENT INTEGER,
CUSTOM_EVENT_ON_CREATE INTEGER,
DATE_FORMATS LONGTEXT,
DATE_TIME_FORMATS LONGTEXT,
DEBUG_PRINT_EMAIL BOOLEAN,
DEFAULT_DUE_DATE_DAYS VARCHAR(255),
DIRECTIVE_PROCESSING_BEHAVIOUR VARCHAR(255),
DROP_BLACKLIST_MATCHES BOOLEAN,
DROP_GREYLIST_SUBJECT_MATCHES BOOLEAN,
DUE_DATE_FORMAT VARCHAR(255),
EAT_EMPTY_BODY_LINES_MAX INTEGER,
EMAIL_SENT_DATE_CF VARCHAR(255),
ENABLE_AUTO_ISSUE_ASSIGNEE BOOLEAN,
FORCE_USER_ID_CASE VARCHAR(255),
FORWARD_TMPL_ID INTEGER,
FORWARD_USER VARCHAR(255),
GREYLIST_EMAIL_BODY_REGEXP LONGTEXT,
GREYLIST_SENDERS LONGTEXT,
GREYLIST_SUBJECT_REGEXPS LONGTEXT,
HIDE_HTML_LINKS BOOLEAN,
HINTOGRAM_ENABLED BOOLEAN,
HINTOGRAM_TMPL_ID INTEGER,
HTML_BLKQT_TAG_HANDLING VARCHAR(255),
HTML_BREAK_TAG_HANDLING VARCHAR(255),
HTML_CODE_TAG_HANDLING VARCHAR(255),
HTML_DIV_TAG_HANDLING VARCHAR(255),
HTML_EXTRACT_METHOD VARCHAR(255),
HTML_HEADING_LEVEL VARCHAR(255),
HTML_HR_TAG_HANDLING VARCHAR(255),
HTML_IMAGE_ATTRIBUTES VARCHAR(255),
HTML_IMAGE_HANDLING VARCHAR(255),
HTML_IMG_TAG_HANDLING VARCHAR(255),
HTML_LINK_HANDLING VARCHAR(255),
HTML_PARA_TAG_HANDLING VARCHAR(255),
HTML_PRE_TAG_HANDLING VARCHAR(255),
HTML_SPAN_TAG_HANDLING VARCHAR(255),
HTML_TABLE_TAG_HANDLING VARCHAR(255),
ID INTEGER AUTO_INCREMENT,
IGNORE_SUBJECT_ISSUE_KEYS BOOLEAN,
INDICATE_ACTIVE_PROCESSOR BOOLEAN,
INDICATE_SOURCED_BY_EMAIL BOOLEAN,
ISSUE_ATTACHMENTS_ENABLED BOOLEAN,
ISSUE_COMMENT_LIMIT INTEGER,
ISSUE_COMMENT_LIMIT_ACTION VARCHAR(255),
ISSUE_COMMENT_MAX_KB INTEGER,
ISSUE_CREATED_TMPL_ID INTEGER,
ISSUE_LINK_TYPE VARCHAR(255),
ISSUE_SECURITY_LEVEL VARCHAR(255),
ISSUE_TYPE VARCHAR(255),
JEMHPROFILE_ENTITY_ID INTEGER,
JEMH_ADDRESSEE_REGEXPS LONGTEXT,
`LABEL` VARCHAR(255),
LDAP_CONFIG_ID INTEGER,
NON_CATCHMAIL_MATCH_ACTION VARCHAR(255),
NON_JIRA_ISSUE_FORMAT VARCHAR(255),
NORMALISE_NEWLINES BOOLEAN,
NOTIFY_USERS BOOLEAN,
NOTIFY_USERS_ON_ISSUE_CREATION VARCHAR(255),
NO_COMMENT_HDR_ADDRESSES LONGTEXT,
ON_COMMENT_ADVANCE_ACTION VARCHAR(255),
ON_COMMENT_ADVANCE_FROM_STATES VARCHAR(255),
ON_COMMENT_DELIM_REGEXPS LONGTEXT,
ON_COMMENT_EVENT_BEHAVIOUR VARCHAR(255),
OVERRIDE_HINT_EML_ADDRESS VARCHAR(255),
OVERRIDE_USER_NOTIFY_SELF BOOLEAN,
PRE_VALIDATE_CF_VALUES BOOLEAN,
PRIORITY VARCHAR(255),
PRIVILEGED_USER VARCHAR(255),
PROJECT VARCHAR(255),
PROJECT_AUTO_ASSIGN BOOLEAN,
PROJ_ASSIGN_FROM_SUBJ VARCHAR(255),
REPORTER_OVERRIDES_DERIVED BOOLEAN,
REPORTER_USER_NAME VARCHAR(255),
SOURCED_BY_TMPL_ID INTEGER,
STRICT_JIRA_PERMISSIONS BOOLEAN,
STRIP_QUOTES BOOLEAN,
SUBJECT_CLEANUP_REGEXPS LONGTEXT,
SUBJECT_ISSUE_KEY_REGEXP VARCHAR(255),
SUMMARY VARCHAR(255),
THRD_PTY_CF_GEN_HNDL BOOLEAN,
THREAD_CHECK_DISABLED BOOLEAN,
THREAD_MATCH_LIMIT VARCHAR(255),
TREAT_UNPRIV_AS_NON_JIRA BOOLEAN,
UPDATED DATETIME,
UPDATED_BY VARCHAR(255),
UPDATE_WITH_COMMENTS_ARE_UPD BOOLEAN,
USER_CREATE_TMPL_ID INTEGER,
USE_EMAIL_SENDER_FOR_SECURITY BOOLEAN,
USE_FIRST_WORD_WORKFLOW_NAME BOOLEAN,
USE_GENERIC_EVENT_ENABLED BOOLEAN,
USE_REPROCESSED_MESSAGE BOOLEAN,
USE_SUB_ADDRESSES BOOLEAN,
WHITELISTED_ATTACHMENT_TYPES LONGTEXT,
WHITELIST_DIRECTIVES LONGTEXT,
WHITELIST_SENDERS LONGTEXT,
WORKFLOW_ADVANCE_ACTION VARCHAR(255),
WORKFLOW_RESOLUTION VARCHAR(255),
WORKLOG_SECURITY_GROUP VARCHAR(255),
WORKLOG_SECURITY_ROLE VARCHAR(255),
XSPAM_FLAG_HANDLING VARCHAR(255),
PRIMARY KEY(ID)
) ENGINE=InnoDB

I have followed the Connecting Jira applications to MySQL 8.0 guide, however I am unable to set innodb_log_file_size to 2G, because I am using the MySQL DB System in Oracle Cloud, and it looks like that parameter cannot be modified.  (It is currently set to 1G.)

Would this parameter be causing the creation of this table to fail?

What options do I have to get around / fix this issue?

Thanks!

 

0 answers

Suggest an answer

Log in or Sign up to answer
DEPLOYMENT TYPE
SERVER
TAGS
Community showcase
Published in Jira Service Management

JSM June Challenge #2: Share how your business teams became ITSM rockstars

For JSM June Challenge #2, share how your non-technical teams like HR, legal, marketing, finance, and beyond started using Jira Service Management! Tell us: Did they ask to start using it or...

203 views 6 7
Read article

Community Events

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

Find an event

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

Unfortunately there are no Community Events near you at the moment.

Host an event

You're one step closer to meeting fellow Atlassian users at your local event. Learn more about Community Events

Events near you