rvesse commented on a change in pull request #13:
URL: https://github.com/apache/jena-site/pull/13#discussion_r446201644
##########
File path: source/documentation/tdb/faqs.md
##########
@@ -181,4 +192,24 @@ RAM, trading off against requests by other applications.
But it also means
the database files are not properly deleted until the JVM exits. A new
dataset can not be created in the same location (directory on disk).
-The workaround is to use a different location.
\ No newline at end of file
+The workaround is to use a different location.
+
+## What is the *Unable to check TDB lock owner, the lock file contents appear
to be for a TDB2 database. Please try loading this location as a TDB2 database*
error? {#tdb2-lock}
+
+As described elsewhere in this FAQ (see [Lock Exceptions](#lock-exception)
+and [No Lock Warning](#no-lock-warning)) TDB uses a lock file to ensure that
multiple
+JVMs don't try to use the same TDB database simultaneously as this can lead to
+data corruption. However with the introduction of [TDB2](../tdb2/) there are
now two
+versions of TDB, TDB2 also uses a lock file however it uses a slightly
different
+format for that file.
+
+This error means that you have tried to open a [TDB2](../tdb2/) database as a
TDB1
+database which is not permitted. Please adjust your usage of Jena libraries
or command
+line tools to use TDB2 code/arguments as appropriate.
+
+For example if [Using TDB2 with Fuseki](../tdb2/tdb2_fuseki.html) you would
need to use
+the `--tdb2` option.
+
+## My question isn't answered here? {#not-answered}
+
+If your question isn't answered here please get in touch with the project,
please check out the [Ask](../help_and_support/index.html) page for ways to ask
for further help.
Review comment:
Good spot, fixed
----------------------------------------------------------------
This is an automated message from the Apache Git Service.
To respond to the message, please log on to GitHub and use the
URL above to go to the specific comment.
For queries about this service, please contact Infrastructure at:
[email protected]
