Confluence had problems starting up after upgrading to 6.12.1
Asked by Jean-Michel Potvin:

Just upgraded from 6.5.1 to 6.12.1 and now get this error:

Description:

Unable to start up Confluence. Fatal error during startup sequence: confluence.lifecycle.core:mananagedjobs (Start and stop the Managed Scheduled Jobs)

Exception:

JDBC exception on Hibernate data access: SQLException for SQL \[n/a\]; SQL state \[HY000\]; error code \[50000\]; could not extract ResultSet; nested exception is org.hibernate.exception.GenericJDBCException: could not extract ResultSet


Answers:
author: Shannon S
body: Hello there,

Can you confirm your database version, and if the Confluence instance is able to access your database server?

Please also confirm with us the exact steps you took to upgrade Confluence.

Regards,

Shannon

comments: author: Jean-Michel Potvin
body: Hi Shannon,

I'm still using the H2 database and I don't see any new records in the LOGINFO table so I'm assuming that the Confluence instance cannot connect.

I have upgraded by running atlassian-confluence-6.12.1-x64.exe and following the steps.

Thanks,

J-M


author: Shannon S
body: Jean-Michel,

The H2 database is only supported for testing instances, and I especially wouldn't recommend performing a migration where it is still in place.

I would recommend setting up a clean 6.12.1 Confluence instance with a [supported database in place](https://confluence.atlassian.com/doc/supported-platforms-207488198.html#SupportedPlatforms-Databases), and restore the backup you made as part of the upgrade process.

Let me know if you have any trouble with that!

Take care,

Shannon


author: Jean-Michel Potvin
body: Shannon,

I have been able to recover my backup using 6.5.1 on MySQL. I will retry the upgrade later.

Thanks for your help.

J-M


author: Shannon S
body: You're welcome, Jean-Michel.

Let us know how it goes and if you run into any issues.

Regards,

Shannon


author: Jean-Michel Potvin
body: The upgrade worked.

Thanks.


author: Shannon S
body: Oh, that's great news! Thank you for confirming.

Take care and have a pleasant rest of your week.

Regards,

Shannon


author: Peter_L?cke
body: Hello Shannon,

I guess I have also a similar situation. I am getting the following error:

![2018-11-27_11h37_30.png](https://community.atlassian.com/t5/image/serverpage/image-id/38670i2941C92245364C6C/image-size/large?v=v2&px=999 "2018-11-27_11h37_30.png")

In my case i guess my database is h2 and mine is test confluence. Please suggest what to do.

Regards,

Tamim


author: Shannon S
body: Hi Tamim,

The H2 database is used for staging/evaluation, and I wouldn't recommend any upgrade or migration using it. If you need to test an upgrade, then it's better to test using the database setup you plan on using for your production instance.

At this point, you won't be able to proceed further. You can use the same steps I recommended to Peter to continue:

1. Roll back the instance by restoring the backup you made prior to attempting the upgrade. Do this by creating a fresh Confluence install (I would recommend using the same version of Confluence that you used to create your XML backup). Restore the XML backup to this.
2. Get that site working normally first.
3. Then connect to a [supported database](https://confluence.atlassian.com/doc/supported-platforms-207488198.html#SupportedPlatforms-Databases).
4. Proceed with the upgrade.

Let me know if you have any questions about that.

Regards,

Shannon


author: Peter_L?cke
body: Hello shannon,

As per your suggestion and confluence documentation I have reverted back my confluence to the older version. Install MYSQL as an external database and install the same version on a different directory (same server). Then I have installed the new version 6.12.2 but unfortunately, got the following errors:

++Description:++

Pre-Upgrade recovery file generation failed.  
Please refer to <https://confluence.atlassian.com/x/ropKGQ> for possible solution.

Post-Upgrade recovery file generation failed.  
Please refer to <https://confluence.atlassian.com/x/ropKGQ> for possible solution.

++Exception:++

No operations allowed after connection closed.

Please suggest something to solve this problem.

Regards,

Tamim


author: Peter_L?cke
body: Hello Shannon,

It works with the solution provided in the following link

<https://confluence.atlassian.com/confkb/warning-recovery-file-generation-failed-424315566.html>

Regards,

Tamim


author: Shannon S
body: Hi Tamim,

Apologies for not coming back to you earlier this morning! Happy to hear you were able to resolve both issues.

Take care, and have a pleasant weekend.

Regards,

Shannon


author: Kouros Ershadi
body: Hi,

I have the same issue. I haven't upgraded the Confluence. Just in a sudden, I receive the error :

JDBC exception on Hibernate data access: SQLException for SQL \[n/a\]; SQL state \[HY000\]; error code \[50000\]; could not extract ResultSet; nested exception is org.hibernate.exception.GenericJDBCException: could not extract ResultSet

I don't have any backup from the database (H2). How I can get the information I have already added in Confluence? Did I loose everything?


author: Shannon S
body: Kouros,

The fix is the same; you need to get off of the H2 database, which isn't supported for upgrades since it's to be used during evaluation period only.

I'll repeat the steps here:

1. Roll back the instance by restoring the backup you made prior to attempting the upgrade. Do this by creating a fresh Confluence install (I would recommend using the same version of Confluence that you used to create your XML backup). Restore the XML backup to this.
2. Get that site working normally first.
3. Then connect to a [supported database](https://confluence.atlassian.com/doc/supported-platforms-207488198.html#SupportedPlatforms-Databases).
4. Proceed with the upgrade.

Alternatively, you can just try this method:

1. Install a fresh copy of the desired version of Confluence.
2. Connect to a supported database.
3. Restore your XML backup.

The first method is more thorough but users have been able to recover with the second method.

Regards,  
Shannon


Tags: confluence-server

server