Foros de discusión

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

thumbnail
Adam T, modificado hace 12 años.

Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

Junior Member Mensajes: 34 Fecha de incorporación: 12/06/07 Mensajes recientes
I was on 5.2.3 with permissions algorithm 2. I upgraded successfully to 6.0, migrated from permissions algorithm 2 to 6.

Now when I try to upgrade from 6.0 to 6.1 I get the following error messages:

14:07:33,508 INFO [UpgradeProcess:207] Upgrading com.liferay.portal.upgrade.v6_1_0.UpgradeSchema
14:07:34,087 WARN [BaseDB:382] Duplicate column name 'userName': alter table BookmarksEntry add userName varchar(75) null;

14:07:34,128 WARN [BaseDB:382] Duplicate column name 'userName': alter table BookmarksFolder add userName varchar(75) null;

14:07:34,158 WARN [BaseDB:382] Can't DROP 'IX_975996C0'; check that column/key exists: drop index IX_975996C0 on Company;

14:07:34,428 WARN [BaseDB:382] Duplicate column name 'mimeType': alter table DLFileEntry add mimeType varchar(75) null;

14:07:35,761 WARN [BaseDB:382] Can't DROP 'IX_CE705D48'; check that column/key exists: drop index IX_CE705D48 on DLFileRank;

14:07:35,763 WARN [BaseDB:382] Can't DROP 'IX_40B56512'; check that column/key exists: drop index IX_40B56512 on DLFileRank;

14:07:35,763 WARN [BaseDB:382] Duplicate column name 'fileEntryId': alter table DLFileRank add fileEntryId bigint;

14:07:35,764 WARN [BaseDB:382] Can't DROP 'IX_55C736AC'; check that column/key exists: drop index IX_55C736AC on DLFileShortcut;

14:07:35,766 WARN [BaseDB:382] Can't DROP 'IX_346A0992'; check that column/key exists: drop index IX_346A0992 on DLFileShortcut;

14:07:35,782 WARN [BaseDB:382] Duplicate column name 'toFileEntryId': alter table DLFileShortcut add toFileEntryId bigint;

14:07:35,800 WARN [BaseDB:382] Can't DROP 'IX_B413F1EC'; check that column/key exists: drop index IX_B413F1EC on DLFileVersion;

14:07:35,801 WARN [BaseDB:382] Can't DROP 'IX_94E784D2'; check that column/key exists: drop index IX_94E784D2 on DLFileVersion;

14:07:35,801 WARN [BaseDB:382] Can't DROP 'IX_2F8FED9C'; check that column/key exists: drop index IX_2F8FED9C on DLFileVersion;

14:07:35,947 WARN [BaseDB:382] Duplicate column name 'fileEntryId': alter table DLFileVersion add fileEntryId bigint;

14:07:35,949 WARN [BaseDB:382] Duplicate column name 'mimeType': alter table DLFileVersion add mimeType varchar(75) null;

14:07:36,477 WARN [BaseDB:382] Duplicate column name 'userName': alter table IGFolder add userName varchar(75) null;

14:07:36,478 WARN [BaseDB:382] Duplicate column name 'userName': alter table IGImage add userName varchar(75) null;

14:07:40,845 WARN [BaseDB:382] Can't DROP 'IX_5ABC2905'; check that column/key exists: drop index IX_5ABC2905 on LayoutSet;

14:07:40,984 WARN [BaseDB:382] Duplicate column name 'allowAnonymous': alter table MBMailingList add allowAnonymous tinyint;

14:07:41,048 WARN [BaseDB:382] Duplicate column name 'companyId': alter table MBThread add companyId bigint;

14:07:41,049 WARN [BaseDB:382] Duplicate column name 'rootMessageUserId': alter table MBThread add rootMessageUserId bigint;

14:07:41,328 WARN [BaseDB:382] Table 'PortalPreferences' already exists: create table PortalPreferences ( portalPreferencesId bigint not null primary key, ownerId bigint, ownerType integer, preferences longtext null) engine InnoDB;

14:07:41,356 WARN [BaseDB:382] Duplicate column name 'ownerId': alter table ResourcePermission add ownerId bigint;

14:07:41,396 WARN [BaseDB:382] Duplicate column name 'type_': alter table Ticket add type_ integer;

14:07:41,397 WARN [BaseDB:382] Duplicate column name 'extraInfo': alter table Ticket add extraInfo longtext null;

14:07:41,602 WARN [BaseDB:382] Duplicate column name 'addedByLDAPImport': alter table UserGroup add addedByLDAPImport tinyint;

14:07:41,606 WARN [BaseDB:382] Table 'UserGroups_Teams' already exists: create table UserGroups_Teams ( userGroupId bigint not null, teamId bigint not null, primary key (userGroupId, teamId)) engine InnoDB;

