The upgrade tool provides the easiest way to upgrade the core and installed modules. Here’s how to use it.
db_upgrade.sh script in the
db_upgrade.bat on Windows) invokes the upgrade tool.
This command prints the upgrade tool usage:
This configuration prevents automatic module upgrade, but causes the upgrade tool to open a Gogo shell for upgrading modules after finishing the core upgrade.
Here are the tool’s default Java parameters:
-Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.timezone=GMT -Xmx2048m
-j option overrides the JVM parameters. For example, these options set the
JVM memory to 10GB, which is a good starting point for this process type:
db_upgrade.sh -j "-Dfile.encoding=UTF-8 -Duser.country=US -Duser.language=en -Duser.timezone=GMT -Xmx10240m"
-l option specifies the tool’s log file name:
db_upgrade.sh -l "output.log"
Here are all the upgrade tool command line options:
–help or -h: Prints the tool’s help message.
–jvm-opts or -j + [arg]: Sets any JVM options for the upgrade process.
–log-file or -l + [arg]: Specifies the tool’s log file name—the
default name is
–shell or -s: Automatically connects you to the Gogo shell after finishing the upgrade process.
It’s time to upgrade your core data using the upgrade tool.
Start the upgrade tool, as the previous section explains. Here are the core upgrade stages:
Show the upgrade patch level
Execute the core upgrade processes
Execute the core verifiers
Monitor the upgrade via the upgrade tool log file (default file is
upgrade.log). If a core upgrade process fails, analyze the failure and resolve
it. If a core upgrade step for Liferay DXP 7.1 (or newer) fails, executing the
upgrade tool again starts it from that step.
If you configured the upgrade tool to upgrade non-core modules, the tool opens a Gogo shell and starts upgrading them. The Gogo shell lets you upgrade modules, check module upgrade status, verify upgrades, and restart module upgrades. Read on to learn how to use Gogo shell commands to complete Liferay DXP upgrades.