RE: Migration of Postgresql DBASE from LR 6.2 to LR 7.1

om prakash, modified 5 Years ago. New Member Posts: 3 Join Date: 3/19/20 Recent Posts
Hi Folks,I was migrating Postgresql DBASE from 6.2 to 7.1, during this I am facing below issue.

Exception in thread "main" java.lang.ClassNotFoundException: com.liferay.portal.tools.DBUpgrader
at java.net.URLClassLoader.findClass(URLClassLoader.java:381)
at java.lang.ClassLoader.loadClass(ClassLoader.java:424)
at java.lang.ClassLoader.loadClass(ClassLoader.java:357)
at com.liferay.portal.tools.db.upgrade.client.DBUpgraderLauncher.main(DBUpgraderLauncher.java:43)

​​​​​​​
Following steps are done as part of migrating DB.
Changed app-server.properties file (Located at \liferay-dxp-tomcat-7.1.10-ga5\tools\portal-tools-db-upgrade-client) 
Changed DB properties 
Changed Liferay.home entry
created a file com.liferay.portal.search.configuration.IndexStatusManagerConfiguration.cfg at \liferay-dxp-tomcat-7.1.10-ga5/osgi/configs 
and add the following content.
indexReadOnly=true.
Tried in Liferay Tomcat  SP1,SP2,SP3,SP4 and GA5 versions but resulting the same error,some one please help us to get rid of this issue ?
thumbnail
Alberto Chaparro Terleira, modified 5 Years ago. Liferay Master Posts: 560 Join Date: 4/25/11 Recent Posts
Hi Om,
The DBUpgrader class is part of the portal-impl.jar so that means that the portal can't see that jar.
Please, check the app-server.propertie and remember that the URLs are relative to the dir property, for example, for this:
dir=/lsc/app-servers/tma-upgrade/liferay-dxp-7.2.10-dxp-4/tomcat-9.0.17
extra.lib.dirs=/lsc/app-servers/tma-upgrade/liferay-dxp-7.2.10-dxp-4/tomcat/bin
global.lib.dir=/lsc/app-servers/tma-upgrade/liferay-dxp-7.2.10-dxp-4/tomcat/lib
portal.dir=/lsc/app-servers/tma-upgrade/liferay-dxp-7.2.10-dxp-4/tomcat/webapps/ROOT
server.detector.server.id=tomcat
It should be:
dir=/lsc/app-servers/tma-upgrade/liferay-dxp-7.2.10-dxp-4/tomcat-9.0.17
extra.lib.dirs=/bin
global.lib.dir=/lib
portal.dir=/webapps/ROOT
server.detector.server.id=tomcat


Please, let us know if this fixes the issue.