Migration From 6.2 GA2 7.0 GA2

[Thirumal Reddy，修改在7 年前。]

Hi All,

can any one teel me ,
how to do Liferay Basic Setup and
Migration from 6.2 GA2 to 7.0 GA2

please give clear description step by step process,

Thanks in advance..

Regards,
Thirumal.

[Juan Gonzalez，修改在7 年前。]

It is usually a good practice to search in dev.liferay.com first:

https://dev.liferay.com/discover/deployment/-/knowledge_base/7-0/upgrading-to-liferay-7

[Thirumal Reddy，修改在7 年前。]

Hi All,
I have seen the link and i did following steps,(Current version is:6.2 GA2)
1.i have downloaded follwing files,
i)liferay-plugins-7.0.1-ga2
ii)liferay-ce-portal-tomcat-7.0-ga2
iii)liferay-ce-portal-src-7.0-ga2
iv)liferay-ide-eclipse-windows-x64-3.0.1-ga2
v)mysql-5.6.31-winx64
vi)jdk1.8.0_92

2.
i)jdk1.8.0_92 installed and configured environment variables
ii)mysql server started,created a new database (production_db) with utf-8. and imported my production database.

3.created a new work space folder and extracted following files inside workspace,
i)liferay-plugins-7.0.1-ga2 extracted and renamed to plugins
ii)liferay-ce-portal-src-7.0-ga2 extracted and renamed to portal
iii)liferay-ce-portal-tomcat-7.0-ga2 extracted and renamed to bundles

4.In bundles folder replaced data folder with my production data folder.

5.created portal-ext.prop file and placed follwing properties inside it,
jdbc.default.driverClassName=com.mysql.jdbc.Driver
jdbc.default.url=jdbc:mysql://localhost/production_db?useUnicode=true&characterEncoding=UTF-8&useFastDateParsing=false
jdbc.default.username=root
jdbc.default.password=
passwords.encryption.algorithm.legacy=SHA

6.I didn't modfied legacy properties and document and media storage, i kept as it is

7.I disabled index's by creating cfg file inside osgi/configs folder with the property,indexReadOnly=true

8.finally, i ran folowing cmd inside portal-tools-db-upgrade-client folder, java -jar com.liferay.portal.tools.db.upgrade.client.jar -j "-Dfile.encoding=UTF8 -Duser.country=US -Duser.language=en -Duser.timezone=GMT -Xmx4096m"

now am getting two exceptions,
i)
08:21:28,392 INFO [main][UpgradeProcess:82] Upgrading com.liferay.portal.upgrade.v7_0_0.UpgradeDocumentLibraryPortletId
08:21:28,393 INFO [main][LoggingTimer:70] Starting com.liferay.portal.upgrade.util.UpgradePortletId#upgradeInstanceablePortletIds
08:21:32,495 WARN [main][UpgradePortletId:436] java.sql.BatchUpdateException: Duplicate entry '10132-20-4-18200_LAYOUT_20-10139' for key 'IX_8D83D0CE'
java.sql.BatchUpdateException: Duplicate entry '10132-20-4-18200_LAYOUT_20-10139' for key 'IX_8D83D0CE'
at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2054)
at com.mysql.jdbc.PreparedStatement.executeBatch(PreparedStatement.java:1467)
at com.liferay.portal.kernel.dao.jdbc.AutoBatchPreparedStatementUtil$ConcurrentBatchInvocationHandler$1.call(AutoBatchPreparedStatementUtil.java:218)
at com.liferay.portal.kernel.dao.jdbc.AutoBatchPreparedStatementUtil$ConcurrentBatchInvocationHandler$1.call(AutoBatchPreparedStatementUtil.java:213)
at java.util.concurrent.FutureTask.run(FutureTask.java:266)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask._runTask(ThreadPoolExecutor.java:756)
at com.liferay.portal.kernel.concurrent.ThreadPoolExecutor$WorkerTask.run(ThreadPoolExecutor.java:667)
at java.lang.Thread.run(Thread.java:745)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLIntegrityConstraintViolationException: Duplicate entry '10132-20-4-18200_LAYOUT_20-10139' for key 'IX_8D83D0CE'
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1040)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4120)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4052)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2503)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2664)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2794)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2458)
at com.mysql.jdbc.PreparedStatement.executeBatchSerially(PreparedStatement.java:2006)
... 7 more


