7.3 Upgrade fails with out of memory error in converting Report Content step
Hello,
we tried to upgrade our test envirnment and ran into a java.lang.OutOfMemoryError: Java heap space Error during the Convertinf Report Content part of the upgrade.
What can we do now to "salvage" the update and how do we add more memory to the upgrade tool?
Many thanks.
Best regards,
Ingo
P.s.: Upgrade command line feedback
--- Installing ---
Backing up webapp ................................................... [OK]
Updating libraries .................................................. [OK]
Updating libraries .................................................. [OK]
Updating libraries .................................................. [OK]
Updating Yellowfin Schema ........................................... [OK]
Converting Report Content ........................................... [OK]
Converting Report Content ........................................... [OK]
Converting Report Content
Installation Error
An error occurred during installation:
java.lang.OutOfMemoryError: Java heap space
java.lang.OutOfMemoryError: Java heap space
at java.nio.charset.Charset.decode(Charset.java:806)
at com.mysql.jdbc.StringUtils.toString(StringUtils.java:1871)
at com.mysql.jdbc.ResultSetRow.getString(ResultSetRow.java:821)
at com.mysql.jdbc.BufferRow.getString(BufferRow.java:542)
at com.mysql.jdbc.ResultSetImpl.getStringInternal(ResultSetImpl.java:5816)
at com.mysql.jdbc.ResultSetImpl.getString(ResultSetImpl.java:5693)
at com.mysql.jdbc.ResultSetImpl.getStringForClob(ResultSetImpl.java:5744)
at com.mysql.jdbc.ResultSetImpl.getObject(ResultSetImpl.java:4996)
at com.hof.dbtool.DBInterface.executeSelect(DBInterface.java:154)
at com.hof.dbtool.DBInterface.executeSelect(DBInterface.java:104)
at com.hof.patch.process.job.ReportFieldTemplateRow.selectReportFieldTemplates(ReportFieldTemplateRow.java:196)
at com.hof.patch.process.job.UpdateContent73Job.updateReportFieldTemplatesDimensionTypeCodes(UpdateContent73Job.j
at com.hof.patch.process.job.UpdateContent73Job.run(UpdateContent73Job.java:91)
at com.hof.patch.PatchInstaller.runInstallJobs(PatchInstaller.java:459)
at com.hof.patch.cmd.CmdInstaller.install(CmdInstaller.java:131)
at com.hof.patch.cmd.CmdInstaller.main(CmdInstaller.java:34)
at com.hof.patch.PatchInstaller.runCmd(PatchInstaller.java:762)
at com.hof.patch.PatchInstaller.runInstaller(PatchInstaller.java:726)
at com.hof.patch.PatchInstaller.main(PatchInstaller.java:796)
[FAILED]
The same problem 
Hi Ryan,
since the tomcat's -Xmx parameter was already set to 12g I decided to add those parameters to the jac -ja call directly and that seems to have helped although the memory never really went beyond 2.7g from what I can tell.
java -jar -Xms128m -Xmx12g ...
Best regards,
Ingo
Hi Ryan,
since the tomcat's -Xmx parameter was already set to 12g I decided to add those parameters to the jac -ja call directly and that seems to have helped although the memory never really went beyond 2.7g from what I can tell.
java -jar -Xms128m -Xmx12g ...
Best regards,
Ingo
Hello Ingo,
Thanks for reaching out with the issue you're experiencing. The first thing you're going to want to do is go ahead and roll back this Yellowfin instance. Before trying the upgrade again, make sure you have valid backups of both the Yellowfin Configuration Database and the Yellowfin installation folder.
I'd recommend increasing your JVM Memory by following the instructions here before you try the upgrade again. Setting this a little overkill isn't a bad idea, as it can always be adjusted back later.
After doing this try your upgrade again and let me know if you're able to get your test instance upgraded.
Thanks,
Ryan
Hello Ingo,
Thanks for reaching out with the issue you're experiencing. The first thing you're going to want to do is go ahead and roll back this Yellowfin instance. Before trying the upgrade again, make sure you have valid backups of both the Yellowfin Configuration Database and the Yellowfin installation folder.
I'd recommend increasing your JVM Memory by following the instructions here before you try the upgrade again. Setting this a little overkill isn't a bad idea, as it can always be adjusted back later.
After doing this try your upgrade again and let me know if you're able to get your test instance upgraded.
Thanks,
Ryan
Hi Ryan,
since the tomcat's -Xmx parameter was already set to 12g I decided to add those parameters to the jac -ja call directly and that seems to have helped although the memory never really went beyond 2.7g from what I can tell.
java -jar -Xms128m -Xmx12g ...
Best regards,
Ingo
Hi Ryan,
since the tomcat's -Xmx parameter was already set to 12g I decided to add those parameters to the jac -ja call directly and that seems to have helped although the memory never really went beyond 2.7g from what I can tell.
java -jar -Xms128m -Xmx12g ...
Best regards,
Ingo
Hi Ingo,
I'm glad to hear you were able to get your instance upgraded.
Have a great week,
Ryan
Hi Ingo,
I'm glad to hear you were able to get your instance upgraded.
Have a great week,
Ryan
Replies have been locked on this page!