Knowledgebase
Slow startup due to large database
Posted by John Villanueva on 07 August 2017 08:03 PM

Note: This problem only affects versions 9.3 and higher. 

 

If your JSCAPE MFT Server takes too long to complete its startup process, it's probably because the built-in H2 database has grown too large. Although the length of time could vary, a 4GB database would typically take between 20-30 minutes to start up. One way to remedy the problem is to compact the database. 

Please follow the steps below to do compact the database. Make sure that, in step 4, you don't execute the next command until the previous one has completed execution. If the previous one generates an error, don't proceed to the next. If you're executing the command remotely using SSH, we recommend you use the screen command to avoid getting lost if the remote session disconnects. 


1) Stop JSCAPE MFT Server. In your case, you may have to do a "kill -5". Please make sure it is really stopped. Kindly do a "ps -efwww" and confirm there is no java process running JSCAPE MFT Server.

2) Create a backup of your "data" directory

3) Copy the attached mft_trunc_db.sql into <mftserver installdir>

4) Execute the following commands in sequence while inside <mftserver installdir>.

java -Xmx2048m -cp libs/h2-1.4.191.jar org.h2.tools.RunScript -url jdbc:h2:./data/server -user server -password server -script mft_trunc_db.sql

java -Xmx2048m -cp libs/h2-1.4.191.jar org.h2.tools.Script -url jdbc:h2:./data/server -user server -password server -script backup.sql

mv data data1

java -Xmx2048m -cp libs/h2-1.4.191.jar org.h2.tools.RunScript -url jdbc:h2:./data/server -user server -password server -script backup.sql

5) Start JSCAPE MFT Server service 



Attachments 
 
 mft_trunc_db.sql (0.14 KB)
(0 vote(s))
This article was helpful
This article was not helpful

Comments (0)
Post a new comment
 
 
Full Name:
Email:
Comments:
Help Desk Software by Kayako fusion