[bioontology-support] 0.5 appliance loading error for SNOMED

[Madani,Sina]

Update:
I was able to bypass the mentioned MYSQL problem by loading SNOMED using LexEVS514 GUI within our local appliance (0.5) and using the included lbconfig.props file (instead of using the appliance Admin utility). I guess I need to update manually some tables for SNOMED meta data.

Sina

From: Madani,Sina
Sent: Monday, April 30, 2012 10:28 AM
To: support at bioontology.org
Subject: 0.5 appliance loading error for SNOMED

Hi ,

Loading SNOMED into Bioportal V 0.5 went through until the end of indexing. But at the very last step I got below error and parsing failed (lexevs log file attached). Do you have any suggestion to fix this? I tried this twice and both times it failed at the very same step.

com.mysql.jdbc.exceptions.jdbc4.CommunicationsException: Communications link failure

Googling the error points to the issue of "netTimeoutForStreamingResults" for very large datasets...

Also, I am not sure if this is a related issue or not but I am getting the error shown in the screenshot below whenever I restart ncbo service.
Is any of the MySQL parameters have been changed in the 0.5 appliance?




[cid:image001.png at 01CD2EAD.93D2FB70]


Thanks!
Sina

-------------- next part --------------
An HTML attachment was scrubbed...
URL: <http://mailman.stanford.edu/pipermail/bioontology-support/attachments/20120510/f7720033/attachment.html>
-------------- next part --------------
A non-text attachment was scrubbed...
Name: image001.png
Type: image/png
Size: 3959 bytes
Desc: image001.png
URL: <http://mailman.stanford.edu/pipermail/bioontology-support/attachments/20120510/f7720033/attachment.png>