ii)
com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: java.sql.SQLException: Incorrect string value: '\xEC\x84\xB8\xEA\xB3\x84...' for column 'name' at row 3
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:91)
at com.liferay.portal.kernel.upgrade.util.UpgradeProcessUtil._upgradeProcess(UpgradeProcessUtil.java:175)
at com.liferay.portal.kernel.upgrade.util.UpgradeProcessUtil.upgradeProcess(UpgradeProcessUtil.java:143)
at com.liferay.portal.kernel.upgrade.util.UpgradeProcessUtil.upgradeProcess(UpgradeProcessUtil.java:125)
at com.liferay.portal.events.StartupHelper.upgradeProcess(StartupHelper.java:164)
at com.liferay.portal.events.StartupHelperUtil.upgradeProcess(StartupHelperUtil.java:81)
at com.liferay.portal.tools.DBUpgrader.upgrade(DBUpgrader.java:157)
at com.liferay.portal.tools.DBUpgrader.main(DBUpgrader.java:103)
Caused by: com.liferay.portal.kernel.upgrade.UpgradeException: java.sql.SQLException: Incorrect string value: '\xEC\x84\xB8\xEA\xB3\x84...' for column 'name' at row 3
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:91)
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:115)
at com.liferay.portal.upgrade.UpgradeProcess_7_0_0.doUpgrade(UpgradeProcess_7_0_0.java:81)
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:88)
... 7 more
Caused by: java.sql.SQLException: Incorrect string value: '\xEC\x84\xB8\xEA\xB3\x84...' for column 'name' at row 3
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1074)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4120)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4052)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2503)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2664)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2794)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2458)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2375)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2359)
at com.liferay.portal.upgrade.v7_0_0.UpgradeGroup.updateGlobalGroupName(UpgradeGroup.java:62)
at com.liferay.portal.upgrade.v7_0_0.UpgradeGroup.doUpgrade(UpgradeGroup.java:45)
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:88)
... 10 more

my first question, what ever i have done is it correct process.?
for first exception i have seen in the resourcepermission table and UpgradePortletId.java , there i din't found any sol'n for the exception
So, please tell me sol'n to resolve those two exceptions. and next what should i do to complete upgradation process?

Thanks in advance...

regards,
Thirumal.

[Juan Gonzalez，修改在7 年前。]

Thirumal Reddy:

ii)
com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.upgrade.UpgradeException: java.sql.SQLException: Incorrect string value: '\xEC\x84\xB8\xEA\xB3\x84...' for column 'name' at row 3
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:91)
at com.liferay.portal.kernel.upgrade.util.UpgradeProcessUtil._upgradeProcess(UpgradeProcessUtil.java:175)
at com.liferay.portal.kernel.upgrade.util.UpgradeProcessUtil.upgradeProcess(UpgradeProcessUtil.java:143)
at com.liferay.portal.kernel.upgrade.util.UpgradeProcessUtil.upgradeProcess(UpgradeProcessUtil.java:125)
at com.liferay.portal.events.StartupHelper.upgradeProcess(StartupHelper.java:164)
at com.liferay.portal.events.StartupHelperUtil.upgradeProcess(StartupHelperUtil.java:81)
at com.liferay.portal.tools.DBUpgrader.upgrade(DBUpgrader.java:157)
at com.liferay.portal.tools.DBUpgrader.main(DBUpgrader.java:103)
Caused by: com.liferay.portal.kernel.upgrade.UpgradeException: java.sql.SQLException: Incorrect string value: '\xEC\x84\xB8\xEA\xB3\x84...' for column 'name' at row 3
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:91)
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:115)
at com.liferay.portal.upgrade.UpgradeProcess_7_0_0.doUpgrade(UpgradeProcess_7_0_0.java:81)
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:88)
... 7 more
Caused by: java.sql.SQLException: Incorrect string value: '\xEC\x84\xB8\xEA\xB3\x84...' for column 'name' at row 3
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1074)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4120)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4052)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2503)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2664)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2794)
at com.mysql.jdbc.PreparedStatement.executeInternal(PreparedStatement.java:2155)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2458)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2375)
at com.mysql.jdbc.PreparedStatement.executeUpdate(PreparedStatement.java:2359)
at com.liferay.portal.upgrade.v7_0_0.UpgradeGroup.updateGlobalGroupName(UpgradeGroup.java:62)
at com.liferay.portal.upgrade.v7_0_0.UpgradeGroup.doUpgrade(UpgradeGroup.java:45)
at com.liferay.portal.kernel.upgrade.UpgradeProcess.upgrade(UpgradeProcess.java:88)
... 10 more

