After upgrade to JIRA 6, user encounters DVCS plugins database storage library error message
Platform Notice: Data Center Only - This article only applies to Atlassian products on the Data Center platform.
Note that this KB was created for the Data Center version of the product. Data Center KBs for non-Data-Center-specific features may also work for Server versions of the product, however they have not been tested. Support for Server* products ended on February 15th 2024. If you are running a Server product, you can visit the Atlassian Server end of support announcement to review your migration options.
*Except Fisheye and Crucible
Symptoms
The following appears in the atlassian-jira.log:
1
2
3
4
5
6
7
8
9
10
11
12
13
14
15
2013-09-03 13:48:32,576 StreamsCompletionService::thread-3935 ERROR xxxx /plugins/servlet/streams [atlassian.streams.internal.LocalActivityProvider] Error building feed
java.lang.RuntimeException: org.postgresql.util.PSQLException: ERROR: zero-length delimited identifier at or near """"
Position: 20
at com.atlassian.jira.plugins.dvcs.activeobjects.v3.To_12_SplitUpChangesetsMigrator.upgrade(To_12_SplitUpChangesetsMigrator.java:360)
at com.atlassian.activeobjects.internal.ActiveObjectUpgradeManagerImpl$1.doInTransaction(ActiveObjectUpgradeManagerImpl.java:81)
at com.atlassian.activeobjects.internal.ActiveObjectUpgradeManagerImpl$1.doInTransaction(ActiveObjectUpgradeManagerImpl.java:76)
at com.atlassian.sal.core.transaction.HostContextTransactionTemplate$1.doInTransaction(HostContextTransactionTemplate.java:25)
at com.atlassian.jira.DefaultHostContextAccessor.doInTransaction(DefaultHostContextAccessor.java:34) <+2>
at java.lang.reflect.Method.invoke(Unknown Source)
...
Caused by: org.postgresql.util.PSQLException: ERROR: zero-length delimited identifier at or near """"
Position: 20
at org.postgresql.core.v3.QueryExecutorImpl.receiveErrorResponse(QueryExecutorImpl.java:2102)
at org.postgresql.core.v3.QueryExecutorImpl.processResults(QueryExecutorImpl.java:1835)
...Cause
The cause is unknown. The problem may be caused by corrupted data in the JIRA DVCS Connector Plugin tables or a PostgreSQL configuration issue. The following tables may be related:
1
2
3
4
5
AO_E8B6CC_ISSUE_TO_CHANGESET
AO_E8B6CC_REPOSITORY_MAPPING
AO_E8B6CC_CHANGESET_MAPPING
AO_E8B6CC_ORGANIZATION_MAPPING
AO_E8B6CC_REPO_TO_CHANGESETResolution
Applying this resolution will cause all repository mapping data to be lost. Please do not apply this solution if that is not acceptable to you.
Navigate to "Plugin Data Storage"
This is located in JIRA Administration > System
You can also use keyboard shortcuts, type g+g and search for "Plugin Data Storage"
Make a list of the tables associated with the JIRA DVCS Connector Plugin. For example:
1 2 3 4 5AO_E8B6CC_ISSUE_TO_CHANGESET AO_E8B6CC_REPOSITORY_MAPPING AO_E8B6CC_CHANGESET_MAPPING AO_E8B6CC_ORGANIZATION_MAPPING AO_E8B6CC_REPO_TO_CHANGESETBackup your JIRA data before making any changes.
Uninstall the JIRA DVCS Connector Plugin, dropping the associated tables from the database, and then re-install the plugin.
Re-sync again (this may take a while)
Was this helpful?