Create
cancel
Showing results for 
Search instead for 
Did you mean: 
Sign up Log in
Celebration

Earn badges and make progress

You're on your way to the next level! Join the Kudos program to earn points and save your progress.

Deleted user Avatar
Deleted user

Level 1: Seed

25 / 150 points

Next: Root

Avatar

1 badge earned

Collect

Participate in fun challenges

Challenges come and go, but your rewards stay with you. Do more to earn more!

Challenges
Coins

Gift kudos to your peers

What goes around comes around! Share the love by gifting kudos to your peers.

Recognition
Ribbon

Rise up in the ranks

Keep earning points to reach the top of the leaderboard. It resets every quarter so you always have a chance!

Leaderboard

Come for the products,
stay for the community

The Atlassian Community can help you and your team get more value out of Atlassian products and practices.

Atlassian Community about banner
4,462,867
Community Members
 
Community Events
176
Community Groups

missing table [MIG_ANALYTICS_EVENT]

Hello everyone

After updating "Confluence Cloud Migration Assistant" to version 3.3.3 we get the following error:

org.apache.velocity.exception.MethodInvocationException: Invocation of method 'getInitialState' in class com.atlassian.migration.agent.web.AppAction threw exception com.atlassian.util.concurrent.LazyReference$InitializationException: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [MIG_ANALYTICS_EVENT] at /templates/app.vm[line 21, column 44]
at org.apache.velocity.runtime.parser.node.ASTIdentifier.execute(ASTIdentifier.java:223)

caused by: com.atlassian.util.concurrent.LazyReference$InitializationException: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [MIG_ANALYTICS_EVENT]
at com.atlassian.util.concurrent.LazyReference.getInterruptibly(LazyReference.java:149)

caused by: org.hibernate.tool.schema.spi.SchemaManagementException: Schema-validation: missing table [MIG_ANALYTICS_EVENT]
at org.hibernate.tool.schema.internal.AbstractSchemaValidator.validateTable(AbstractSchemaValidator.java:121)

 

We've already tried the steps mentioned in these articles: 

[MIG-189] Migration assistant fails in Confluence if not all MIG_ tables exist - Create and track feature requests for Atlassian products.

[CONFSERVER-58124] Cloud Migration Assistant app shows up in the list of apps even after being uninstalled - Create and track feature requests for Atlassian products.

In our case we did:

  • uninstalled "Confluence Cloud Migration Assistant"
  • stopped the confluence service
  • dropped the MIG_* tables
  • deleted the chache folders (MIG-189)
  • started the confluence service
  • installed "Confluence Cloud Migration Assistant"

As a result, the MIG_* tables are created, but we get the same error again.
A previous version (3.2.1) worked, but has to be updated in order to migrate to the cloud.

Are there any ideas or workarounds how to get the newest version of "Confluence Cloud Migration Assistant" installed?

 

Thanks in advance

1 answer

1 accepted

0 votes
Answer accepted

Hi @Erich Stöckli

Thanks for contacting Atlassian Community. I just did a test upgrade and install and it worked fine. I was running on PostgreSQL. 

What database are you running so we can try and reproduce the error?

Regards,
James.

Hi @James Richards

We are running Microsoft SQL Server Standard 2016 (Version 13.0.4001.0).

Regards,
Erich

Hi,

What version of Confluence are you running? We need to make sure SQL Server 2016 is supported.

See https://confluence.atlassian.com/doc/supported-platforms-207488198.html for versions.

James.

Hi,

We are currently still using Confluence 6.2.1.

Regards,
Erich

Hi,

From

https://confluence.atlassian.com/display/CONF62/Supported+Platforms

Confluence 6.2 only supports SQL Server 2012, 2014. I'd recommend upgrading Confluence first of all to make sure everything is on the same version level.

Regards,
James.

Thank you very much for the support. The update to Confluence 6.15 and Confluence Cloud Migration Assistant 3.3.4 has now solved the problem for us and the migration to the cloud is now working.

Regards,
Erich

Like James Richards likes this

Suggest an answer

Log in or Sign up to answer
TAGS

Atlassian Community Events