This seems to be caused by having a non-UTF-8 (with default collation) target database. Please check that.

Thirumal Reddy:

next what should i do to complete upgradation process?

When upgrade fails, you would see a gogo shell console where you can launch some commands. Take a look at upgrade:* commands in the mentioned article upgrade instructions.

[Thirumal Reddy，修改在7 年前。]

Hi Jaun,
Thanks for quick replay,
I have created database with
db charset : utf-8
db collation: utf-8_general_ci

regards,
Thirumal.

[Juan Gonzalez，修改在7 年前。]

Thirumal Reddy:

Hi Jaun,
Thanks for quick replay,
I have created database with
db charset : utf-8
db collation: utf-8_general_ci

regards,
Thirumal.

Just before executing the upgrade, check the actual DB schema charset and probably you would see it isn't UTF8.

[Thirumal Reddy，修改在7 年前。]

actually, while creating database itself i have choosen utf-8.
Ok i will recheck that once.

and what about first exception any suggestion.?

[Juan Gonzalez，修改在7 年前。]

BTW if you use MySQL Workbench for importing the database, it will recreate the schema, that's the reason of not having the right charset.

Be sure to import the data using the right charset, or row data will be wrong encoded.

About the other, that index belongs to:

ResourcePermission (companyId, name, scope, primKey, roleId);

.

There is a Verify process that should remove those duplicated values (made under https://issues.liferay.com/browse/LPS-65718). That is supposed to be fixed under 7.0.1 GA2. Are you sure you're using GA2?

In any case, solution would be getting rows in ResourcePermission with the same companyId, name, scope and primKey, having PowerUser and User as their roleId. Just delete the rows having Power User role as roleId.

[Thirumal Reddy，修改在7 年前。]

Hi Jaun,
I am sure about version i.e, Liferay 7.0.1 GA2

coming to problem,
for primekey "18200_LAYOUT_20" three roleId's are assosiated(10139,10140,10147)
i removed three rows and i started upgradation process i got three rows with same primekey and roleId's but for 10147 actionId is 15 before removing
but after upgradation it is 7. but now i didn't get duplicate entry exception.

for second issue we need to create database with "utf8mb4"

and now i am getting one more issue,
13:10:33,964 ERROR [Framework Event Dispatcher: Equinox Container: e0579182-d645-0016-18a2-9c0af5dcaf01][com_liferay_portal_configuration_persistence:97] FrameworkEvent ERROR
org.osgi.framework.BundleException: Exception in com.liferay.portal.configuration.persistence.activator.ConfigurationPersistenceBundleActivator.start() of bundle com.liferay.portal.configuration.persistence.
at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:795)
at org.eclipse.osgi.internal.framework.BundleContextImpl.start(BundleContextImpl.java:724)
at org.eclipse.osgi.internal.framework.EquinoxBundle.startWorker0(EquinoxBundle.java:951)
at org.eclipse.osgi.internal.framework.EquinoxBundle$EquinoxModule.startWorker(EquinoxBundle.java:328)
at org.eclipse.osgi.container.Module.doStart(Module.java:566)
at org.eclipse.osgi.container.Module.start(Module.java:434)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1582)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.incStartLevel(ModuleContainer.java:1562)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.doContainerStartLevel(ModuleContainer.java:1533)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1476)
at org.eclipse.osgi.container.ModuleContainer$ContainerStartLevel.dispatchEvent(ModuleContainer.java:1)
at org.eclipse.osgi.framework.eventmgr.EventManager.dispatchEvent(EventManager.java:230)
at org.eclipse.osgi.framework.eventmgr.EventManager$EventThread.run(EventManager.java:340)
Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 767 bytes
at sun.reflect.NativeConstructorAccessorImpl.newInstance0(Native Method)
at sun.reflect.NativeConstructorAccessorImpl.newInstance(NativeConstructorAccessorImpl.java:62)
at sun.reflect.DelegatingConstructorAccessorImpl.newInstance(DelegatingConstructorAccessorImpl.java:45)
at java.lang.reflect.Constructor.newInstance(Constructor.java:423)
at com.mysql.jdbc.Util.handleNewInstance(Util.java:411)
at com.mysql.jdbc.Util.getInstance(Util.java:386)
at com.mysql.jdbc.SQLError.createSQLException(SQLError.java:1053)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4120)
at com.mysql.jdbc.MysqlIO.checkErrorPacket(MysqlIO.java:4052)
at com.mysql.jdbc.MysqlIO.sendCommand(MysqlIO.java:2503)
at com.mysql.jdbc.MysqlIO.sqlQueryDirect(MysqlIO.java:2664)
at com.mysql.jdbc.ConnectionImpl.execSQL(ConnectionImpl.java:2788)
at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1816)
at com.mysql.jdbc.StatementImpl.executeUpdate(StatementImpl.java:1730)
at com.liferay.portal.configuration.persistence.ConfigurationPersistenceManager.createConfigurationTable(ConfigurationPersistenceManager.java:262)
at com.liferay.portal.configuration.persistence.ConfigurationPersistenceManager.start(ConfigurationPersistenceManager.java:165)
at com.liferay.portal.configuration.persistence.activator.ConfigurationPersistenceBundleActivator.start(ConfigurationPersistenceBundleActivator.java:63)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:774)
at org.eclipse.osgi.internal.framework.BundleContextImpl$3.run(BundleContextImpl.java:1)
at java.security.AccessController.doPrivileged(Native Method)
at org.eclipse.osgi.internal.framework.BundleContextImpl.startActivator(BundleContextImpl.java:767)
... 12 more

i searched for it but it is unresolved LPS-66854
So how can i complete my upgradation process..?
and please confirm the process(previous post) what i am doing is it correct or not?

Regards,
Thirumal.

[Thirumal Reddy，修改在7 年前。]

hello Jaun,
I am waiting for your replay.
please give me quick replay.

Thanks..

[Arun Das，修改在7 年前。]

Hi,

Caused by: com.mysql.jdbc.exceptions.jdbc4.MySQLSyntaxErrorException: Specified key was too long; max key length is 767 bytes

Can you try the solution stated here

Run this query in mysql
SET @@global.innodb_large_prefix = 1;
and try the upgrade again

Arun

[Thirumal Reddy，修改在7 年前。]

Hi Arun,

Arun Das:

Run this query in mysql
SET @@global.innodb_large_prefix = 1;
and try the upgrade again

Even though it is throwing same exceptions.

[Arun Das，修改在7 年前。]

Hi,
Try to execute the following in mysql console / workbench

SET @@global.innodb_file_format = 'barracuda';
SET @@global.innodb_file_per_table = 1;
SET @@global.innodb_large_prefix = 1;

Once the above queries are executed, please post the results for the following queries here

SHOW VARIABLES LIKE 'innodb_file_format';

SHOW VARIABLES LIKE 'innodb_file_per_table';

SHOW VARIABLES LIKE 'innodb_large_prefix';

Make sure your liferay is not running. Once the query is done, restart the upgrade process

