Skip to content

Commit 8f1199d

Browse files
committed
Add 25, 2D, and 42 codes
1 parent 2c2494a commit 8f1199d

File tree

1 file changed

+243
-27
lines changed

1 file changed

+243
-27
lines changed

modules/ROOT/pages/errors/gql-errors.adoc

Lines changed: 243 additions & 27 deletions
Original file line numberDiff line numberDiff line change
@@ -7,10 +7,14 @@
77
The following page provides an overview of all GQLSTATUS server error codes in Neo4j.
88
All errors in Neo4j have severity level `ERROR`.
99

10+
<<<<<<< HEAD
1011
* <<_connection-exceptions, Connection exceptions>>
1112
* <<_data-exceptions, Data exceptions>>
1213

1314
[[_connection-exceptions]]
15+
=======
16+
17+
>>>>>>> cf8ebb1 (Add 25, 2D, and 42 codes)
1418
== Connection exceptions
1519
1620
Connection exceptions occur when the client is unable to connect to the server for various reasons such as network issues, server-side routing being disabled, or the database being unavailable, etc.
@@ -105,117 +109,329 @@ Status description:: error: connection exception - no such routing policy. Polic
105109
Database exceptions occur when a client request contains the wrong format, types, or other unsupported input.
106110
Some examples are data and constraint creation, which conflicts with existing constraints, properties of non-storable type, and spatial and temporal values with invalid components.
107111
108-
=== 22N00
112+
=== 22N00
109113
110114
Status description:: error: data exception - unsupported value. The provided value is unsupported and cannot be processed.
111115
112-
=== 22N01
116+
=== 22N01
113117
114118
Status description:: error: data exception - invalid type.
115119
Expected the value { $value } to be of type { $valueTypeList }, but was of type { $valueType }.
116120
117-
=== 22N02
121+
=== 22N02
118122
119123
Status description:: error: data exception - specified negative numeric value. Expected { $option } to be a positive number but found { $value } instead.
120124
121-
=== 22N03
125+
=== 22N03
122126
123127
Status description:: error: data exception - specified numeric value out of range. Expected { $component } to be of type { $valueType } and in the range { $lower } to { $upper } but found { $value }.
124128
125-
=== 22N04
129+
=== 22N04
126130
127131
Status description:: error: data exception - invalid input value. Invalid input { $input } for { $context }. Expected one of { $inputList }.
128132
129133
=== 22N05
130134
131135
Status description:: error: data exception - input failed validation. Invalid input { $input } for { $context }.
132136
133-
=== 22N06
137+
=== 22N06
134138
135139
Status description:: error: data exception - empty input string. Invalid input. { $option } needs to be specified.
136140
137-
=== 22N07
141+
=== 22N07
138142
139143
Status description:: error: data exception - invalid pre-parser option key. Invalid pre-parser option(s): { $optionList }.
140144
141-
=== 22N08
145+
=== 22N08
142146
143147
Status description:: error: data exception - invalid pre-parser combination. Invalid pre-parser option, cannot combine { $option1 } with { $option2 }.
144148
145-
=== 22N09
149+
=== 22N09
146150
147151
Status description:: error: data exception - conflicting pre-parser combination. Invalid pre-parser option, cannot specify multiple conflicting values for { $option }.
148152
149-
=== 22N10
153+
=== 22N10
150154
151155
Status description:: error: data exception - invalid pre-parser option value. Invalid pre-parser option, specified { $input } is not valid for option { $option }. Valid options are: { $optionList }.
152156
153-
=== 22N11
157+
=== 22N11
154158
155159
Status description:: error: data exception - invalid argument. Invalid argument: cannot process { $input }.
156160
157-
=== 22N12
161+
=== 22N12
158162
159163
Status description:: error: data exception - invalid date, time, or datetime format. Invalid argument: cannot process { $input }.
160164
161-
=== 22N13
165+
=== 22N13
162166
163167
Status description:: error: data exception - invalid time zone. Specified time zones must include a date component.
164168
165-
=== 22N14
169+
=== 22N14
166170
167171
Status description:: error: data exception - invalid temporal value combination. Cannot select both { $temporal } and { $component }.
168172
169-
=== 22N15
173+
=== 22N15
170174
171175
Status description:: error: data exception - invalid temporal component. Cannot read the specified { $component } component from { $temporal }.
172176
173-
=== 22N16
177+
=== 22N16
174178
175179
Status description:: error: data exception - invalid import value. Importing entity values to a graph with a USE clause is not supported. Attempted to import { $expr } to { $graph }.
176180
177-
// === 22N17
181+
// === 22N17
178182
179183
// Status description:: error: data exception - invalid date, time, or datetime function field name. Cannot read the specified { $component } component from { $temporal }.
180184
181-
=== 22N18
185+
=== 22N18
182186
183187
Status description:: error: data exception - incomplete spatial value. A { $crs } POINT must contain { $mapKeyList }.
184188
185-
=== 22N19
189+
=== 22N19
186190
187191
Status description:: error: data exception - invalid spatial value. A POINT must contain either 'x' and 'y', or 'latitude' and 'longitude'.
188192
189-
=== 22N20
193+
=== 22N20
190194
191195
Status description:: error: data exception - invalid spatial value dimensions. Cannot create POINT with { $dim1 }D coordinate reference system (CRS) and { $value } coordinates. Use the equivalent { $dim2 }D coordinate reference system instead.
192196
193-
=== 22N21
197+
=== 22N21
194198
195199
Status description:: error: data exception - unsupported coordinate reference system. Unsupported coordinate reference system (CRS): { $crs }.
196200
197-
=== 22N22
201+
=== 22N22
198202
199203
Status description:: error: data exception - invalid spatial value combination. Cannot specify both coordinate reference system (CRS) and spatial reference identifier (SRID).
200204
201-
=== 22N23
205+
=== 22N23
202206
203207
Status description:: error: data exception - invalid latitude value. Cannot create WGS84 POINT with invalid coordinate: { $coordinates }. The valid range for the latitude coordinate is [-90, 90].
204208
205-
=== 22N24
209+
=== 22N24
206210
207211
Status description:: error: data exception - invalid coordinate arguments. Cannot construct a { $valueType } from { $coordinates }.
208212
209-
=== 22N25
213+
=== 22N25
210214
211215
Status description:: error: data exception - invalid temporal arguments. Cannot construct a { $valueType } from { $temporal }.
212216
213-
=== 22N26
217+
=== 22N26
214218
215219
Status description:: error: data exception - unsupported rounding mode. Unknown rounding mode. Valid values are: CEILING, FLOOR, UP, DOWN, HALF_EVEN, HALF_UP, HALF_DOWN, UNNECESSARY.
216220
217-
=== 22N27
221+
=== 22N27
218222
219223
Status description:: error: data exception - invalid entity type. Invalid input { $input } for { $variable }. Expected to be one of { $valueTypeList }.
220224
221225
226+
== Invalid transaction state
227+
228+
Invalid transaction state errors occur when the client attempts to perform an operation that is not allowed in the current transaction state.
229+
230+
=== 25N01
231+
232+
Status description:: error: invalid transaction state - invalid combination of statement types.Failed to execute the query { $query } due to conflicting statement types (read query, write query, schema modification, or administration command). To execute queries in the same transaction, they must be either of the same type, or be a combination of schema modifications and read commands.
233+
234+
=== 25N02
235+
236+
Status description:: error: invalid transaction state - unable to complete transaction. Unable to complete transaction. See debug log for details.
237+
238+
=== 25N03
239+
240+
Status description:: error: invalid transaction state - concurrent access violation. Transaction is being used concurrently by another request.
241+
242+
=== 25N04
243+
244+
Status description:: error: invalid transaction state - specified transaction does not exist.
245+
Transaction { $transactionId } does not exist.
246+
247+
=== 25N05
248+
249+
Status description:: error: invalid transaction state - transaction terminated or closed. The transaction has been terminated or closed.
250+
251+
=== 25N06
252+
253+
Status description:: error: invalid transaction state - transaction start failed. Failed to start transaction. See debug log for details.
254+
255+
=== 25N07
256+
257+
Status description:: error: invalid transaction state - constituent transaction start failed. Failed to start constituent transaction. See debug log for details.
258+
259+
=== 25N08
260+
261+
Status description:: error: invalid transaction state - invalid transaction lease. The lease for the transaction is no longer valid.
262+
263+
=== 25N09
264+
265+
Status description:: error: invalid transaction state - internal transaction failure. The transaction failed due to an internal error.
266+
267+
=== 25N11
268+
269+
Status description:: error: invalid transaction state - conflicting transaction state. There was a conflict detected between the transaction state and applied updates. Please retry the transaction.
270+
271+
=== 25N12
272+
273+
Status description:: error: invalid transaction state - index was dropped. Index { $idx } was dropped in this transaction and cannot be used.
274+
275+
=== 25N13
276+
277+
Status description:: error: invalid transaction state - cannot access entity after removal. A { $entityType } was accessed after being deleted in this transaction. Verify the transaction statements.
278+
279+
== Invalid transaction termination
280+
281+
=== 2DN01
282+
283+
Status description:: error: invalid transaction termination - commit failed. Failed to commit transaction. See debug log for details.
284+
285+
=== 2DN02
286+
287+
Status description:: error: invalid transaction termination - constituent commit failed. Failed to commit constituent transaction. See debug log for details.
288+
289+
=== 2DN03
290+
291+
Status description:: error: invalid transaction termination - transaction termination failed. Failed to terminate transaction. See debug log for details.
292+
293+
=== 2DN04
294+
295+
Status description:: error: invalid transaction termination - constituent transaction termination failed. Failed to terminate constituent transaction. See debug log for details.
296+
297+
=== 2DN05
298+
299+
Status description:: error: invalid transaction termination - failed to apply transaction. There was an error on applying the transaction. See logs for more information.
300+
301+
=== 2DN06
302+
303+
Status description:: error: invalid transaction termination - failed to append transaction. There was an error on appending the transaction. See logs for more information.
304+
305+
=== 2DN07
306+
307+
Status description:: error: invalid transaction termination - inner transactions still open. Unable to commit transaction because it still have non-closed inner transactions.
308+
309+
[[transaction-rollback]]
310+
== Transaction rollback
311+
312+
=== 40N01
313+
314+
Status description:: error: transaction rollback - rollback failed. Failed to rollback transaction. See debug log for details.
315+
316+
=== 40N02
317+
318+
Status description:: error: transaction rollback - constituent rollback failed. Failed to rollback constituent transaction. See debug log for details.
319+
320+
[[syntax-error-access-rule-violation]]
321+
== Syntax error or access rule violation
322+
323+
=== 42N01
324+
325+
Status description:: error: syntax error or access rule violation - no such constituent graph exists in composite database. The constituent graph { $graph } was not found in the in composite database { $db }. Verify that the spelling is correct.
326+
327+
=== 42N02
328+
329+
Status description:: error: syntax error or access rule violation - writing in read access mode. Writing in read access mode not allowed.
330+
331+
=== 42N03
332+
333+
Status description:: error: syntax error or access rule violation - writing to multiple graphs. Writing to multiple graphs in the same transaction is not allowed. Use CALL IN TRANSACTION or create separate transactions in your application.
334+
335+
=== 42N04
336+
337+
Status description:: error: syntax error or access rule violation - unsupported access of composite database. Failed to access database identified by { $db1 } while connected to session database { $db2 }. Connect to { $db3 } directly.
338+
339+
=== 42N05
340+
341+
Status description:: error: syntax error or access rule violation - unsupported access of standard database. Failed to access database identified by { $db1 } while connected to composite session database { $db2 }. Connect to { $db3 } directly or create an alias in the composite database.
342+
343+
=== 42N06
344+
345+
Status description:: error: syntax error or access rule violation - unsupported action on composite database. { $action } is not supported on composite databases.
346+
347+
=== 42N07
348+
349+
Status description:: error: syntax error or access rule violation - variable already defined. The variable { $var } is shadowing a variable with the same name from the outer scope and needs to be renamed.
350+
351+
=== 42N08
352+
353+
Status description:: error: syntax error or access rule violation - no such procedure or function. The procedure or function { $procFun } was not registered for this database instance. Verify that the spelling is correct.
354+
355+
=== 42N09
356+
357+
Status description:: error: syntax error or access rule violation - no such user. A user with the name { $user } was not found. Verify that the spelling is correct.
358+
359+
=== 42N10
360+
361+
Status description:: error: syntax error or access rule violation - no such role. A role with the name { $role } was not found. Verify that the spelling is correct.
362+
363+
=== 42N11
364+
365+
Status description:: error: syntax error or access rule violation - database or alias already exists. A [composite] database or alias with the name { $db } already exists.
366+
367+
=== 42N12
368+
369+
Status description:: error: syntax error or access rule violation - user already exists. A user with the name { $user } already exists.
370+
371+
=== 42N13
372+
373+
Status description:: error: syntax error or access rule violation - role already exists. A role with the name { $role } already exists.
374+
375+
=== 42N14
376+
377+
Status description:: error: syntax error or access rule violation - invalid use of command. { $clause } cannot be used together with `$cmd`.
378+
379+
=== 42N15
380+
381+
Status description:: error: syntax error or access rule violation - invalid use of reserved keyword. { $syntax } is a reserved keyword and cannot be used in this place.
382+
383+
=== 42N16
384+
385+
Status description:: error: syntax error or access rule violation - unsupported index or constraint. Only single property { $idxType } are supported.
386+
387+
=== 42N17
388+
389+
Status description:: error: syntax error or access rule violation - unsupported request. { $input } is not allowed on the system database.
390+
391+
=== 42N49
392+
393+
Status description:: error: syntax error or access rule violation - unsupported normal form. Unknown Normal Form: { $input }.
394+
395+
=== 42N75
396+
397+
Status description:: error: syntax error or access rule violation - invalid use of graph function. A call to the graph function { $fun } is only allowed as the top-level argument of a USE clause.
398+
399+
=== 42N83
400+
401+
Status description:: error: syntax error or access rule violation - impersonation disallowed while password change required. Cannot impersonate a user while password change required.
402+
403+
=== 42N84
404+
405+
Status description:: error: syntax error or access rule violation - TERMINATE TRANSACTION misses YIELD clause. WHERE clause without YIELD clause. Use 'TERMINATE TRANSACTION ... YIELD ... WHERE ...'.
406+
407+
=== 42N85
408+
409+
Status description:: error: syntax error or access rule violation - cannot specify both allowed and denied databases. Allowed and denied database options are mutually exclusive.
410+
411+
=== 42N88
412+
413+
Status description:: error: syntax error or access rule violation - cannot grant privilege. Permission cannot be granted for 'REMOVE IMMUTABLE PRIVILEGE'.
414+
415+
=== 42N89
416+
417+
Status description:: error: syntax error or access rule violation - invalid driver settings map. Failed evaluating the given driver settings. { $cause }
418+
419+
=== 42N90
420+
421+
Status description:: error: syntax error or access rule violation - cannot alter immutable composite database. Composite databases cannot be altered (database: { $db }).
422+
423+
=== 42I50
424+
425+
Status description:: error: syntax error or access rule violation - token name too long. Invalid input { $input }. A { $tokenType } name cannot be longer than { $maxTokenLength }.
426+
427+
=== 42NFD
428+
429+
Status description:: error: syntax error or access rule violation - credentials expired. Permission denied. The credentials you provided were valid, but must be changed before you can use this instance.
430+
431+
=== 42NFE
432+
433+
Status description:: error: syntax error or access rule violation - auth info expired. Authentication and/or authorization info expired.
434+
435+
=== 42NFF
436+
437+
Status description:: error: syntax error or access rule violation - permission/access denied. Access denied, see the security logs for details.

0 commit comments

Comments
 (0)