Error during upgrade, dot_containers

12 views
Skip to first unread message

David Petersheim

unread,
Sep 2, 2016, 10:47:22 AM9/2/16
to dotCMS User Group
We are attempting to upgrade from 2.5.6 to 3.5.1 in a sandbox environment that's a copy of production. The upgrade fails each time at the same place.

During the upgrade we get the following error in the dotcms.log:

[01/09/16 15:30:20:265 EDT] FATAL runonce.Task03035FixContainerCheckTrigger: Unable to execute SQL upgrade
com.microsoft.sqlserver.jdbc.SQLServerException: The object 'dot_containers' does not exist or is invalid for this operation.
        at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:217) ~[sqljdbc42.jar:?]
        at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1635) ~[sqljdbc42.jar:?]
        at com.microsoft.sqlserver.jdbc.SQLServerStatement.doExecuteStatement(SQLServerStatement.java:865) ~[sqljdbc42.jar:?]
        at com.microsoft.sqlserver.jdbc.SQLServerStatement$StmtExecCmd.doExecute(SQLServerStatement.java:762) ~[sqljdbc42.jar:?]
        at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:6276) ~[sqljdbc42.jar:?]
        at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1793) ~[sqljdbc42.jar:?]
        at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:184) ~[sqljdbc42.jar:?]
        at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:159) ~[sqljdbc42.jar:?]
        at com.microsoft.sqlserver.jdbc.SQLServerStatement.execute(SQLServerStatement.java:735) ~[sqljdbc42.jar:?]
        at org.apache.tomcat.dbcp.dbcp2.DelegatingStatement.execute(DelegatingStatement.java:290) ~[tomcat-dbcp.jar:8.0.18]
        at org.apache.tomcat.dbcp.dbcp2.DelegatingStatement.execute(DelegatingStatement.java:290) ~[tomcat-dbcp.jar:8.0.18]
        at com.dotmarketing.common.db.DotConnect.executeStatement(DotConnect.java:222) ~[dotcms_3.5.1_3.5-8-g8506266.jar:?]
        at com.dotmarketing.startup.AbstractJDBCStartupTask.executeUpgrade(AbstractJDBCStartupTask.java:192) [dotcms_3.5.1_3.5-8-g8506266.jar:?]
        at com.dotmarketing.startup.StartupTasksExecutor.executeUpgrades(StartupTasksExecutor.java:268) [dotcms_3.5.1_3.5-8-g8506266.jar:?]
        at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:116) [dotcms_3.5.1_3.5-8-g8506266.jar:?]
        at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1231) [catalina.jar:8.0.18]

The upgrade stops at that point.


While looking into the problem I found that the Task03035FixContainerCheckTrigger class, the source of the exception, has changed the name of the table in its query from 'containers' to 'dot_containers' in the 3.5.1 release. The table name has changed back to 'containers' in master-3.6.

The table name change seems to be my problem and I don't see a practical way past it. Any ideas besides waiting on 3.6 to release? Am I getting something wrong?




Thanks,

Dave

John Michael Thomas

unread,
Sep 2, 2016, 3:32:02 PM9/2/16
to dotCMS User Group
Yes, unfortunately there's a known issue upgrading directly from a pre-3.2.4 release to 3.5.1: http://dotcms.com/docs/latest/change-log#Pre33Upgrade3.5.1

Your options are to either:

* Do a 2-step upgrade (from 2.5.6 to 3.5 and then from 3.5 to 3.5.1), or
* Upgrade directly from 2.5.6 to 3.6 (which was just released in the past hour) instead.

David Petersheim

unread,
Sep 2, 2016, 7:02:33 PM9/2/16
to dotCMS User Group
Thanks John.
Reply all
Reply to author
Forward
0 new messages