-
Type:
Bug
-
Status: Open
-
Resolution: Unresolved
-
Affects Version/s: 7.1.10 DXP GA1
-
Fix Version/s: None
-
Component/s: Core Infrastructure > DB Upgrade Client
-
Labels:None
Issue
If you obtain the DB Upgrade Tools 2.0.1 from the Customer Portal Downloads page, the directory structure is different from what the DB Upgrade Tools 2.0.1 looks like in the 7.1 DXP SP1 bundle and our official upgrade documentation. This undocumented change creates the potential for confusion and error.
Analysis
7.1 DXP SP1 Tomcat Bundle's DB Upgrade Tool Path
liferay:portal-tools-db-upgrade-client liferay$ pwd /Users/liferay/Downloads/liferay-dxp-7.1.10.1-sp1/tools/portal-tools-db-upgrade-client liferay:portal-tools-db-upgrade-client liferay$ find . | sed -e "s/[^-][^\/]*\// |/g" -e "s/|\([^ ]\)/|-\1/" . |-db_upgrade.sh |-db_upgrade.bat |-com.liferay.portal.tools.db.upgrade.client.jar
portal-tools-db-upgrade-client-2.0.1 from Customer Portal Downloads page
liferay:portal-tools-db-upgrade-client-2.0.1 liferay$ pwd /Users/liferay/Downloads/portal-tools-db-upgrade-client-2.0.1 liferay:portal-tools-db-upgrade-client-2.0.1 liferay$ find . | sed -e "s/[^-][^\/]*\// |/g" -e "s/|\([^ ]\)/|-\1/" . |-bin | |-portal-tools-db-upgrade-client | |-portal-tools-db-upgrade-client.bat |-lib | |-db_upgrade.sh | |-db_upgrade.bat | |-com.liferay.portal.tools.db.upgrade.client-2.0.1.jar
Notice in the 7.1 SP1 bundle, it is relatively flat, while the upgrade client from Downloads shows a two folder structure with different naming conventions/scripts (i.e., there are two scripts in bin, and two scripts in lib and the JAR file contains the version number. Also, the upgrade client standalone has a different top folder called portal-tools-db-upgrade-client-2.0.1.
Problem
This makes things confusing since the official documentation suggests running db_upgrade.sh script (db_upgrade.bat on Windows) in the [Liferay Home]/tools/portal-tools-db-upgrade-client.
Note
I've also reported an issue related to this request in LPS-90969, but I wanted to note that because of the naming convention of the JAR file, running db_upgrade.sh results in the following:
liferay:lib liferay$ ./db_upgrade.sh Error: Unable to access jarfile com.liferay.portal.tools.db.upgrade.client.jar
- is related to
-
LPS-90969 Running DB Upgrade Tool 2.0.1 Script results in Error: Unable to access jarfile com.liferay.portal.tools.db.upgrade.client.jar
- Verified
-
LPS-91038 Default suggested paths in DB Upgrade Tool 2.0.1 in Liferay DXP 7.1 SP1 Tomcat bundle
- Verified
- relates
-
LPS-90964 Upgrade Tool on Liferay DXP 7.1.10.1 SP1 Tomcat Bundle throw java.lang.ClassNotFoundException: com.liferay.portal.tools.DBUpgrader
- Closed