Skip to content

Commit 0cae796

Browse files
mnd999mnd999
committed
Additional errors for 42NAC, 50N26, 51N7A
1 parent 67d0942 commit 0cae796

File tree

4 files changed

+85
-0
lines changed

4 files changed

+85
-0
lines changed

‎modules/ROOT/content-nav.adoc‎

Lines changed: 3 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -369,6 +369,7 @@
369369
**** xref:errors/gql-errors/42NA8.adoc[]
370370
**** xref:errors/gql-errors/42NA9.adoc[]
371371
**** xref:errors/gql-errors/42NAA.adoc[]
372+
**** xref:errors/gql-errors/42NAC.adoc[]
372373
**** xref:errors/gql-errors/42NFC.adoc[]
373374
**** xref:errors/gql-errors/42NFD.adoc[]
374375
**** xref:errors/gql-errors/42NFE.adoc[]
@@ -392,6 +393,7 @@
392393
**** xref:errors/gql-errors/50N20.adoc[]
393394
**** xref:errors/gql-errors/50N21.adoc[]
394395
**** xref:errors/gql-errors/50N23.adoc[]
396+
**** xref:errors/gql-errors/50N26.adoc[]
395397
**** xref:errors/gql-errors/50N42.adoc[]
396398
*** xref:errors/gql-errors/index.adoc#system-configuration-or-operation-exceptions[System configuration or operation exceptions]
397399
**** xref:errors/gql-errors/51N00.adoc[]
@@ -469,6 +471,7 @@
469471
**** xref:errors/gql-errors/51N74.adoc[]
470472
**** xref:errors/gql-errors/51N76.adoc[]
471473
**** xref:errors/gql-errors/51N77.adoc[]
474+
**** xref:errors/gql-errors/51N7A.adoc[]
472475
*** xref:errors/gql-errors/index.adoc#procedure-exceptions[Procedure exceptions]
473476
**** xref:errors/gql-errors/52N01.adoc[]
474477
**** xref:errors/gql-errors/52N02.adoc[]

‎modules/ROOT/pages/errors/gql-errors/42NAC.adoc‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
= 42NAC
2+
3+
== Status description
4+
error: syntax error or access rule violation - invalid CREATE DATABASE statement. The backup metadata script contains an invalid or missing CREATE DATABASE statement. The metadata script must contain exactly one CREATE DATABASE statement and it must use the parameter $database.
5+
6+
== Explanation
7+
When using the `existingMetadata: true` option to restore a database from a backup, the backup metadata script must contain exactly one CREATE DATABASE statement. This statement must use the parameter `$database` to specify the name of the database being restored. If the metadata script is missing this statement or contains an invalid statement, the CREATE DATABASE operation will fail with this error.
8+
9+
== Example scenario
10+
For example, try to create a database with using the following command:
11+
12+
[source,cypher]
13+
----
14+
CREATE DATABASE `$databaseString` OPTIONS {existingMetadata:'use', seedUri:'$uri', existingData:'use'}
15+
----
16+
17+
If the backup at `$uri` is missing the required CREATE DATABASE statement, an error will be thrown with GQLSTATUS 42NAC.
18+
19+
== Possible solutions
20+
21+
To resolve this issue, use another backup with a valid metadata script.
22+
23+
ifndef::backend-pdf[]
24+
[discrete.glossary]
25+
== Glossary
26+
27+
include::partial$glossary.adoc[]
28+
endif::[]

‎modules/ROOT/pages/errors/gql-errors/50N26.adoc‎

Lines changed: 28 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,28 @@
1+
= 50N26
2+
3+
== Status description
4+
error: general processing exception - invalid backup metadata script. The backup metadata script contains invalid syntax.
5+
6+
== Explanation
7+
When using the `existingMetadata: true` option to restore a database from a backup, the backup metadata script must contain valid Cypher statements. If the metadata script contains invalid syntax, the restore operation will fail with this error.
8+
9+
== Example scenario
10+
For example, try to create a database with using the following command:
11+
12+
[source,cypher]
13+
----
14+
CREATE DATABASE `$databaseString` OPTIONS {existingMetadata:'use', seedUri:'$uri', existingData:'use'}
15+
----
16+
17+
If the backup at `$uri` constains invalid Cypher syntax in its metadata script, an error will be thrown with GQLSTATUS 50N23.
18+
19+
== Possible solutions
20+
21+
To resolve this issue, use another backup with a valid metadata script.
22+
23+
ifndef::backend-pdf[]
24+
[discrete.glossary]
25+
== Glossary
26+
27+
include::partial$glossary.adoc[]
28+
endif::[]

‎modules/ROOT/pages/errors/gql-errors/51N7A.adoc‎

Lines changed: 26 additions & 0 deletions
Original file line numberDiff line numberDiff line change
@@ -0,0 +1,26 @@
1+
= 51N7A
2+
3+
== Status description
4+
error: system configuration or operation exception - no admin user candidate. No admin user candidate could be found. Please use `neo4j-admin dbms set-default-admin` to select a valid admin.
5+
6+
== Explanation
7+
When initialsing the Neo4j DBMS for the first time, the system will attempt to determine a default admin user. This user is required to perform administrative tasks on the database. If no valid admin user candidate can be found, the system will throw this error.
8+
9+
== Example scenario
10+
For example, before the database starts up for the first time, execute the following command to set a default admin user that does not exist:
11+
12+
[source]
13+
----
14+
neo4j-admin dbms set-default-admin user-that-does-not-exist
15+
----
16+
17+
== Possible solutions
18+
19+
To resolve this issue, run `neo4j-admin dbms set-default-admin` again with a user that does exist in the system.
20+
21+
ifndef::backend-pdf[]
22+
[discrete.glossary]
23+
== Glossary
24+
25+
include::partial$glossary.adoc[]
26+
endif::[]

0 commit comments

Comments
 (0)