Details
-
Bug
-
Resolution: Unresolved
-
Low
-
None
-
JCMA - 1.10.7
-
None
-
4
-
Severity 3 - Minor
-
2
Description
Issue Summary
The user is unable to activate and then launch JCMA as the error message pops up with this message - Connection Failure - Error Communicating with Server.
As per the log file, the following error appears in the log file when Jira DB is hosted on Microsoft SQLServer instance. There appears to be a missing schema for AO tables.
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'null.AO_6FF49D_MIGRATION_ENTITY'.
at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:256)
Steps to Reproduce
- Attempt to Activate JCMA under Manage Apps
Expected Results
The user should be able to activate JCMA
Actual Results
Connection Failure - Error Communicating with Server.
Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'null.AO_6FF49D_MIGRATION_ENTITY'. at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:256)
Workaround
Advised the user to change the schema for AO tables using this article here
- Shutdown JIRA
- Run the following SQL query in SQL Server:
SELECT 'ALTER SCHEMA newschema TRANSFER ' + TABLE_SCHEMA + '.' + TABLE_NAME FROM INFORMATION_SCHEMA.TABLES WHERE TABLE_SCHEMA = 'oldschema'
-
- Replace newschema and oldschema with the actual names of your new and old schema.
- This essentially provides a list of SQL queries to help automate the ALTER SCHEMA function in SQL Server
- Copy the results into a new SQL script and run the queries.
- Define the new schema in dbconfig.xml: JIRA Home Directory
- Restart JIRA