Uploaded image for project: 'Jira Data Center'
  1. Jira Data Center
  2. JRASERVER-78404

Jira upgrade to 10.3.x shows SQL Exception error ORA-01735: invalid ALTER TABLE option

XMLWordPrintable

    • Icon: Bug Bug
    • Resolution: Fixed
    • Icon: Medium Medium
    • 10.3.4
    • 10.3.0
    • Upgrade

      Issue Summary

      When upgrading from Jira 9.4.x. or 9.12.x to 10.3.x, the application starts successfully.
      However, the application log shows the following SQL exception error:

      2025-01-15 15:41:09,491+0000 main ERROR      [o.o.c.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
          ALTER TABLE jiraaction MODIFY CREATED TIMESTAMP(6), MODIFY UPDATED TIMESTAMP(6)
          Error was: java.sql.SQLSyntaxErrorException: ORA-01735: invalid ALTER TABLE option 

      Those are failing SQL statement:

      ALTER TABLE jiraaction MODIFY CREATED TIMESTAMP(6), MODIFY UPDATED TIMESTAMP(6);
      ALTER TABLE jiraissue MODIFY CREATED TIMESTAMP(6), MODIFY UPDATED TIMESTAMP(6);
      

      Steps to Reproduce

      1. Install Jira 9.12.14
      2. Perform a manual upgrade to Jira 10.3.0 following the upgrade documentation

      Expected Results

      The upgraded Jira application should start successfully without any SQL exception errors.

      Actual Results

      • The upgraded Jira 10.3.0 application starts successfully
      • However, the application log shows the following error:
        2025-01-15 15:41:09,491+0000 main ERROR      [o.o.c.entity.jdbc.DatabaseUtil] SQL Exception while executing the following:
            ALTER TABLE jiraaction MODIFY CREATED TIMESTAMP(6), MODIFY UPDATED TIMESTAMP(6)
            Error was: java.sql.SQLSyntaxErrorException: ORA-01735: invalid ALTER TABLE option

      Environment

      • Database: Oracle
      • Upgrade Path: Jira 9.12.14 to 10.3.0

      Workaround

      You can execute failing SQL statements manually just before starting the application:

      ALTER TABLE jiraaction MODIFY CREATED TIMESTAMP(6);
      ALTER TABLE jiraaction MODIFY UPDATED TIMESTAMP(6);
      ALTER TABLE jiraissue MODIFY CREATED TIMESTAMP(6);
      ALTER TABLE jiraissue MODIFY UPDATED TIMESTAMP(6);
      

      This fixes the problem.

              jxu2@atlassian.com Sam Xu
              02a6ae09c2cc Cecille Maquito (Inactive)
              Votes:
              3 Vote for this issue
              Watchers:
              23 Start watching this issue

                Created:
                Updated:
                Resolved: