Message Boards

  1. Home
  2. Development
  3. Database migration LF 6.2 GA2 to LF 6.2 GA6

Database migration LF 6.2 GA2 to LF 6.2 GA6

Tinfo Tinfo, modified 3 Years ago.

Database migration LF 6.2 GA2 to LF 6.2 GA6

New Member Posts: 14 Join Date: 5/14/20 Recent Posts
Hello, i'm trying to migrate a 6.2 GA2 liferay portal to 6.2 GA6 version, i've unzipped a fresh 6.2 GA6 portal, copy pasted the data folder from the older portal and attached the database, the expected behaviour was to see the database upgrade procedure but nothing happens, in the release table the portal build number remain 6201, is there a way to upgrade the database with some tool like the one present in the 7.* portal? In catalina.out i have the following logs:
15:34:33,112 INFO  [localhost-startStop-1][DialectDetector:71] Determine dialect for MySQL 5
15:34:33,139 INFO  [localhost-startStop-1][DialectDetector:136] Found dialect org.hibernate.dialect.MySQLDialect
Starting Liferay Portal Community Edition 6.2 CE GA6 (Newton / Build 6205 / January 6, 2016)
15:34:56,045 INFO  [localhost-startStop-1][StartupAction:97] There are no patches installed
15:34:57,109 INFO  [localhost-startStop-1][BaseDB:484] Database does not support case sensitive queries
15:34:57,599 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyDB2
15:34:57,601 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyMySQL
15:34:57,629 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyOracle
15:34:57,631 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifySQLServer
15:34:57,632 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyUUID
15:34:57,686 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyPermission
15:35:11,364 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyGroup
15:35:23,099 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyRole
15:35:23,236 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyAsset
15:35:23,251 INFO  [localhost-startStop-1][UpgradeProcess:164] Upgrading com.liferay.portal.upgrade.util.UpgradeAssetPublisherManualEntries
15:35:23,254 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyAuditedModel
15:35:23,635 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyBlogs
15:35:24,999 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyBookmarks
15:35:25,029 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyDynamicDataMapping
15:35:25,619 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyGroupId
15:35:25,901 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyJournal
15:35:27,284 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyLayout
15:35:37,676 INFO  [localhost-startStop-1][VerifyProcess:65] Verifying com.liferay.portal.verify.VerifyMessageBoards
Sep 25, 2020 3:37:05 PM org.apache.catalina.startup.HostConfig deployDescriptors
SEVERE: Error waiting for multi-thread deployment of context descriptors to complete
java.util.concurrent.ExecutionException: java.lang.OutOfMemoryError: GC overhead limit exceeded
    at java.util.concurrent.FutureTask.report(FutureTask.java:122)
    at java.util.concurrent.FutureTask.get(FutureTask.java:188)
    at org.apache.catalina.startup.HostConfig.deployDescriptors(HostConfig.java:595)
    at org.apache.catalina.startup.HostConfig.deployApps(HostConfig.java:491)
    at org.apache.catalina.startup.HostConfig.start(HostConfig.java:1660)
    at org.apache.catalina.startup.HostConfig.lifecycleEvent(HostConfig.java:335)
    at org.apache.catalina.util.LifecycleSupport.fireLifecycleEvent(LifecycleSupport.java:117)
    at org.apache.catalina.util.LifecycleBase.fireLifecycleEvent(LifecycleBase.java:90)
    at org.apache.catalina.util.LifecycleBase.setStateInternal(LifecycleBase.java:402)
    at org.apache.catalina.util.LifecycleBase.setState(LifecycleBase.java:347)
    at org.apache.catalina.core.ContainerBase.startInternal(ContainerBase.java:1140)
    at org.apache.catalina.core.StandardHost.startInternal(StandardHost.java:819)
    at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:150)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1575)
    at org.apache.catalina.core.ContainerBase$StartChild.call(ContainerBase.java:1565)
    at java.util.concurrent.FutureTask.run(FutureTask.java:262)
    at java.util.concurrent.ThreadPoolExecutor.runWorker(ThreadPoolExecutor.java:1145)
    at java.util.concurrent.ThreadPoolExecutor$Worker.run(ThreadPoolExecutor.java:615)
    at java.lang.Thread.run(Thread.java:745)
Caused by: java.lang.OutOfMemoryError: GC overhead limit exceeded
    at com.mysql.jdbc.SingleByteCharsetConverter.toString(SingleByteCharsetConverter.java:327)
    at com.mysql.jdbc.ResultSetRow.getString(ResultSetRow.java:819)
    at com.mysql.jdbc.ByteArrayRow.getString(ByteArrayRow.java:70)
    at com.mysql.jdbc.ResultSetImpl.getStringInternal(ResultSetImpl.java:5816)
    at com.mysql.jdbc.ResultSetImpl.getTimestampInternal(ResultSetImpl.java:6582)
    at com.mysql.jdbc.ResultSetImpl.getTimestamp(ResultSetImpl.java:6192)
    at com.mysql.jdbc.ResultSetImpl.getTimestamp(ResultSetImpl.java:6230)
    at com.mchange.v2.c3p0.impl.NewProxyResultSet.getTimestamp(NewProxyResultSet.java:2082)
    at org.hibernate.type.descriptor.sql.TimestampTypeDescriptor$2.doExtract(TimestampTypeDescriptor.java:62)
    at org.hibernate.type.descriptor.sql.BasicExtractor.extract(BasicExtractor.java:64)
    at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:254)
    at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:250)
    at org.hibernate.type.AbstractStandardBasicType.nullSafeGet(AbstractStandardBasicType.java:230)
    at org.hibernate.type.AbstractStandardBasicType.hydrate(AbstractStandardBasicType.java:331)
    at org.hibernate.persister.entity.AbstractEntityPersister.hydrate(AbstractEntityPersister.java:2283)
    at org.hibernate.loader.Loader.loadFromResultSet(Loader.java:1527)
    at org.hibernate.loader.Loader.instanceNotYetLoaded(Loader.java:1455)
    at org.hibernate.loader.Loader.getRow(Loader.java:1355)
    at org.hibernate.loader.Loader.getRowFromResultSet(Loader.java:611)
    at org.hibernate.loader.Loader.doQuery(Loader.java:829)
    at org.hibernate.loader.Loader.doQueryAndInitializeNonLazyCollections(Loader.java:274)
    at org.hibernate.loader.Loader.doList(Loader.java:2542)
    at org.hibernate.loader.Loader.listIgnoreQueryCache(Loader.java:2276)
    at org.hibernate.loader.Loader.list(Loader.java:2271)
    at org.hibernate.hql.classic.QueryTranslatorImpl.list(QueryTranslatorImpl.java:940)
    at org.hibernate.engine.query.HQLQueryPlan.performList(HQLQueryPlan.java:196)
    at org.hibernate.impl.SessionImpl.list(SessionImpl.java:1268)
    at org.hibernate.impl.QueryImpl.list(QueryImpl.java:102)
    at com.liferay.portal.dao.orm.hibernate.QueryImpl.list(QueryImpl.java:113)
    at com.liferay.portal.dao.orm.hibernate.QueryImpl.list(QueryImpl.java:104)
    at com.liferay.portal.kernel.dao.orm.QueryUtil.list(QueryUtil.java:170)
    at com.liferay.portlet.messageboards.service.persistence.MBThreadPersistenceImpl.findAll(MBThreadPersistenceImpl.java:13625)
Sep 25, 2020 3:37:05 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/life621/tomcat-7.0.62/webapps/marketplace-portlet
Sep 25, 2020 3:37:06 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Sep 25, 2020 3:37:06 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/life621/tomcat-7.0.62/webapps/marketplace-portlet has finished in 1,101 ms
Sep 25, 2020 3:37:06 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/life621/tomcat-7.0.62/webapps/web-form-portlet
Sep 25, 2020 3:37:07 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Sep 25, 2020 3:37:07 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/life621/tomcat-7.0.62/webapps/web-form-portlet has finished in 844 ms
Sep 25, 2020 3:37:07 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/life621/tomcat-7.0.62/webapps/notifications-portlet
Sep 25, 2020 3:37:08 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Sep 25, 2020 3:37:08 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/life621/tomcat-7.0.62/webapps/notifications-portlet has finished in 883 ms
Sep 25, 2020 3:37:08 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/life621/tomcat-7.0.62/webapps/opensocial-portlet
Sep 25, 2020 3:37:10 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Sep 25, 2020 3:37:10 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/life621/tomcat-7.0.62/webapps/opensocial-portlet has finished in 1,605 ms
Sep 25, 2020 3:37:10 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/life621/tomcat-7.0.62/webapps/kaleo-web
Sep 25, 2020 3:37:10 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Sep 25, 2020 3:37:10 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/life621/tomcat-7.0.62/webapps/kaleo-web has finished in 931 ms
Sep 25, 2020 3:37:10 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/life621/tomcat-7.0.62/webapps/sync-web
Sep 25, 2020 3:37:11 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Sep 25, 2020 3:37:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/life621/tomcat-7.0.62/webapps/sync-web has finished in 988 ms
Sep 25, 2020 3:37:11 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/life621/tomcat-7.0.62/webapps/resources-importer-web
Sep 25, 2020 3:37:12 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Sep 25, 2020 3:37:12 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/life621/tomcat-7.0.62/webapps/resources-importer-web has finished in 657 ms
Sep 25, 2020 3:37:12 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deploying web application directory /opt/life621/tomcat-7.0.62/webapps/calendar-portlet
Sep 25, 2020 3:37:13 PM org.apache.catalina.startup.TldConfig execute
INFO: At least one JAR was scanned for TLDs yet contained no TLDs. Enable debug logging for this logger for a complete list of JARs that were scanned but no TLDs were found in them. Skipping unneeded JARs during scanning can improve startup time and JSP compilation time.
Sep 25, 2020 3:37:13 PM org.apache.catalina.startup.HostConfig deployDirectory
INFO: Deployment of web application directory /opt/life621/tomcat-7.0.62/webapps/calendar-portlet has finished in 981 ms
Sep 25, 2020 3:37:13 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["http-bio-2080"]
Sep 25, 2020 3:37:13 PM org.apache.coyote.AbstractProtocol start
INFO: Starting ProtocolHandler ["ajp-bio-2009"]
Sep 25, 2020 3:37:13 PM org.apache.catalina.startup.Catalina start
INFO: Server startup in 178380 ms
thumbnail
Alberto Chaparro, modified 3 Years ago.

RE: Database migration LF 6.2 GA2 to LF 6.2 GA6

Liferay Master Posts: 549 Join Date: 4/25/11 Recent Posts
Hi Tinfo,

it seems you are getting an OutOfMemoryError when the portal tries to get all MBThreads. 

You have two options to fix this:
  1.  Adding more memory to the JVM before starting the server. You can check the size of MBThread table to get an idea, it can be the size of that table + 1 GB.
  2. Since it's a minor upgrade process probably you can skip the VerifyMessageBoards process. You can configure that with this property:
    https://github.com/liferay/liferay-portal/blob/6.2.x/portal-impl/src/portal.properties#L220
Here is the list of all verify processes to be executed:https://github.com/liferay/liferay-portal/blob/6.2.x/portal-impl/src/com/liferay/portal/verify/VerifyProcessSuite.java#L23

You can define which ones to be executed in this way (this is just an example):
​​​​​​​verify.processes=com.liferay.portal.verify.VerifyJournal,\
com.liferay.portal.verify.VerifyLayout,\
com.liferay.portal.verify.VerifyOrganization,\
com.liferay.portal.verify.VerifyPortletPreferences,\
com.liferay.portal.verify.VerifyRegion,\
com.liferay.portal.verify.VerifyResourcePermissions,\
com.liferay.portal.verify.VerifyUser,\
com.liferay.portal.verify.VerifyWiki,\
com.liferay.portal.verify.VerifyWorkflow

Configure the property with all verifiers in the VerifyProcessSuite except for VerifyMessageBoards

​​​​​​​I hope it helps.