-
Type:
Bug
-
Resolution: Fixed
-
Priority:
Low
-
None
-
Affects Version/s: None
-
Component/s: Jira - Migration Assistant - Export
-
None
-
1
-
Severity 3 - Minor
Issue Summary
JCMA : Error "Communicating With Server and There Was A Problem Retrieving Your Plans" when the timestamp format is incorrectly set in the database.
Investigation
- Expected default TIMEZONE format: 'DD-MON-RR HH.MI.SSXFF AM'
dd-MMM-yy hh:mm:ss.SSS a (e.g. 01-Jan-70 12:00:00.000 AM - as we see in the failing CREATE TABLE statement)
- Any other parameter for the 'NLS_TIMESTAMP_FORMAT' like DD-MON-RR HH24.MI.SSXFF are not accepted by the JCMA plugin.
DB query to get the 'NLS_TIMESTAMP_FORMAT' Values from the server
SELECT
value
FROM
V$NLS_PARAMETERS
WHERE
parameter = 'NLS_TIMESTAMP_FORMAT';
Error Logs from Support.zip
2020-04-03 09:47:13,074 active-objects-init-JiraTenantImpl{id='system'}-0 DEBUG sean.haskell [c.a.activeobjects.osgi.TenantAwareActiveObjects] bundle [com.atlassian.jira.migration.jira-migration-plugin] creating ActiveObjects
2020-04-03 09:47:13,324 active-objects-init-JiraTenantImpl{id='system'}-0 ERROR sean.haskell [n.java.ao.sql] Exception executing SQL update <CREATE TABLE "AO_6FF49D_PLAN_ENTITY" (
"CREATED" TIMESTAMP DEFAULT '01-Jan-70 12:00:00.000 AM',
"ID" VARCHAR(36) NOT NULL,
"JSON" CLOB,
"PLAN_NAME" VARCHAR(255) CONSTRAINT U_AO_6FF49D_PLAN_EN548125492 UNIQUE NOT NULL,
"UPDATED" TIMESTAMP DEFAULT '01-Jan-70 12:00:00.000 AM',
PRIMARY KEY("ID")
)>
java.sql.SQLDataException: ORA-01830: date format picture ends before converting entire input string
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1149)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:624)
at java.lang.Thread.run(Thread.java:748)
Caused by: Error : 1830, Position : 71, Sql = CREATE TABLE "AO_6FF49D_PLAN_ENTITY" (
"CREATED" TIMESTAMP DEFAULT '01-Jan-70 12:00:00.000 AM',
"ID" VARCHAR(36) NOT NULL,
"JSON" CLOB,
"PLAN_NAME" VARCHAR(255) CONSTRAINT U_AO_6FF49D_PLAN_EN548125492 UNIQUE NOT NULL,
"UPDATED" TIMESTAMP DEFAULT '01-Jan-70 12:00:00.000 AM',
), OriginalSql = CREATE TABLE "AO_6FF49D_PLAN_ENTITY" (
"CREATED" TIMESTAMP DEFAULT '01-Jan-70 12:00:00.000 AM',
"ID" VARCHAR(36) NOT NULL,
"JSON" CLOB,
"PLAN_NAME" VARCHAR(255) CONSTRAINT U_AO_6FF49D_PLAN_EN548125492 UNIQUE NOT NULL,
"UPDATED" TIMESTAMP DEFAULT '01-Jan-70 12:00:00.000 AM',
PRIMARY KEY("ID")
), Error Msg = ORA-01830: date format picture ends before converting entire input string
at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:498)
... 64 more
2020-04-03 09:47:13,324 active-objects-init-JiraTenantImpl{id='system'}-0 WARN sean.haskell [n.j.ao.db.OracleDatabaseProvider] Error in schema creation: ORA-01830: date format picture ends before converting entire input string
; attempting to roll back last partially generated table
2020-04-03 09:47:13,324 active-objects-init-JiraTenantImpl{id='system'}-0 WARN sean.haskell [c.a.activeobjects.osgi.TenantAwareActiveObjects] bundle [com.atlassian.jira.migration.jira-migration-plugin] failed to create ActiveObjects
com.atlassian.activeobjects.internal.ActiveObjectsSqlException: There was a SQL exception thrown by the Active Objects library:
Database:
- name:Oracle
- version:Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production
With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options
- minor version:1
- major version:12
Driver:
- name:Oracle JDBC driver
- version:12.2.0.1.0
Any additional Details
-> Jira Version :
<product name="Jira" version="8.3.3"/>
-> Plugin version used:
</plugin>
<plugin>
<key>com.atlassian.jira.migration.jira-migration-plugin</key>
<name>Jira Cloud Migration Assistant</name>
<version>1.1.0</version>
<vendor>Atlassian</vendor>
<status>ENABLED</status>
<vendor-url>https://www.atlassian.com/</vendor-url>
<framework-version>2</framework-version>
<bundled>User installed</bundled>
-> Database in use :
<Database-type>oracle10g</Database-type>
<Database-JNDI-address>oracle10g jdbc:oracle:thin:@//jirac01-zvtsdb95:1521/jira</Database-JNDI-address>
<Database-URL>Hidden</Database-URL>
<Database-version>Oracle Database 12c Enterprise Edition Release 12.1.0.2.0 - 64bit Production With the Partitioning, OLAP, Advanced Analytics and Real Application Testing options</Database-version>
Workaround
Currently, there is no known workaround for this behavior. A workaround will be added here when available
