Support Staff2 Posted by Mike on 09 May, 2012 05:29 PM
It sounds/looks like you may have upgraded a database that was
already upgraded with a beta version of Cascade. If this is the
case, you will have to start with a fresh database dump from your
production instance (or any instance that is running a production
release of Cascade) as we do not support upgrading from a beta
version of Cascade to a production version. Let me know if that
resolves your issue. Thanks!
Support Staff4 Posted by Mike on 09 May, 2012 05:59 PM
Yes, I would start over with a fresh database dump. I'm not sure
if maybe the database was partially upgraded or not. This can
happen if you shut down the server before it has finished applying
database updates. Usually when we see messages like "Table 'xyz'
already exists", it means that a database update is being applied
for a second time when it should not be. In rarer cases, this can
happen when the account used to connect to the database is not
You shouldn't have to reinstall Cascade 7 as long as your
context.xml file (found in /<cascade install
directory>/tomcat/conf) is pointing to the correct test
database. If you're not sure, then I would go ahead and do a fresh
install. Make sure that there are no other Cascade instances
running against the database you are trying to upgrade.
Upgrading your production instance should be as simple as
installing Cascade 7 and pointing it to your existing production
database (after having shut down the other version of Cascade,
6.10.5 in your case). Remember to always back up your database
before doing a production upgrade.
Hmm, I don't know, after making sure the database was not being
molested and taking the mysqldump at that point, then using that
copy for the dev environment, I still get the same errors about
cxml_unpublishable and so on.
I suppose I'm going to try reinstalling Cascade without changing
the database and seeing what that gives.
Hi, this is odd. Your query results tell us that your database
should have been running Cascade 6.10 prior to the upgrade but your
log is saying that the database already contains a
table (cxml_unpublishable) that is new to 7.0 and that it is trying
to add during the upgrade.
Can you try:
rolling your database back to a backup before
you attempted the upgrade
sending us the output of the query: show tables
against your MySQL database
Also, your log indicates that Cascade is only attempting to
apply database update 7_0_010 during the upgrade which would
indicate that updates 7_0_001 to 7_0_009 had already been applied.
Yet, your query of your DATABASECHANGELOG table shows that no 7_0_x
updates have been applied yet.
Is it possible your server is pointed at a different database
than the one you're examining? Can you include your
tomcat/conf/context.xml file and a brief overview of the names and
locations of the databases you're using?
All right, I've completely scrubbed everything out from the
database in the dev site and gave it a fresh backup from our live
server and it's worked fine. I think the problem was that I didn't
delete everything in the database before giving it the db from the
live server, which had the 6.10 tables.
So here's what happened:
Updated Cascade on dev site (works great)
Updated database on dev site to reflect live server
I guess I should have known better, but this hasn't been a
problem the last few upgrades in the 6.10.x series, so live and