Arun

[Thirumal Reddy，修改在7 年前。]

Hi Arun,
Thanks for your replay,
if i change database charset to utf8mb4 i am getting
18a2-9c0af5dcaf01][com_liferay_portal_configuration_persistence:97] FrameworkEvent ERROR (you can see previous posts for more log.)

so please clarify me ,
which charset and collation i need to use and
if i use charset is utf8, what query's i need to run before running upgrdation
if i use charset is utf8mb4,what query's i need to run before running upgrdation

Please cleaerly send the process.

if you give soln it's great help to me .

Thanks in advance..

regards,
Thirumal.

[Arun Das，修改在7 年前。]

Hi,
I've updated the post. Sorry for confusing it up

Arun

[Thirumal Reddy，修改在7 年前。]

Hi Arun,
I have created a database with charset:utf8, collation:utf8_general_ci
and i have run

SET @@global.innodb_file_format = 'barracuda';
SET @@global.innodb_file_per_table = 1;
SET @@global.innodb_large_prefix = 1;

after that i run following query's

1.SHOW VARIABLES LIKE 'innodb_file_format';
2.SHOW VARIABLES LIKE 'innodb_file_per_table';
3.SHOW VARIABLES LIKE 'innodb_large_prefix';
O/P:
1.barracuda
2.ON
3.ON

now can i start upgradation process?
or before upgradation do i need to change anything?

regards,
Thirumal.

[Arun Das，修改在7 年前。]

Hi,
All good. Can u try the upgrade process?

Arun

[Thirumal Reddy，修改在7 年前。]

Ok
Thank you so much..

[Thirumal Reddy，修改在7 年前。]

Hi Arun,

Again i am getting same problem,
please see my log file.
to resolve this what should i do...?

[Arun Das，修改在7 年前。]

Hi,
Seems like some of your tables is not in utf8 charset. Following is the script to convert to utf8 collation.

SELECT CONCAT("ALTER TABLE ",TABLE_SCHEMA,".",TABLE_NAME," CHARACTER SET utf8 COLLATE utf8_general_ci;   ", 
"ALTER TABLE ",TABLE_SCHEMA,".",TABLE_NAME," CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;  ") AS alter_sql 
FROM information_schema.TABLES WHERE TABLE_SCHEMA = 'lportal' INTO OUTFILE 'alter_sql.txt'

Once you run the script in mysql, a file named alter_sql.txt will be created(search in your mysql folder. If linux then you can find in /var/lib/mysql/lportal.) with queries to convert your database tables to utf8 charset.
The content in alter_sql.txt will look like

ALTER TABLE lportal.Account_ CHARACTER SET utf8 COLLATE utf8_general_ci;
ALTER TABLE lportal.Account_ CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;
ALTER TABLE lportal.Address CHARACTER SET utf8 COLLATE utf8_general_ci;
ALTER TABLE lportal.Address CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci;
ALTER TABLE lportal.AnnouncementsDelivery CHARACTER SET utf8 COLLATE utf8_general_ci;

and so on.
Run all the queries from the alter_sql.txt. This solves all the issues like

Caused by: java.sql.SQLException: Incorrect string value: '\xEC\x84\xB8\xEA\xB3\x84...' for column 'name' at row 3

Next,execute the following script

ALTER TABLE `ResourcePermission` DROP INDEX `IX_8D83D0CE`, ADD INDEX `IX_8D83D0CE` (`companyId`,`name`,`scope`,`primKey`,`roleId`)

and this will solve your

java.sql.BatchUpdateException: Duplicate entry '10132-20-4-18200_LAYOUT_20-10139' for key 'IX_8D83D0CE'

issue. Now run your upgrade again.

Arun

[Thirumal Reddy，修改在7 年前。]

Hi Arun,
Thanks for replay,
It resolved previous errors,
but after runnung alter_sql.txt i got some errors,for two tables(user_ and marketplace_module)

