As a preparation to upgrade my confluence production environment from 5.9.5 to 5.10.8 i'm running into an error:
Upgrade failed. Please consult the system logs for details. You will need to fix these problems, restore your database and confluence home directory to the pre upgrade state. Then retry the upgrade.
In Confluence log I find the following error:
ncategorized SQLException for SQL []; SQL state [S0002]; error code [208]; Invalid object name 'scheduler_clustered_jobs'.; nested exception is java.sql.SQLException: Invalid object name 'scheduler_clustered_jobs'.
Looking into database both in test as in production I'm missig an table named scheduler_clustered_jobs
What to do now?
How can I check schema names in confluence.cfg.xml? In SQL Server schema name both in test and prod are dbo, but I cannot verify this in configfile. There it is both like:
property name="hibernate.connection.driver_class">net.sourceforge.jtds.jdbc.Driver</property>
<property name="hibernate.connection.isolation">2</property>
<property name="hibernate.connection.password"></property>
<property name="hibernate.connection.url">jdbc:jtds:sqlserver://localhost:1433/Confluence</property>
<property name="hibernate.connection.username">Confluence</property>
Arno,
The article actually mentions that it's in conf/server.xml but I'm not able to see there what needs to be modified.
In my search, I discovered you already created a support ticket. I will take that ticket for now, and I ask that you send a copy of your support zip there so I can see your full logs to get a better idea of the problem.
Thank you for your help!
Kind regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Arno,
Can you let us know the version of SQL you are running, and also make sure that your schema names are consistent?
Thank you!
Kind regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Shanon, the SQL version in test is 2014. However in production this is stil 2008. As we're running out of support with our Confluence version end this week, we want to first upgrade Confluence to the next step Confluence and migrate Confluence to a new Windows server version and SQL version after that
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Arno,
Thank you for confirming. When you have a chance, please let me know what the results of your schema tests were.
Kind regards,
Shannon
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Online forums and learning are now in one easy-to-use experience.
By continuing, you accept the updated Community Terms of Use and acknowledge the Privacy Policy. Your public name, photo, and achievements may be publicly visible and available in search engines.
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.