-
Notifications
You must be signed in to change notification settings - Fork 35
Additional errors for 42NAC, 50N26, 51N7A #398
New issue
Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.
By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.
Already on GitHub? Sign in to your account
Merged
Merged
Changes from 3 commits
Commits
Show all changes
11 commits
Select commit
Hold shift + click to select a range
0cae796
Additional errors for 42NAC, 50N26, 51N7A
mnd999 56711d6
Fixes
mnd999 b3024a5
Apply suggestions from code review
mnd999 e6392b3
Apply suggestions from code review
mnd999 29349b6
Update modules/ROOT/pages/errors/gql-errors/42NAC.adoc
renetapopova 7c716e0
Update modules/ROOT/pages/errors/gql-errors/42NAC.adoc
renetapopova b2415a3
regenerate the index file
renetapopova 3f94f78
Apply suggestion from @renetapopova
renetapopova eabfbe9
Apply suggestion from @renetapopova
renetapopova 16e57f9
Merge branch 'dev' into dev-errors-cypherops
renetapopova 68ce936
regenerate the index file
renetapopova File filter
Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
There are no files selected for viewing
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| = 42NAC | ||
|
|
||
| == Status description | ||
| 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. | ||
renetapopova marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
renetapopova marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| == Explanation | ||
| When using the `existingMetadata: use` 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. | ||
mnd999 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| == Example scenario | ||
| For example, try to create a database with using the following command: | ||
renetapopova marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| [source,cypher] | ||
| ---- | ||
| CREATE DATABASE `$databaseString` OPTIONS {existingMetadata:'use', seedUri:'$uri', existingData:'use'} | ||
| ---- | ||
|
|
||
| If the backup at `$uri` is missing the required CREATE DATABASE statement, an error will be thrown with GQLSTATUS 42NAC. | ||
mnd999 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| == Possible solutions | ||
|
|
||
| To resolve this issue, use another backup with a valid metadata script. | ||
|
|
||
| ifndef::backend-pdf[] | ||
| [discrete.glossary] | ||
| == Glossary | ||
|
|
||
| include::partial$glossary.adoc[] | ||
| endif::[] | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,28 @@ | ||
| = 50N26 | ||
mnd999 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| == Status description | ||
| error: general processing exception - invalid backup metadata script. The backup metadata script contains invalid syntax. | ||
|
|
||
| == Explanation | ||
| 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. | ||
mnd999 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| == Example scenario | ||
| For example, try to create a database with using the following command: | ||
renetapopova marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| [source,cypher] | ||
| ---- | ||
| CREATE DATABASE `$databaseString` OPTIONS {existingMetadata:'use', seedUri:'$uri', existingData:'use'} | ||
| ---- | ||
|
|
||
| If the backup at `$uri` contains invalid Cypher syntax in its metadata script, an error will be thrown with GQLSTATUS 50N26. | ||
|
|
||
| == Possible solutions | ||
|
|
||
| To resolve this issue, use another backup with a valid metadata script. | ||
|
|
||
| ifndef::backend-pdf[] | ||
| [discrete.glossary] | ||
| == Glossary | ||
|
|
||
| include::partial$glossary.adoc[] | ||
| endif::[] | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
| Original file line number | Diff line number | Diff line change |
|---|---|---|
| @@ -0,0 +1,26 @@ | ||
| = 51N7A | ||
mnd999 marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| == Status description | ||
| 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. | ||
mnd999 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| == Explanation | ||
| 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. | ||
mnd999 marked this conversation as resolved.
Outdated
Show resolved
Hide resolved
|
||
|
|
||
| == Example scenario | ||
| 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: | ||
|
|
||
| [source] | ||
| ---- | ||
| neo4j-admin dbms set-default-admin user-that-does-not-exist | ||
| ---- | ||
|
|
||
| == Possible solutions | ||
|
|
||
| To resolve this issue, run `neo4j-admin dbms set-default-admin` again with a user that does exist in the system. | ||
renetapopova marked this conversation as resolved.
Show resolved
Hide resolved
|
||
|
|
||
| ifndef::backend-pdf[] | ||
| [discrete.glossary] | ||
| == Glossary | ||
|
|
||
| include::partial$glossary.adoc[] | ||
| endif::[] | ||
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Add this suggestion to a batch that can be applied as a single commit.
This suggestion is invalid because no changes were made to the code.
Suggestions cannot be applied while the pull request is closed.
Suggestions cannot be applied while viewing a subset of changes.
Only one suggestion per line can be applied in a batch.
Add this suggestion to a batch that can be applied as a single commit.
Applying suggestions on deleted lines is not supported.
You must change the existing code in this line in order to create a valid suggestion.
Outdated suggestions cannot be applied.
This suggestion has been applied or marked resolved.
Suggestions cannot be applied from pending reviews.
Suggestions cannot be applied on multi-line comments.
Suggestions cannot be applied while the pull request is queued to merge.
Suggestion cannot be applied right now. Please check back later.
Uh oh!
There was an error while loading. Please reload this page.