14:07:41,607 WARN [BaseDB:382] Table 'UserNotificationEvent' already exists: create table UserNotificationEvent ( uuid_ varchar(75) null, userNotificationEventId bigint not null primary key, companyId bigint, userId bigint, type_ varchar(75) null, timestamp bigint, deliverBy bigint, payload longtext null, archived tinyint) engine InnoDB;

14:07:41,608 WARN [BaseDB:382] Table 'VirtualHost' already exists: create table VirtualHost ( virtualHostId bigint not null primary key, companyId bigint, layoutSetId bigint, hostname varchar(75) null) engine InnoDB;


Also

14:07:48,727 INFO [UpgradeProcess:207] Upgrading com.liferay.portal.upgrade.v6_1_0.UpgradeDocumentLibrary
14:07:48,937 ERROR [MainServlet:201] com.liferay.portal.kernel.events.ActionException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'folderId' in 'field list'
com.liferay.portal.kernel.events.ActionException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'folderId' in 'field list'
at com.liferay.portal.events.StartupAction.run(StartupAction.java:58)
at com.liferay.portal.servlet.MainServlet.processStartupEvents(MainServlet.java:1284)
at com.liferay.portal.servlet.MainServlet.init(MainServlet.java:198)
at javax.servlet.GenericServlet.init(GenericServlet.java:160)
at org.apache.catalina.core.StandardWrapper.initServlet(StandardWrapper.java:1266)
at org.apache.catalina.core.StandardWrapper.loadServlet(StandardWrapper.java:1185)
at org.apache.catalina.core.StandardWrapper.load(StandardWrapper.java:1080)
at org.apache.catalina.core.StandardContext.loadOnStartup(StandardContext.java:5015)
at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5302)
at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:897)
at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:873)
at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:615)
at org.apache.catalina.startup.HostConfig.deployDescriptor(HostConfig.java:649)
at org.apache.catalina.startup.HostConfig$DeployDescriptor.run(HostConfig.java:1581)
at java.util.concurrent.Executors$RunnableAdapter.call(Executors.java:441)
at java.util.concurrent.FutureTask$Sync.innerRun(FutureTask.java:303)
at java.util.concurrent.FutureTask.run(FutureTask.java:138)
at java.util.concurrent.ThreadPoolExecutor$Worker.runTask(ThreadPoolExecutor.java:885)
at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:907)
at java.lang.Thread.run(Thread.java:619)
Caused by: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'folderId' in 'field list'
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:213)
at com.liferay.portal.upgrade.UpgradeProcessUtil._upgradeProcess(UpgradeProcessUtil.java:103)
at com.liferay.portal.upgrade.UpgradeProcessUtil.upgradeProcess(UpgradeProcessUtil.java:56)
at com.liferay.portal.upgrade.UpgradeProcessUtil.upgradeProcess(UpgradeProcessUtil.java:36)
at com.liferay.portal.events.StartupHelper.upgradeProcess(StartupHelper.java:81)
at com.liferay.portal.events.StartupHelperUtil.upgradeProcess(StartupHelperUtil.java:48)
at com.liferay.portal.tools.DBUpgrader.upgrade(DBUpgrader.java:119)
at com.liferay.portal.events.StartupAction.doRun(StartupAction.java:144)
at com.liferay.portal.ee.license.StartupAction.doRun(Unknown Source)
at com.liferay.portal.events.StartupAction.run(StartupAction.java:52)
... 20 more
Caused by: com.liferay.portal.kernel.upgrade.UpgradeException: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'folderId' in 'field list'
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:213)
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:227)
at com.liferay.portal.upgrade.UpgradeProcess_6_1_0.doUpgrade(UpgradeProcess_6_1_0.java:64)
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:210)
... 29 more
Caused by: com.mysql.jdbc.exceptions.MySQLSyntaxErrorException: Unknown column 'folderId' in 'field list'
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:936)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:2985)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:1631)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:1723)
at com.mysql.jdbc.Connection.execSQL(Connection.java:3256)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:1313)
at com.mysql.jdbc.PreparedStatement.executeQuery(PreparedStatement.java:1448)
at com.mchange.v2.c3p0.impl.NewProxyPreparedStatement.executeQuery(NewProxyPreparedStatement.java:76)
at com.liferay.portal.upgrade.v6_1_0.UpgradeDocumentLibrary.updateFileRanks(UpgradeDocumentLibrary.java:195)
at com.liferay.portal.upgrade.v6_1_0.UpgradeDocumentLibrary.doUpgrade(UpgradeDocumentLibrary.java:87)
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:210)
... 32 more


My portal-ext.properties file contains the following entries:

