--- title: "Troubleshooting BigGantt Visibility Issues After Jira Database Migration to PostgreSQL" canonical: "https://support.appfire.com/space/SUPPORT/3504275677/Troubleshooting%20BigGantt%20Visibility%20Issues%20After%20Jira%20Database%20Migration%20to%20PostgreSQL" format: markdown --- This draft captures a resolved support pattern from a Jira Data Center case where BigGantt appeared not to load correctly after a database migration from Microsoft SQL Server to PostgreSQL. The goal is to help support engineers quickly recognize the symptom, request the right data, and guide customers through likely recovery steps. > ℹ️ Use this article for **Jira Data Center** cases involving **BigGantt** after a database migration or major environment change, especially when the app starts, but boards or data do not appear as expected. # Issue summary A customer migrated their Jira database from MS SQL to PostgreSQL and then found that BigGantt was not fully usable. The customer reported difficulty getting the app “up and running.” In the resolved case, the missing content eventually appeared after additional testing and several server restarts. The most useful lesson from this case is that post-migration app visibility issues are not always caused by permanent data corruption. In some situations, the app may recover after Jira restarts and background initialization completes. # Typical symptoms - BigGantt installs and opens, but expected boards or views are missing. - The app appears partially loaded after a database migration. - The customer suspects a version-jump or database-engine migration problem. - Jira itself is running, but BigGantt data is incomplete or not displayed. # Environment pattern from the reference case | Field | Value | | --- | --- | | Host platform | Jira Data Center | | Source scenario | Database migration from Microsoft SQL Server to PostgreSQL | | App | BigGantt | | Reported app version | BigGantt 8.43.0 | | Reported Jira version | Jira 9.12.15 | | Outcome | Boards became visible after further testing and multiple Jira restarts | # What support should assess first - Is BigGantt completely unavailable, or are only some boards missing? - Did the problem start immediately after the database migration? - Verify this is Jira Data Center or Server-style infrastructure. - Check whether the customer migrated only the Jira database engine, or also changed app versions, Jira versions, or infrastructure. - Ask whether Jira has been restarted since the migration. - Ask whether the behaviour changes after additional restarts and time for startup tasks to complete. - Support zip file - Database dump of `AO_8AC478_UPGRADE_TASK_HISTORY` > ℹ️ For BigGantt, the Active Objects table prefix is `AO_8AC478_`. This is useful when checking whether app-specific migration or upgrade tasks completed correctly. # Initial support response template > Thank you for contacting Support. To analyze the post-migration BigGantt behavior, please share a Jira support zip file and a dump of the `AO_8AC478_UPGRADE_TASK_HISTORY` table. These will help us verify whether BigGantt upgrade or initialization tasks completed correctly after the database migration. # Likely causes in similar cases - **Post-migration initialization delay:** BigGantt may require time and successful startup cycles to complete internal tasks after the database move. - **Incomplete app upgrade tasks:** Upgrade history may show tasks that did not complete cleanly after the environment change. - **Version-jump side effects:** If Jira or BigGantt was also upgraded, missing views can be related to upgrade sequencing rather than the database engine alone. - **Transient cache or startup state issues:** Multiple restarts may allow the app to rebuild caches or re-register data correctly. # Recommended troubleshooting flow - Request the Jira support zip. - Request the `AO_8AC478_UPGRADE_TASK_HISTORY` table dump. - Ask for screenshots showing the missing boards or incomplete UI. - Check whether BigGantt upgrade tasks completed successfully. - Look for errors, pending tasks, or repeated failures in logs and upgrade history. - Confirm whether only the database engine changed, or whether Jira and BigGantt versions changed too. - Check whether the customer followed any app-specific migration or upgrade guidance. - If there is no evidence of hard failure, ask the customer to restart Jira and recheck the app. - If needed, repeat after allowing full startup completion. - Ask whether all boards are now visible. - If yes, document that the issue resolved after repeated restarts following migration. > 📝 In the reference ticket, the final resolution was not a schema repair or manual database cleanup. The customer reported that after more testing and four additional server reboots, all boards appeared again. # Resolution pattern from the reference case After additional testing and four more Jira server reboots, the customer reported that all boards were visible again and confirmed the ticket could be closed. > ✅ Practical takeaway: if BigGantt is partially visible after a database migration and diagnostics do not show a clear blocking failure, repeated full Jira restarts may resolve the issue by allowing app initialization and background tasks to finish. # What not to assume - Do not assume the database migration permanently damaged BigGantt data. - Do not immediately recommend destructive cleanup of Active Objects tables. - Do not recommend a clean install unless evidence clearly shows corruption or failed app state that cannot recover normally. # When to consider deeper action Move beyond basic restart-and-verify guidance when any of the following is true: - The `AO_8AC478_UPGRADE_TASK_HISTORY` data shows failed or stuck upgrade tasks. - Logs show repeated startup exceptions related to BigGantt tables or schema access. - The app remains incomplete after multiple full Jira restarts. - The customer also performed a major version jump and behavior suggests unsupported sequencing.
Escalation notes for support engineers
# Customer-facing response example > Hello, > Thank you for the update. In similar post-migration cases, BigGantt may need additional Jira restarts before all internal initialization tasks complete correctly. Please share a support zip file and a dump of the `AO_8AC478_UPGRADE_TASK_HISTORY` table so we can verify the app’s upgrade state. If there are no blocking errors in the logs, a few full Jira restarts may help the missing boards reappear. > > If the issue persists after that, we can review the upgrade-task history and logs in more detail. > > Best regards, > Support Team # References - [Extracting Jira support zip](https://appfire.atlassian.net/wiki/spaces/DLP/pages/296981153) - [Upgrade (migration from BigGantt to BigPicture)](https://appfire.atlassian.net/wiki/spaces/DLP/pages/297865130) - [Clean Install BigPlugins](https://appfire.atlassian.net/wiki/spaces/DLP/pages/2211972321)