com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.)

Atlassian JIRA | Bogdan Dziedzic [Atlassian] | 7 years ago
  1. 0

    Users who integrate JIRA with a MS SQL database with the case sensitive collation won't be able to perform upgrade of the application. There are a few upgrades task that are failing due to the case sensitive collation. {noformat} 2010-06-07 12:54:50,487 http-8081-1 ERROR anonymous 774x61x1 9l6cw1 127.0.1.1 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:565) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.calculateResolutionDateForAllIssues(UpgradeTask_Build401.java:214) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.doUpgrade(UpgradeTask_Build401.java:116) {noformat} or {noformat} Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:552) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build437.doUpgrade(UpgradeTask_Build437.java:63) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:508) {noformat} Users experiencing similar problems are recommended to create a new database with a case insensitive collation such as _SQL_Latin1_General_CP437_CI_AI_

    Atlassian JIRA | 7 years ago | Bogdan Dziedzic [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.)
  2. 0

    Users who integrate JIRA with a MS SQL database with the case sensitive collation won't be able to perform upgrade of the application. There are a few upgrades task that are failing due to the case sensitive collation. {noformat} 2010-06-07 12:54:50,487 http-8081-1 ERROR anonymous 774x61x1 9l6cw1 127.0.1.1 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:565) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.calculateResolutionDateForAllIssues(UpgradeTask_Build401.java:214) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.doUpgrade(UpgradeTask_Build401.java:116) {noformat} or {noformat} Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:552) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build437.doUpgrade(UpgradeTask_Build437.java:63) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:508) {noformat} Users experiencing similar problems are recommended to create a new database with a case insensitive collation such as _SQL_Latin1_General_CP437_CI_AI_

    Atlassian JIRA | 7 years ago | Bogdan Dziedzic [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.)
  3. 0

    Hello, when connected to a Sybase DBMS upgrade task _UpgradeTask_Build401_ will fail throwing an exception due to bad SQL: {noformat} 2009-10-14 09:58:51,957 http-8080-4 ERROR anonymous 35884x9x1 1lj127n /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT MAX(CG.CREATED), CG.issueid FROM changegroup CG INNER JOIN changeitem CI ON CG.ID = CI.groupid WHERE (CG.issueid IN (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ) AND ((CI.FIELD = ? ) OR (CI.FIELD = ? )) AND (CI.NEWSTRING IS NOT NULL ) AND (CI.OLDVALUE IS NULL ) GROUP BY CG.issueid (TEXT-, IMAGE- und UNITEXT-Datentypen dürfen in WHERE-Klausel nur mit dem Ausdruck LIKE verwendet werden.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT MAX(CG.CREATED), CG.issueid FROM changegroup CG INNER JOIN changeitem CI ON CG.ID = CI.groupid WHERE (CG.issueid IN (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ) AND ((CI.FIELD = ? ) OR (CI.FIELD = ? )) AND (CI.NEWSTRING IS NOT NULL ) AND (CI.OLDVALUE IS NULL ) GROUP BY CG.issueid (TEXT-, IMAGE- und UNITEXT-Datentypen dürfen in WHERE-Klausel nur mit dem Ausdruck LIKE verwendet werden.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.findByCondition(DefaultOfBizDelegator.java:174) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401$CalculatingResolutionDateConsumer.processBatch(UpgradeTask_Build401.java:279) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.calculateResolutionDateForAllIssues(UpgradeTask_Build401.java:179) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.doUpgrade(UpgradeTask_Build401.java:114) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:508) {noformat} Running the query directly returns the following error: {noformat} TEXT, IMAGE and UNITEXT datatypes may not be used in a WHERE clause, except with the LIKE expression. {noformat} Best Regards, Edoardo

    Atlassian JIRA | 7 years ago | Edoardo Causarano [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:SELECT MAX(CG.CREATED), CG.issueid FROM changegroup CG INNER JOIN changeitem CI ON CG.ID = CI.groupid WHERE (CG.issueid IN (?, ?, ?, ?, ?, ?, ?, ?, ?, ?) ) AND ((CI.FIELD = ? ) OR (CI.FIELD = ? )) AND (CI.NEWSTRING IS NOT NULL ) AND (CI.OLDVALUE IS NULL ) GROUP BY CG.issueid (TEXT-, IMAGE- und UNITEXT-Datentypen dürfen in WHERE-Klausel nur mit dem Ausdruck LIKE verwendet werden.)
  4. Speed up your debug routine!

    Automated exception search integrated into your IDE

  5. 0

    Users who integrate JIRA with a MS SQL database with the case sensitive collation won't be able to perform upgrade of the application. There are a few upgrades task that are failing due to the case sensitive collation. {noformat} 2010-06-07 12:54:50,487 http-8081-1 ERROR anonymous 774x61x1 9l6cw1 127.0.1.1 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:565) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.calculateResolutionDateForAllIssues(UpgradeTask_Build401.java:214) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.doUpgrade(UpgradeTask_Build401.java:116) {noformat} or {noformat} Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:552) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build437.doUpgrade(UpgradeTask_Build437.java:63) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:508) {noformat} Users experiencing similar problems are recommended to create a new database with a case insensitive collation such as _SQL_Latin1_General_CP437_CI_AI_

    Atlassian JIRA | 7 years ago | Bogdan Dziedzic [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.)
  6. 0

    Users who integrate JIRA with a MS SQL database with the case sensitive collation won't be able to perform upgrade of the application. There are a few upgrades task that are failing due to the case sensitive collation. {noformat} 2010-06-07 12:54:50,487 http-8081-1 ERROR anonymous 774x61x1 9l6cw1 127.0.1.1 /secure/SetupImport.jspa [atlassian.jira.upgrade.UpgradeManagerImpl] Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:565) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.calculateResolutionDateForAllIssues(UpgradeTask_Build401.java:214) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build401.doUpgrade(UpgradeTask_Build401.java:116) {noformat} or {noformat} Exception thrown during upgrade: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.) com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.) at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:552) at com.atlassian.jira.upgrade.tasks.UpgradeTask_Build437.doUpgrade(UpgradeTask_Build437.java:63) at com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:508) {noformat} Users experiencing similar problems are recommended to create a new database with a case insensitive collation such as _SQL_Latin1_General_CP437_CI_AI_

    Atlassian JIRA | 7 years ago | Bogdan Dziedzic [Atlassian]
    com.atlassian.jira.exception.DataAccessException: org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.jiraissue SET RESOLUTIONDATE = ? WHERE id = ? (Invalid column name 'id'.)

    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

      org.ofbiz.core.entity.GenericDataSourceException: SQL Exception while executing the following:UPDATE jiraschema.portalpage SET ppversion = ? WHERE id = ? (Invalid column name 'id'.)

      at com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey()
    2. com.atlassian.jira
      UpgradeManagerImpl.doUpgradeTaskSucess
      1. com.atlassian.jira.ofbiz.DefaultOfBizDelegator.bulkUpdateByPrimaryKey(DefaultOfBizDelegator.java:552)
      2. com.atlassian.jira.upgrade.tasks.UpgradeTask_Build437.doUpgrade(UpgradeTask_Build437.java:63)
      3. com.atlassian.jira.upgrade.UpgradeManagerImpl.doUpgradeTaskSucess(UpgradeManagerImpl.java:508)
      3 frames