Challenges exporting large HSQLDB to import into Oracle - need a guru's advice

Hello, I could really use some help here…

I inherited a very large xWiki knowledgebase with a 20GB HSQL database that was running extremely slow (like, try to open a page and get a cup of coffee while it opens). It was also on a craptastic machine with a Linux OS.

It is on version 8.4.2. I managed to get the install working on a Windows 2016 server with dual CPU’s and 8 gigs of RAM using Tomcat instead of the previous Jetty. For now, it seems to work much better but I know that I’m on borrowed time with HSQLDB.

My problem is migrating out of HSQLDB and into Oracle. Yes, I’ve tried both the regular export and the Large XAR export, plus I’ve tried to break up the exports according to the 80+ namespaces into separate files, with very poor results.

xWiki will not even attempt to import the 300MB single XAR. No errors in the logs, it just hangs. After breaking up the XAR into multiple files, the Administrative panel seems to go awry – when I switch to Oracle, I end up with a totally empty wiki with just the ability to import and XAR. When I start importing, I reach an impasse where permissions becomes a problem, extensions don’t work, etc. I’m not sure if there is an order to the imports that I should know about.

I have tried to do a fresh, clean install and then to start importing the multiple XAR’s. Same problems as above.

So I gave up and decided a different approach: to try to get a dump of the HSQL database in the hopes of importing the data manually into Oracle. (Praying that the structures are exactly the same).

I am not familiar with HSQLDB, but I found a utility called RazorSQL that supposedly could generate the DDL’s for the tables and export the data. However, for the life of me I cannot get a connection and I don’t know what it wants. My connection url is as follows:

jdbc:hsqldb:file:D:/data/database/xwiki_db;shutdown=true;sreadonly=true

I’m getting Access denied errors from the .lck file – but I know that I am using the same username and password as set in the hibernate file…

Could really use some advice here.