[Virtuoso-users] Not able to load large .nq files into virtuoso

[Rose B. <ros...@gm...>]

Dear Developers,

I installed 07.00.3207 OpenLink Virtuoso. After this I tried to load
dbpedia to virtuoso.   When loading 40+  GB files using DB.DBA.TTLP_MTWhen
loading large files (2GB) using
DB.DBA.TTLP_MT(file_to_string_output('filename'),'','graphname',512);
virtuoso hangs (CPU usage 0%). Within my virtuoso.ini file I have allocated
64 GB RAM to virtuoso.

The output after running virtuoso is mentioned below:

/usr/local/virtuoso-opensource/bin# ./virtuoso-t -f -c
/usr/local/virtuoso-opensource/var/lib/virtuoso/db/virtuoso.ini

04:48:30 SQL Optimizer enabled (max 1000 layouts)
04:48:31 Compiler unit is timed at 0.000286 msec
04:48:36 built-in procedure "repl_undot_name" overruled by the RDBMS
04:48:38 Roll forward started
04:48:38 Roll forward complete
04:48:39 Checkpoint started
04:48:40 Checkpoint finished, log reused
04:48:40 HTTP/WebDAV server online at 8890
04:48:40 Server online at 1111 (pid 4988)
04:52:54 * Monitor: Locks are held for a long time
04:54:55 * Monitor: Locks are held for a long time
04:56:55 * Monitor: Locks are held for a long time
05:01:07 * Monitor: Locks are held for a long time
05:03:07 * Monitor: Locks are held for a long time
05:05:08 * Monitor: Locks are held for a long time
05:07:09 * Monitor: Locks are held for a long time
05:09:10 * Monitor: Locks are held for a long time
05:11:10 * Monitor: Locks are held for a long time
05:13:11 * Monitor: Locks are held for a long time
05:15:22 * Monitor: Locks are held for a long time
05:17:30 * Monitor: Locks are held for a long time
05:19:43 * Monitor: Locks are held for a long time
05:29:50 * Monitor: Locks are held for a long time
05:31:51 * Monitor: Locks are held for a long time
05:33:54 * Monitor: Locks are held for a long time
05:35:56 * Monitor: Locks are held for a long time
05:37:59 * Monitor: Locks are held for a long time
05:39:59 * Monitor: Locks are held for a long time
05:41:59 * Monitor: Locks are held for a long time
05:44:02 * Monitor: Locks are held for a long time
05:46:02 * Monitor: Locks are held for a long time
05:48:02 * Monitor: Locks are held for a long time
05:49:35 * Monitor: Should read for update because lock escalation from
shared to exclusive fails frequently (1)
05:50:03 * Monitor: Locks are held for a long time
05:50:52 Checkpoint started
05:52:06 Checkpoint finished, log reused
05:52:13 * Monitor: Locks are held for a long time
06:02:52 * Monitor: Many lock waits
06:04:52 * Monitor: Many lock waits
06:06:52 * Monitor: Many lock waits

I tried to set DefaultIsolation = 2 in virtuoso.ini as mentioned at:
https://github.com/openlink/virtuoso-opensource/issues/40. However, still
Virtuoso continues to hang with 0% CPU usage.

Can someone please help