com.atlassian.jira.exception.DataAccessException: Unable to complete the export due to an error in the cloning command 2016-09-12 19:21:39.562605500 at com.atlassian.jira.config.database.export.AbstractExportDatabaseManager.cloneMainDatabaseToExportDatabase(AbstractExportDatabaseManager.java:76) 2016-09-12 19:21:39.562609500 at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntitiesWithExportDatabase(DefaultSaxEntitiesExporter.java:137)

Atlassian JIRA | Ryan Mook [Atlassian] | 3 months ago
  1. 0

    h3. Summary It is not possible to create a JIRA backup on JIRA Cloud, either with the {{Create Backup for Cloud}} or the {{Create Backup for Server}} option h3. Environment Atlassian Cloud JIRA 1000.319.1 h3. Steps to Reproduce create a backup on a JIRA Cloud instance using either the {{Create Backup for Cloud}} or the {{Create Backup for Server}} either with or without attachments enabled. h3. Expected Results A backup is created h3. Actual Results The error message Woah! Something went wrong! Unexpected error during export has occurred is displayed.   The below exception is thrown in the log file: {noformat} 2016-09-12 19:21:18.188166500 2016-09-12 19:21:18,185 http-nio-2993-exec-1 INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.o.backupmanager.rest.RootResource] Starting OnDemand backup 2016-09-12 19:21:18.195905500 2016-09-12 19:21:18,195 http-nio-2993-exec-1 INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.ondemand.backupmanager.BackupProcessManagerImpl] Generated task id = 01d94065-b6ec-4e66-aa6c-2258a9a9de28 2016-09-12 19:21:18.201401500 2016-09-12 19:21:18,200 http-nio-2993-exec-1 INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.o.backupmanager.rest.RootResource] OnDemand backup finished 2016-09-12 19:21:18.355780500 2016-09-12 19:21:18,354 Long running task: OnDemandBackup INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.j.a.a.export.DefaultSaxEntitiesExporter.privacy-safe] Exporting entities via the external export database 2016-09-12 19:21:18.356207500 2016-09-12 19:21:18,356 Long running task: OnDemandBackup INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.j.a.a.export.DefaultSaxEntitiesExporter.privacy-safe] Trying to acquire lock for completing an export. 2016-09-12 19:21:18.356357500 2016-09-12 19:21:18,356 Long running task: OnDemandBackup INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.j.a.a.export.DefaultSaxEntitiesExporter.privacy-safe] Successfully retrieved the lock 2016-09-12 19:21:18.358403500 2016-09-12 19:21:18,356 Long running task: OnDemandBackup INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.j.c.d.export.AbstractExportDatabaseManager.privacy-safe] Starting process for cloning main database to export database 2016-09-12 19:21:18.362906500 2016-09-12 19:21:18,362 Long running task: OnDemandBackup INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.j.c.d.export.AbstractExportDatabaseManager.privacy-safe] Clearing data from export database 2016-09-12 19:21:24.188000500 2016-09-12 19:21:24,187 Long running task: OnDemandBackup INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.j.c.d.export.AbstractExportDatabaseManager.privacy-safe] Ignoring these tables in export: [] 2016-09-12 19:21:24.188002500 2016-09-12 19:21:24,187 Long running task: OnDemandBackup INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.j.c.d.export.AbstractExportDatabaseManager.privacy-safe] Cloning main database to export database command has started 2016-09-12 19:21:39.560976500 2016-09-12 19:21:39,559 Long running task: OnDemandBackup ERROR sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.j.c.d.export.AbstractExportDatabaseManager.privacy-safe] There was an error executing the clone command: pg_restore: [archiver (db)] Error while PROCESSING TOC: 2016-09-12 19:21:39.560978500 pg_restore: [archiver (db)] Error from TOC entry 19; 1255 59203 FUNCTION drop_flyway_table() jira 2016-09-12 19:21:39.560979500 pg_restore: [archiver (db)] could not execute query: ERROR: function "drop_flyway_table" already exists with same argument types 2016-09-12 19:21:39.560989500 Command was: 2016-09-12 19:21:39.560989500 CREATE FUNCTION drop_flyway_table() RETURNS integer 2016-09-12 19:21:39.560990500 LANGUAGE plpgsql 2016-09-12 19:21:39.560990500 AS $$ 2016-09-12 19:21:39.560990500 BEGIN 2016-09-12 19:21:39.560990500 BEGIN 2016-09-12 19:21:39.560990500 DROP TABLE flyway_sche... 2016-09-12 19:21:39.560994500 WARNING: errors ignored on restore: 1 2016-09-12 19:21:39.560994500 2016-09-12 19:21:39.560995500 2016-09-12 19:21:39,560 Long running task: OnDemandBackup INFO sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.j.a.a.export.DefaultSaxEntitiesExporter.privacy-safe] Unlocked the export database so now others may use it. 2016-09-12 19:21:39.562582500 2016-09-12 19:21:39,561 Long running task: OnDemandBackup ERROR sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.o.backupmanager.rest.OnDemandBackupTask] Failure during task executing. Task's service: com.atlassian.ondemand.backupmanager.service.JiraBackupService@1ad474 2016-09-12 19:21:39.562584500 com.atlassian.ondemand.backupmanager.backuppolicy.BackupManagerException: Error: PROBLEM_DURING_EXPORT. 2016-09-12 19:21:39.562584500 com.atlassian.jira.exception.DataAccessException: Unable to complete the export due to an error in the cloning command 2016-09-12 19:21:39.562594500 at com.atlassian.ondemand.backupmanager.service.JiraBackupService.backup(JiraBackupService.java:162) 2016-09-12 19:21:39.562594500 at com.atlassian.ondemand.backupmanager.rest.OnDemandBackupTask.run(OnDemandBackupTask.java:86) 2016-09-12 19:21:39.562595500 at com.atlassian.ondemand.backupmanager.longrunning.ManagedTask.run(ManagedTask.java:35) 2016-09-12 19:21:39.562595500 at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:511) 2016-09-12 19:21:39.562599500 at java.util.concurrent.FutureTask.run(FutureTask.java:266) 2016-09-12 19:21:39.562599500 at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1142) 2016-09-12 19:21:39.562604500 at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:617) 2016-09-12 19:21:39.562605500 at java.lang.Thread.run(Thread.java:745) 2016-09-12 19:21:39.562605500 Caused by: com.atlassian.jira.exception.DataAccessException: Unable to complete the export due to an error in the cloning command 2016-09-12 19:21:39.562605500 at com.atlassian.jira.config.database.export.AbstractExportDatabaseManager.cloneMainDatabaseToExportDatabase(AbstractExportDatabaseManager.java:76) 2016-09-12 19:21:39.562609500 at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntitiesWithExportDatabase(DefaultSaxEntitiesExporter.java:137) 2016-09-12 19:21:39.562610500 at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntities(DefaultSaxEntitiesExporter.java:110) 2016-09-12 19:21:39.562610500 at com.atlassian.ondemand.backupmanager.service.JiraBackupService.exportJIRA(JiraBackupService.java:330) 2016-09-12 19:21:39.562614500 at com.atlassian.ondemand.backupmanager.service.JiraBackupService.backup(JiraBackupService.java:138) 2016-09-12 19:21:39.562614500 2016-09-12 19:21:39,562 Long running task: OnDemandBackup WARN sysadmin 1161x21940x1 psmc0h 193.240.188.96 /rest/obm/1.0/runbackup [c.a.o.backupmanager.rest.OnDemandBackupTask] com.atlassian.ondemand.backupmanager.service.JiraBackupService@1ad474 fails to provide text via configured resource bundle. Can't find resource for bundle java.util.PropertyResourceBundle, key backupmanager.PROBLEM_DURING_EXPORT. Trying to resolve directly {noformat} h3. Workaround None h3. Notes Fix is currently being implemented      

    Atlassian JIRA | 3 months ago | Ryan Mook [Atlassian]
    com.atlassian.jira.exception.DataAccessException: Unable to complete the export due to an error in the cloning command 2016-09-12 19:21:39.562605500 at com.atlassian.jira.config.database.export.AbstractExportDatabaseManager.cloneMainDatabaseToExportDatabase(AbstractExportDatabaseManager.java:76) 2016-09-12 19:21:39.562609500 at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntitiesWithExportDatabase(DefaultSaxEntitiesExporter.java:137)
  2. 0

    {noformat} 2010-05-04 01:49:24,618 main INFO [jira.upgrade.tasks.UpgradeTask_Build552] Converting search requests to use the new labels system field is 100% complete. 2010-05-04 01:49:24,618 main INFO [jira.upgrade.tasks.UpgradeTask_Build552] Updating saved filters to use the new labels system field...DONE 2010-05-04 01:49:24,618 main INFO [jira.upgrade.tasks.UpgradeTask_Build552] Updating label gadgets use the new labels system field... 2010-05-04 01:49:24,717 main ERROR [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception whi le executing the following:SELECT ID, PORTLETCONFIGURATION, USERPREFKEY, USERPREFVALUE FROM gadgetuserpreference WHERE (PORTLETCONFIGURATION IN () ) AND (USERPREFKEY = ? ) (You have a n error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right syntax to use near ') ) AND (USERPREFKEY = 'fieldId' )' at line 1) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, PORTLETCONFIGURATION, USERPRE FKEY, USERPREFVALUE FROM gadgetuserpreference WHERE (PORTLETCONFIGURATION IN () ) AND (USERPREFKEY = ? ) (You have an error in your SQL syntax; check the manual that corresponds to yo ur MySQL server version for the right syntax to use near ') ) AND (USERPREFKEY = 'fieldId' )' at line 1) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByCondition(DefaultOfBizDelegator.java:188) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByCondition(DefaultOfBizDelegator.java:175) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build552.updateGadgetConfigurations(UpgradeTask_Build552.java:190) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build552.doUpgrade(UpgradeTask_Build552.java:151) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:562) at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:466) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:402) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:353) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:292) at com.atlassian.jira.upgrade.UpgradeLauncher.checkIfUpgradeNeeded(UpgradeLauncher.java:100) at com.atlassian.jira.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:49) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3934) at org.apache.catalina.core.StandardContext.start(StandardContext.java:4429) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardHost.start(StandardHost.java:722) at org.apache.catalina.core.ContainerBase.start(ContainerBase.java:1045) at org.apache.catalina.core.StandardEngine.start(StandardEngine.java:443) at org.apache.catalina.core.StandardService.start(StandardService.java:516) at org.apache.catalina.core.StandardServer.start(StandardServer.java:710) at org.apache.catalina.startup.Catalina.start(Catalina.java:583) at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method) at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39) at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25) at java.lang.reflect.Method.invoke(Method.java:597) at org.apache.catalina.startup.Bootstrap.start(Bootstrap.java:288) at org.apache.catalina.startup.Bootstrap.main(Bootstrap.java:413) Caused by: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, PORTLETCONFIGURATION, USERPREFKEY, USERPREFVALUE FROM gadgetuserpref erence WHERE (PORTLETCONFIGURATION IN () ) AND (USERPREFKEY = ? ) (You have an error in your SQL syntax; check the manual that corresponds to your MySQL server version for the right s yntax to use near ') ) AND (USERPREFKEY = 'fieldId' )' at line 1) at org.ofbiz.core.entity.jdbc.SQLProcessor.executeQuery(SQLProcessor.java:596) at org.ofbiz.core.entity.GenericDAO.selectListIteratorByCondition(GenericDAO.java:1076) at org.ofbiz.core.entity.GenericDAO.selectByCondition(GenericDAO.java:919) at org.ofbiz.core.entity.GenericHelperDAO.findByCondition(GenericHelperDAO.java:162) at org.ofbiz.core.entity.GenericDelegator.findByCondition(GenericDelegator.java:960) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByCondition(DefaultOfBizDelegator.java:183) ... 25 more {noformat}

    Atlassian JIRA | 7 years ago | George Barnett
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT ID, PORTLETCONFIGURATION, USERPRE FKEY, USERPREFVALUE FROM gadgetuserpreference WHERE (PORTLETCONFIGURATION IN () ) AND (USERPREFKEY = ? ) (You have an error in your SQL syntax; check the manual that corresponds to yo ur MySQL server version for the right syntax to use near ') ) AND (USERPREFKEY = 'fieldId' )' at line 1)
  3. 0

    There is a spelling mistake of *esablish* which suppose to be *establish* in bq. Unable to esablish a connection with the database. Also, when we are at it, is it possible to further improve the error thrown to sent more clearer message? h4. Steps to reproduce: # Start JIRA that is connected to external database (eg. MySQL) # Go to Issue Navigator # Stop MySQL service # Click on one of the issue in the Issue Navigator h4. Error thrown: !esablish.PNG|thumbnail! {noformat} Cause: com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) Stack Trace: [hide] com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:94) at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssue(DefaultIssueManager.java:114) at com.atlassian.jira.issue.managers.DefaultIssueManager.getIssueObject(DefaultIssueManager.java:306) at com.atlassian.jira.servlet.QuickLinkServlet.linkToIssue(QuickLinkServlet.java:139) at com.atlassian.jira.servlet.QuickLinkServlet.service(QuickLinkServlet.java:46) at javax.servlet.http.HttpServlet.service(HttpServlet.java:722) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:305) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:210) at com.atlassian.jira.web.filters.steps.ChainedFilterStepRunner.doFilter(ChainedFilterStepRunner.java:78) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:243){noformat}

    Atlassian JIRA | 4 years ago | Zulfadli Noor Sazali [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Unable to esablish a connection with the database. (Communications link failure The last packet sent successfully to the server was 0 milliseconds ago. The driver has not received any packets from the server.)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Hi Bob, We are using atlassian-cli-3.9.0 and JIRA version 5.4.12. We are using following command to delete some projects: jira --action deleteProject --project "prokjectKey" The above command is working fine for most of the projects but in some cases this fails to delete projects. We have experienced following error in JIRA log: ------------------- 2016-05-08 10:54:44,476 http-bio-8080-exec-118 ERROR anonymous 638x278692x1 - 172.18.16.166,172.18.13.241,172.18.14.165 /rpc/soap/jirasoapservice-v2 [atlassian.jira.project.DefaultProjectManager] Exception removing issues com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Generic Entity Exception occurred in deleteByAnd (SQL Exception while executing the following:DELETE FROM moved_issue_key WHERE ISSUE_ID=? (Deadlock found when trying to get lock; try restarting transaction)) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.removeByAnd(DefaultOfBizDelegator.java:311) ---------------------- On command line interface we are getting below error message: --------------------- Remote error: ; nested exception is: java.net.SocketException: Connection reset Sun May 8 10:43:36 GMT 2016 Could not deleted Project with key: AU --------------------- Once we checked the database, then we found that some of the projects are not deleted but some of them were deleted in spite of these errors. So my question is that can you please confirm that whether these deleted projects are deleted successfully along with their related data or only partial data were removed of deleted projects as during deletion we were getting above error. Can you please suggest any solution in order to prevent these errors, as we have so many projects (about 1600) to delete. Thanks, Reetesh

    JIRA | 7 months ago | Reetesh Kumar
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: Generic Entity Exception occurred in deleteByAnd (SQL Exception while executing the following:DELETE FROM moved_issue_key WHERE ISSUE_ID=? (Deadlock found when trying to get lock; try restarting transaction))
  6. 0

    Upgrade from 3.4 fails with SQL Exception: 2006-03-10 16:07:00,040 ERROR [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: S QL Exception while executing the following:SELECT PE.PROPERTY_KEY, PE.ENTITY_NAME, PE.ID, PS.propertyvalue FROM propertyentry PE LEFT JOIN propertystring PS O N PE.ID = PS.ID WHERE PE.PROPERTY_KEY=? AND PE.ENTITY_NAME=? (ORA-00933: SQL command not properly ended ) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT PE.PROP ERTY_KEY, PE.ENTITY_NAME, PE.ID, PS.propertyvalue FROM propertyentry PE LEFT JOIN propertystring PS ON PE.ID = PS.ID WHERE PE.PROPERTY_KEY=? AND PE.ENTITY_NAM E=? (ORA-00933: SQL command not properly ended ) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByAnd(DefaultOfBizDelegator.java:32) at com.atlassian.jira.user.util.UserUtilImpl.getUserLocalePreferenceEntries(UserUtilImpl.java:131) at com.atlassian.jira.user.util.UserUtilImpl.getUserLocalePreferenceCount(UserUtilImpl.java:122) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build125.doUpgrade(UpgradeTask_Build125.java:60) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:681) at com.atlassian.jira.upgrade.UpgradeManagerImpl.runUpgradeTasks(UpgradeManagerImpl.java:577) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgrade(UpgradeManagerImpl.java:403) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeeded(UpgradeManagerImpl.java:351) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeIfNeededAndAllowed(UpgradeManagerImpl.java:311) at com.atlassian.jira.upgrade.UpgradeLauncher.contextInitialized(UpgradeLauncher.java:68) at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:3212) at org.apache.catalina.core.StandardContext.start(StandardContext.java:3554) at org.apache.catalina.core.StandardHostDeployer.start(StandardHostDeployer.java:582) at org.apache.catalina.core.StandardHost.start(StandardHost.java:866) at org.apache.catalina.servlets.ManagerServlet.start(ManagerServlet.java:1056) at org.apache.catalina.servlets.HTMLManagerServlet.start(HTMLManagerServlet.java:506) at org.apache.catalina.servlets.HTMLManagerServlet.doGet(HTMLManagerServlet.java:108) at javax.servlet.http.HttpServlet.service(HttpServlet.java:696) at javax.servlet.http.HttpServlet.service(HttpServlet.java:809) at org.apache.catalina.core.ApplicationFilterChain.internalDoFilter(ApplicationFilterChain.java:200) at org.apache.catalina.core.ApplicationFilterChain.doFilter(ApplicationFilterChain.java:146) at org.apache.catalina.core.StandardWrapperValve.invoke(StandardWrapperValve.java:209) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) at org.apache.catalina.core.StandardContextValve.invoke(StandardContextValve.java:144) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:596) at org.apache.catalina.authenticator.AuthenticatorBase.invoke(AuthenticatorBase.java:504) at org.apache.catalina.core.StandardPipeline$StandardPipelineValveContext.invokeNext(StandardPipeline.java:594) at org.apache.catalina.core.StandardPipeline.invoke(StandardPipeline.java:433) at org.apache.catalina.core.ContainerBase.invoke(ContainerBase.java:948) :

    Atlassian JIRA | 1 decade ago | Eric Helfrich
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT PE.PROP ERTY_KEY, PE.ENTITY_NAME, PE.ID, PS.propertyvalue FROM propertyentry PE LEFT JOIN propertystring PS ON PE.ID = PS.ID WHERE PE.PROPERTY_KEY=? AND PE.ENTITY_NAM E=? (ORA-00933: SQL command not properly ended )

    Not finding the right solution?
    Take a tour to get the most out of Samebug.

    Tired of useless tips?

    Automated exception search integrated into your IDE

    Root Cause Analysis

    1. com.atlassian.jira.exception.DataAccessException

      Unable to complete the export due to an error in the cloning command 2016-09-12 19:21:39.562605500 at com.atlassian.jira.config.database.export.AbstractExportDatabaseManager.cloneMainDatabaseToExportDatabase(AbstractExportDatabaseManager.java:76) 2016-09-12 19:21:39.562609500 at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntitiesWithExportDatabase(DefaultSaxEntitiesExporter.java:137)

      at com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntities()
    2. com.atlassian.jira
      DefaultSaxEntitiesExporter.exportEntities
      1. com.atlassian.jira.action.admin.export.DefaultSaxEntitiesExporter.exportEntities(DefaultSaxEntitiesExporter.java:110)
      1 frame
    3. com.atlassian.ondemand
      JiraBackupService.exportJIRA
      1. com.atlassian.ondemand.backupmanager.service.JiraBackupService.exportJIRA(JiraBackupService.java:330)
      1 frame