image.hook.impl=com.liferay.portal.image.DatabaseHook
dl.hook.impl=com.liferay.documentlibrary.util.JCRHook
jcr.initialize.on.startup=false
jcr.workspace.name=liferay
jcr.node.documentlibrary=documentlibrary
jcr.jackrabbit.repository.root=/root/liferay/jackrabbit
jcr.jackrabbit.config.file.path=${jcr.jackrabbit.repository.root}/repository.xml
jcr.jackrabbit.repository.home=${jcr.jackrabbit.repository.root}/home
jcr.jackrabbit.credentials.username=none
jcr.jackrabbit.credentials.password=none

Everything has been done using Tomcat bundles. Anyone run into similar issues and figure out what is happening?
thumbnail
David H Nebinger, modificado hace 12 años.

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

Liferay Legend Mensajes: 14914 Fecha de incorporación: 2/09/06 Mensajes recientes
Was this perchance your second attempt at trying to upgrade from 6.0 to 6.1?

If the upgrade failed the first time, you need to restore your database/filesystem components before any further attempts at upgrading.
thumbnail
Adam T, modificado hace 12 años.

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

Junior Member Mensajes: 34 Fecha de incorporación: 12/06/07 Mensajes recientes
David, I have seen this behavior in the past after a failed update but in this instance this is a freshly upgraded to 6.0 copy of the document library and the database.

I've lost count of the number of times I have reset my environment prior to each upgrade attempt with different portal-ext.properties.
thumbnail
Hitoshi Ozawa, modificado hace 12 años.

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

Liferay Legend Mensajes: 7942 Fecha de incorporación: 24/03/10 Mensajes recientes
Seems to be similar to LPS-23109. Liferay.com is saying they can't reproduce it. If you can give move concrete steps, it may be worthwhile to recreate an issue (don't write comment to the current issue because it's already been closed.)

http://issues.liferay.com/browse/LPS-23109

Also, the following thread may also be the cause:
http://issues.liferay.com/browse/LPS-25750
thumbnail
Juan Carrey Labarta, modificado hace 12 años.

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

Junior Member Mensajes: 31 Fecha de incorporación: 15/08/11 Mensajes recientes
You need the upgrade process to be : (If you are in 6.0.5 EE SP2)

6_0_12_to_6_1_0
and then, 6_1_10

The folderId column is created in 6_1_10
thumbnail
Adam T, modificado hace 12 años.

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

Junior Member Mensajes: 34 Fecha de incorporación: 12/06/07 Mensajes recientes
Juan Carrey Labarta:
You need the upgrade process to be : (If you are in 6.0.5 EE SP2)

6_0_12_to_6_1_0
and then, 6_1_10

The folderId column is created in 6_1_10


Juan, could you explain this more?

I started with 5.2.3 ce then upgraded to 6.0-ee-sp2. Now I am trying to run 6.1.10-ee-ga1.

I am allowing Liferay to run the upgrade scripts automatically. Are you saying I should run them manually to fix this?
thumbnail
David H Nebinger, modificado hace 12 años.

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

Liferay Legend Mensajes: 14914 Fecha de incorporación: 2/09/06 Mensajes recientes
I should hope not. The liferay upgrade process does more than just make database changes, it will also do index changes and filesystem changes. Running just the sql to update manually would bypass these other upgrade processes and possibly lead to environment corruption...
thumbnail
Juan Carrey Labarta, modificado hace 12 años.

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

Junior Member Mensajes: 31 Fecha de incorporación: 15/08/11 Mensajes recientes
Not manually, but there is a portal-ext property called (update.processes) that takes a comma separated value of classes, explained on a graph that i cannot find, but it says whats the path between your version, and the current version.

The last version of the 6.1 EE is the upgrade processes 6_1_10 that i mentioned, but the automatic update stops at 6_1_0

I recently updated to 6.1 EE, and that error happends to me when i forgot the last upgrade.processes from 6_1_0 to 6_1_10
Andy Fraley, modificado hace 12 años.

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

New Member Mensajes: 5 Fecha de incorporación: 9/02/11 Mensajes recientes
I had the same problem. I was able to complete the upgrade by placing the following in portal-ext.properties:

upgrade.processes=com.liferay.portal.upgrade.UpgradeProcess_6_0_12_to_6_1_0,com.liferay.portal.upgrade.UpgradeProcess_6_1_1
Gowtham Mani, modificado hace 12 años.

RE: Upgrade from 6.0 EE to 6.1 EE UpgradeSchema Duplicate column name

New Member Mensajes: 2 Fecha de incorporación: 13/01/12 Mensajes recientes
I tried the solution given by Andey and it works fine for me

Regards,
Gowtham