Index column size too large. The maximum column size is 767 bytes.
ALTER TABLE lportal7ga2.marketplace_module CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci
ALTER TABLE lportal7ga2.user_ CONVERT TO CHARACTER SET utf8 COLLATE utf8_general_ci
i think this error got because of length of column, in user_(openId length=1024) and in marketplace_module (bundleSymbolicName length=500)
i verfied user_ and marketplace_module tables charest and collation those are modified to utf8 and utf8_general_ci.so that i started my upgradation process.
Is it OK.?

But i got some other exceptions,

java.lang.RuntimeException: com.liferay.portal.kernel.upgrade.UpgradeException: com.liferay.portal.kernel.xml.DocumentException: Error on line 1 of document : The markup in the document following the root element must be well-formed. Nested exception: The markup in the document following the root element must be well-formed.

for this exception i have seen my journal article table in that content column data is not welformed means the data is not placed inside <xml>and <root> tag. am i correct?
If it is Yes, i will modify those and i will run again upgradation process

07:09:44,528 ERROR [default-11][GroupImpl:580] com.liferay.portal.kernel.exception.NoSuchLayoutSetException: No LayoutSet exists with the key {groupId=66210, privateLayout=false}
can i ignore this?

07:50:23,286 ERROR [main][VerifyProcessTracker:221] com.liferay.portal.verify.VerifyException: com.liferay.dynamic.data.mapping.validator.DDMFormValidationException$MustNotDuplicateFieldName: The field name subject cannot be defined more than once

07:54:24,365 ERROR [main][ServiceConfiguratorImpl:156] Unable to initialize service component
com.liferay.portal.kernel.exception.OldServiceComponentException: Build namespace Calendar has build number 9 which is newer than 5

I don't know how to resolve these. plg give some suggestions

for more info plg see my log file.
Thanks in advance..
I am waiting for your replay...

[Arun Das，修改在7 年前。]

Hi,
Seems like the upgrade was completed.

Completed Liferay core upgrade and verify processes in 9090 seconds

Index column size too large. The maximum column size is 767 bytes.

should not be there, as you have previously set global.innodb_large_prefix = 1;
For the errors I'm not sure whether you can safely ignore those as I'm no expert. May be Juan Gonzalez or David can help

Arun

[Thirumal Reddy，修改在7 年前。]

Hi Arun,
Thank you so much for your replay's

with this statement i thought that, upgradation process not yet completed.

Checking to see if all upgrades have completed... your upgrades have failed, have not started, or are still running.

with this statement can i trust as , my upgradation process is completed.?

Completed Liferay core upgrade and verify processes in 9090 seconds

If it is can i start Migration of 6.2 GA2 plugins into 7.0.1 Environment.?

As well as i started migration in Liferay 7 Basic setup, but here i am unable to migrate Ext's and themes?
If you know anything regarding these please suggest.
And as per themes, themesupgradation toll is not working properly in windows , and even i am unable create new theme as legacy(plugins sdk) so what steps i need to follow?
I dont know how to create themes with modularity.

And one more dought, In 6.2 in portal/portal-web there is a build-themes but in 7.0 i am not seeing that. why i am asking this because i am able to create themes after building build-themes in 6.2.

I am migrating portlets into plugins sdk, after importing portlet, i got some errors and i resolved and deployed successfully, and i am able to access the portlet from controlpanel. but i am not seeing the portlets in tomcat/webapps location, like whenever we deploy any plugin in 6.2 we will see a copy in tomcat/webapps location but in 7 i am not seeing that

And can you explain about project template Name category's ,like
i)activator
ii)contenttargetingrule
iii)contenttargetingtrackingaction
iv)controlmenuentry
v)mvcportlet(NR)
vi)portlet(NR)
vi)service
vii)servicebuilder(NR)
and
viii)servicewrapper
I have seen all these about in liferay developer network but i didn't understand properly.

Once again thanks arun for your replays,

regards,
Thirumal.

[Thirumal Reddy，修改在7 年前。]

Hi Arun,
can you please give replay to this,
https://web.liferay.com/community/forums/-/message_boards/message/76751560