Loading TOC...
Messages and Codes Reference Guide (PDF)

Messages and Codes Reference Guide — Chapter 37

XDMP Messages

XDMP-ABORTED

Message Text

Transaction variable1 aborted: exception_stack

Cause

A distributed transaction was aborted because at least one participant failed to successfully commit the transaction. The logged message includes the underlying cause in the exception_stack.

Response

Refer to the secondary error messages to determine the root cause of the failure.

XDMP-ABSCAST

W3C XQuery Standard Equivalent: err:XPST0080

Message Text

Invalid cast to abstract type variable1

Cause

Your code attempted to cast a value to xs:Notation or xs:anyAtomicType.

Response

Correct your code.

XDMP-ACTION

Message Text

Invalid $cts:action variable1; should be "continue", "break", or "skip"

Cause

An invalid action was specified for $cts:action to a Search Built-in, such as cts:highlight or cts:walk. The only valid values for $cts:action are "continue", "break", and "skip".

Response

Correct your code and retry.

XDMP-ACTIONJS

Message Text

Invalid action variable1; should be "continue", "break", or "skip"

Cause

An invalid action was returned from the callback to a Search Built-in, such as cts.highlight or cts.walk. The only valid return values from the callback function are "continue", "break", and "skip".

Response

Correct your code and retry.

XDMP-ADDATTRIBUTE

Message Text

There can be only one root node.

XDMP-ADDBINARY

Message Text

There can be only one root node.

XDMP-ADDBOOLEAN

Message Text

There can be only one root node.

XDMP-ADDDOCUMENT

Message Text

A document node must be the first node.

XDMP-ADDELEMENT

Message Text

There can be only one root node.

XDMP-ADDNODE

Message Text

There can be only one root node.

XDMP-ADDNULL

Message Text

There can be only one root node.

XDMP-ADDNUMBER

Message Text

There can be only one root node.

XDMP-ADDTEXT

Message Text

There can be only one root node.

XDMP-AFTERTONODE

Message Text

This node builder is finished.

XDMP-ALLFORESTSRETIRED

Message Text

All forests in the database are retired

XDMP-APPREQ

Message Text

Application level authentication required

Cause

The operation attempted requires application level authentication. Application-level authentication bypasses all authentication and automatically logs all users in as a specified default user.

Response

Use the Admin Interface to specify a default user and set its permissions. Any users accessing the server automatically inherit the security attributes (roles, privileges, default permissions) of the default user. Application-level authentication is available on HTTP and WebDAV servers.

For more information, see the Understanding and Using Security Guide.

XDMP-ARG

Message Text

variable1 is invalid

Cause

XDMP-ARG is usually thrown by API functions receiving invalid parameter values. For example, passing xdmp:hex_to_integer an input string that doesn't represent a valid hexadecimal number; or, passing a sequence as an external variable parameter to xdmp:eval or xdmp:invoke.

Response

Correct your code.

XDMP-ARGTYPE

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

variable1 is not of type variable2

Cause

XDMP-ARGTYPE indicates a mismatch between the actual type (variable1) and expected type (variable2) of a function call argument. For example, passing an empty sequence when a node is expected. The message usually includes context information about the expression where the error occurred.

XDMP-ARGTYPE may also occur as the side-effect of another syntax or semantic error.

Response

Correct your code.

XDMP-ARRAY

Message Text

Invalid array element

Cause

Invalid array element.

Response

Check element and try again.

XDMP-ARRAYCYCLE

Message Text

A cycle was detected in the array entry

Cause

An array cannot be member of itself, either directly or indirectly.

Response

Do not add the array as a member of itself.

XDMP-AS

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Invalid coercion: variable1 as variable2

Cause

XDMP-AS indicates a mismatch between the actual type (variable1) and expected type (variable2) of an expression. For example, using an empty sequence when a node is expected. The message usually includes context information about the expression where the error occurred.

XDMP-AS may also occur as the side-effect of another syntax or semantic error.

Response

Correct your code.

XDMP-ATOMIZEFUNC

W3C XQuery Standard Equivalent: err:FOTY0013

Message Text

Functions cannot be atomized

Cause

An attempt was made to atomize a function. This might be via a call to the built-in fn:data function, or implicitly.

Response

You might be able to use functions like fn:function-name and xdmp:function-signature to describe the function as a string.

XDMP-ATTREXISTS

Message Text

Attribute with name variable1 already exists

Cause

An update operation such as xdmp:node-insert-child attempted to insert an attribute node for an attribute that already exists.

Response

Correct your code. For example, use xdmp:node-replace instead of xdmp:node-insert-child.

XDMP-ATTRIBNAME

Message Text

Cannot use variable1 as an attribute name

XDMP-ATTRNAME

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Cannot use variable1 as an attribute name

XDMP-ATTRPRFX

Message Text

No prefix has been defined for attribute namespace URI variable1

XDMP-ATTRSEQ

W3C XQuery Standard Equivalent: err:XQTY0024

W3C XSLT Standard Equivalent: err:XTDE0410

Message Text

Attribute node cannot follow non-attribute node in element content

Cause

Attribute constructors must appear before any elements or character data in an element constructor.

Response

Correct your code by moving the attribute constructor before any elements or character data in the parent element constructor.

XDMP-ATTRVALCHAR

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Invalid attribute value character variable1

Cause

The less-than character (<) may not be used as the literal value of an attribute. Less-than always indicates the beginning of a markup tag.

Response

Correct your code. For example, use a computed attribute constructor.

XDMP-ATTRXMLNS

Message Text

A namespace-qualified attribute name cannot be "xmlns".

XDMP-AUTHMISMATCH

Message Text

Authorization mismatch: variable1 specified, server wants variable2

Cause

The client application used an authentication scheme that did not match what MarkLogic Server expected. For example, the client used basic when the server expected digest.

This error sometimes occurs when the browser caches credentials across a change to the server's authentication scheme.

Response

Change the application server's authentication scheme in the Admin Inerface, if appropriate. Or, pass the desired authentication scheme as an explicit option:

<options xmlns="xdmp:http">
  <authentication method="digest">
    <username>myname</username>
    <password>mypassword</password>
  </authentication>
</options> 

For more information, see the Understanding and Using Security Guide.

XDMP-AUXFORESTNOTOPEN

Message Text

$m with identifier variable1

XDMP-AWSSVCREG

Message Text

Cannot determine AWS service and region from domain 'variable1'

XDMP-BACKDATADIR

Message Text

Cannot backup to Data directory/subdirectories: variable1

Cause

The configured backup directory is the same as, or is a sub-directory of, MarkLogic's data directory.

Your backup directory may not be inside the MarkLogic Server installation or data area. For example, on Unix, you should not save your backups under /var/opt/MarkLogic or /opt/MarkLogic.

Response

Configure your backups to use a directory that is not inside the MarkLogic Server installation or data directories.

XDMP-BACKDIRCORRUPT

Message Text

Backup data directory is corrupt: variable1

Cause

The backup data directory is corrupted. The error may be caused by file system errors, such has disk failures. Backups cannot proceed until the problem is corrected.

Response

Review the surrounding MarkLogic Server and system error log messages to identify the underlying cause. Contact MarkLogic Technical Support for assistance.

XDMP-BACKDIRINUSE

Message Text

Backup data directory currently has a backup job in progress: variable1

Cause

A restore was attempted while another process was already running a backup. Or, another process has the backup directory locked.

Response

If there is another backup running, wait for it to complete or kill it.

XDMP-BACKDIRNOTFOUND

Message Text

Backup data directory does not exist: variable1 on host variable2

Cause

The configured backup directory does not exist or cannot be found.

Response

Check the existence and permissions of the backup directory. Check your backup configuration for errors in the backup directory name.

XDMP-BACKDIRSPACE

Message Text

Not enough disk space for backup: variable1

Cause

The disk containing the backup directory has run out of disk space.

Response

Make more space on your backup disk, or move your backups to a disk with sufficient space.

XDMP-BACKINSTALLDIR

Message Text

Cannot backup to installation directory/subdirectories: variable1

Cause

Your backup directory is inside the MarkLogic Server installation or data directory tree. For example, on Unix, the backup directory is configured as a sub-directory of /opt/MarkLogic or /var/opt/MarkLogic.

Response

Configure your backups to use a directory that is not inside the MarkLogic Server installation or data directories.

XDMP-BACKPUBLICDIR

Message Text

Cannot backup to a forest's public data directory/subdirectories: variable1

Cause

The configured backup directory is within a forest's data directory. Your backup directory should not be inside the MarkLogic Server installation or data directory tree. For example, on Unix, the backup directory should not be configured as a sub-directory of /opt/MarkLogic or /var/opt/MarkLogic.

Response

Move your backups to a location outside of any installation or public forest data directories.

XDMP-BACKUP

Message Text

Error in backup: variable1

XDMP-BACKUPCATALOGMISSING

Message Text

Restore from incremental backup failed. Documents missing from the catalog.

XDMP-BACKUPDATADIR

Message Text

Backup pathname conflicts with data directory: variable1

Cause

The configured backup directory is the same as, or is a sub-directory of, MarkLogic's data directory.

Your backup directory may not be inside the MarkLogic Server installation or data area. For example, on Unix, you should not save your backups under /var/opt/MarkLogic or /opt/MarkLogic.

Response

Configure your backups to use a directory that is not inside the MarkLogic Server installation or data directories.

XDMP-BACKUPDIR

Message Text

Backup pathname is not a directory: variable1

Cause

You attempted to restore a forest from a pathname that does not refer to a directory.

Response

Confirm the existence of the source directory. Check for broken symbolic links. Correct any typographical errors in the pathname.

XDMP-BACKUPEMPTY

Message Text

No forests specified for backup or restore.

Cause

You attempted to start a database backup or restore without including any forests. A backup or restore must include at least one forest.

Response

Change your backup configuration to include at least one forest.

XDMP-BACKUPINMEMORY

Message Text

Cannot backup in-memory stand: variable1 (variable2 <= variable3 < variable4)

XDMP-BACKUPINSTALLDIR

Message Text

Backup pathname conflicts with install directory: variable1

Cause

The configured backup directory is the same as, or is a sub-directory of, MarkLogic's installation directory.

Your backup directory may not be inside the MarkLogic Server installation or data area. For example, on Unix, you should not save your backups under /var/opt/MarkLogic or /opt/MarkLogic.

Response

Configure your backups to use a directory that is not inside the MarkLogic Server installation or data directories.

XDMP-BACKUPNOTFOUND

Message Text

No backup found in backup pathname: variable1

XDMP-BACKUPSTAMP

Message Text

Backup timestamp too old for forest: variable1

XDMP-BAD

Message Text

Bad variable1

Cause

Many different kinds of error can log this message. Refer to the error text for details. Often, XDMP-BAD indicates an unexpected internal error condition.

Response

Refer to the full text of the error for additional information. For more assistance, contact MarkLogic Technical Support.

XDMP-BADANNNS

W3C XQuery Standard Equivalent: err:XQST0045

Message Text

Functions annotations may not use a reserved namespace

Cause

A function annotation uses a reserved namespace.

Response

Choose a different namespace.

XDMP-BADAPIVERSION

Message Text

The plugin is compiled for another version of the MarkLogic plugin API. expected: variable1, found: variable2, host: variable3

Cause

The plugin is compiled for another version of the MarkLogic plugin API.

Response

Recompile the plugin, or otherwise obtain a compatible plugin.

XDMP-BADARC

Message Text

Arc must span more than 0 degrees and less than 180 degrees, and cannot cross a pole.

Cause

An invalid pair of points was specified to geo:arc-intersection. Each arc passed to geo:arc-intersection must not cover more than 180 degrees, and must not cross a pole.

Response

Correct your code. For more information, see Geospatial Search Applications in the Search Developer's Guide.

XDMP-BADBOX

Message Text

Invalid box: variable1 > variable2

Cause

Invalid box coordinates were passed to a geospatial query operation such as a box query. For example, the south boundary of the box is above the north boundary.

Response

Correct your code or data.

XDMP-BADBOXSPEC

Message Text

Bad box specification

Cause

An attempt is made to construct a cts:box from a malformed KML Envelope or GML LongLatBox. In particular, the child elements that should be simple values have children of their own.

Response

Fix the GML or KML elements.

XDMP-BADBRK

Message Text

Bad word break rules: variable1

Cause

The word break rules are invalid for some reason.

Response

Check your word break rules.

XDMP-BADCHAR

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Unexpected character found variable1

Cause

The XQuery lexer found a character where the XQuery language does not permit it to be.

Response

Fix your query to use correct grammar.

XDMP-BADCIRCLE

Message Text

Invalid circle

Cause

The radius of the cts:circle is too large. The circle cannot cover the entire earth.

Response

Correct your code.

XDMP-BADCLASSIFIER

Message Text

Invalid classifier specification element

Cause

An invalid classifier was passed to cts:classify. For example, the element supplied as the classifier parameter is not of type cts:classifier. The classifier is usually created by calling cts:train.

Response

Correct your code.

XDMP-BADCOLLATION

Message Text

Error in collation variable1

Cause

An invalid or non-existent collation URI was specified.

Response

Correct the collation URI. For more information about collations, see "Encodings and Collations" in the Search Developer's Guide.

XDMP-BADDEPTHALL

Message Text

Invalid depth (should be "0", "1", or "infinity")

XDMP-BADDEPTHSOME

Message Text

Invalid depth (should be "0" or "infinity")

Cause

An invalid value was supplied for depth to a locking function such as xdmp:lock-acquire. The only values allowed are "0" and "infinity".

Response

Correct your code. For more information, see the Overview of Locks in the Application Developer's Guide.

XDMP-BADDIR

Message Text

Invalid directory URI

Cause

In invalid directory name was supplied to xdmp:directory-create. For example, an empty string or badly formed URI was passed.

Response

Correct your code.

XDMP-BADDOCID

Message Text

Invalid classifier specification element: document id variable1 not found

Cause

A document used in the training set for a supports type classifier is not a valid document.

A supports type classifier contains a list of document elements which identify the specific training nodes, using an internal key. The internal key is only valid across queries for nodes in the database. If training and classification are done in different queries when the training documents are not in the database, XDMP-BADDOCID is thrown.

Response

Possible solutions include:

Place your training set in the database.Perform training and classification in the same query.Use a weights classifier. Weights classifiers do not have this restriction.

XDMP-BADFORATQNAME

W3C XQuery Standard Equivalent: err:XQST0089

Message Text

An "at" variable may not have the same name as the bound variable

Cause

The same variable name is used as both the for variable and its associated positional variable in the at clause. For example:

for $bad-choice at $bad-choice...
      

Response

Correct your code by using different variables in the for and its at clause.

XDMP-BADFORESTUPDATESTATE

Message Text

All forests must not be in read-only or flash-backup mode when backing up with journal archiving

Cause

This occurs when trying to do a full database backup with journal archiving enabled and at least one forest is in read-only or flash-backup mode.

Response

Make sure all forests have their update status set to all or delete-only when taking a full database backup with journal archiving.

XDMP-BADFORESTUPDATESTATEFLASHBACKUP

Message Text

All forests must be in flash-backup mode when running xdmp:start-journal-archiving

Cause

This occurs when running xdmp:start-journal-archiving and at least one forest is not in flash-backup update state.

Response

Put all forests in flash-backup update state when running xdmp:start-journal-archiving.

XDMP-BADGEOMETRY

Message Text

Invalid geometry : variable1

Cause

The provided geometry violates one or more of the required constraints.

Response

Correct your code. For more information, see Geospatial Search Applications in the Search Developer's Guide.

XDMP-BADGEOMETRYTYPE

Message Text

Invalid geometry type

Cause

The geometry has an unrecognized type.

XDMP-BADGROUPSEP

Message Text

Group separator must be a single character/codepoint.

Cause

The group separator passed to xdmp:format-number contains more than one character or codepoint.

Response

Correct your code to use a single character/codepoint group separator.

XDMP-BADHEX

Message Text

Bad hex string: variable1 is invalid hex string

Cause

A string that was not a valid hex-encoded binary string was passed as a parameter where one was expected.

Response

Correct your code.

XDMP-BADJNLNAME

Message Text

Bad journal name: variable1

Cause

This error means a journal file with an unexpected filename was encountered.

Response

Contact MarkLogic support.

XDMP-BADJOURNALARCHIVE

Message Text

The journal archive is invalid: variable1

Cause

Journal archive file read a bad header frame when resuming journal archiving. This will happen if header stored checksum does not match with its calculated checksum.

Response

Set journaling option to "fast" or "strict" for the database this forest is attached to

XDMP-BADJSONLABELS

Message Text

Invalid classification labels element

Cause

Labels were badly formed.

Response

Correct your code. For more information, see Training the Classifier in the Application Developer's Guide.

XDMP-BADLABELS

Message Text

Invalid classification labels element

Cause

An element that is not a cts:label was encountered in the label set passed to cts:train, or a child node that is not a cts:class was encountered on a cts:label.

Response

Correct your code. For more information, see Training the Classifier in the Application Developer's Guide.

XDMP-BADLABELVALUE

Message Text

Invalid classification label value: must be 1 or -1

Cause

An invalid value was given on the val attribute of a cts:label element supplied to cts:train. If present, the val must be 1 or -1.

Response

Correct your code. For more information, see Training the Classifier in the Application Developer's Guide.

XDMP-BADLANGKEY

Message Text

Bad tokenizer key language variable1

XDMP-BADLANGOVER

Message Text

Cannot override stemmer/tokenizer for language variable1

XDMP-BADLEXER

Message Text

The lexer could not be initialized: variable1 lexer invalid

Cause

The lexer was misconfigured or cannot be used for that language.

Response

Check your language configuration.

XDMP-BADLINESTRING

Message Text

Invalid linestring

Cause

Fewer than two vertices were given when constructing a linestring with cts:linestring.

Response

Correct your code.

XDMP-BADLOCKTOKEN

Message Text

Incorrect Lock Token

Cause

The file locking token supplied to the app server when acquiring a lock does not match the locking token supplied when releasing the lock. Your WebDAV client may not be working properly.

The WebDAV protocol supports locking of files. When locking a file, a WebDAV client can supply a lock token. When the client is ready to release the lock, the same lock token is supplied. XDMP-BADLOCKTOKEN is thrown when these locking tokens do not match.

Response

Correct the mismatch. If you need assistance determining the cause of the mismatch, contact MarkLogic Technical Support.

XDMP-BADLOGLEVEL

Message Text

The second argument level should be one of the following: emergency, alert, critical, error, warning, notice, info, config, debug, fine, finer, or finest. The default level is "info".

Cause

The second argument of xdmp:log($msg,$level) level is not specified correctly.

Response

Correct your code.

XDMP-BADMAP

Message Text

Invalid option: 'map' cannot be used with 'array' option

XDMP-BADMTYPE

Message Text

Backup data directory was created from a different machine type: variable1 (variable2)

Cause

You attempted to restore from a backup created for a different platform. Backup files are platform-specific. You may not restore a backup to a machine type different from the host where the backup was created.

Response

Restore to a host whose platform matches that of the host that created the backup.

XDMP-BADNULLABLE

Message Text

Illegal nullable in tuple selector: first tuple selector cannot be nullable: variable1

Cause

The first lexicon selected in cts:value-tuples was given with the option "nullable". This is not allowed.

Response

Remove the "nullable" option from the first lexicon, or reorder the lexicons so that a nullable on is not the first.

XDMP-BADOCCURS

Message Text

Invalid occurrence indicator: variable1

Cause

The min-occurs option value is greater than the max-occurs option value in your query. These options to the cts:query constructors constrain searches to return results only if the search terms appear a minimum or a maximum number of times.

Response

Correct your query constructor options.

XDMP-BADORDCHAR

Message Text

Ordchar argument must be either "yes" or an ordinal character starting followed by a dash "-".

Cause

The ordinal number parameter to xdmp:format-number is not one of:

An empty sequenceThe string "yes"An ordinal string, beginning with a dash ("-").

Response

Correct your code.

XDMP-BADPINAME

Message Text

Invalid processing instruction name "variable1" at variable2 line variable3

Cause

An unrecognized Processing Instruction was encountered while parsing XML data, on line variable3 of the data with URI variable2. The following is an example of an XML processing instruction:

<?xml version="1.0" encoding="UTF-8" ?>

Response

Correct the processing instruction and try the operation again.

XDMP-BADPLUGINVERSION

Message Text

The plugin does not match the expected version number. expected: variable1, found: variable2, host: variable3

Cause

The plugins loaded on two hosts report different version numbers.

Response

Redeploy your native plugins directory.

XDMP-BADPOINTSPEC

Message Text

Bad point specification

Cause

The set of points describing a region or arc in one of the geospatial builtins is invalid. For example, an empty sequence was passed instead of a valid point.

Response

Correct your code.

XDMP-BADPOLYGON

Message Text

Invalid polygon

Cause

Fewer than three vertices were given when constructing a polygon with cts:polygon.

Response

Correct your code.

XDMP-BADPROP

Message Text

Malformed property

Cause

Document properties are malformed.

Response

If the error occurs when you are creating properties, correct your code. If the error occurs during operations that use previously supplied properties, then the document properties may be corrupted; contact MarkLogic Technical Support for assistance.

XDMP-BADREFERENCE

Message Text

The cts reference cannot be used in this context: variable1

Cause

A cts reference was passed to a function that cannot use it.

Response

Use the correct cts reference constructor.

XDMP-BADREP

W3C XQuery Standard Equivalent: err:FORX0004

Message Text

Invalid replacement string: variable1

Cause

An invalid replacement string was supplied to fn:replace. The error is usually one of these cases:

The replacement string contains a "$" character that is not immediately followed by a digit 0-9 and not immediately preceded by a "\".The replacement string contains a "\" character that is not part of a "\\" pair and not immediately followed by a "$" character.

Response

Correct your code.

XDMP-BADRESTOREPATH

Message Text

Not all hosts contained the same restore path

XDMP-BADRESTORETOTIME

Message Text

restore-to-time was less than the earliest full backup time in the folder

XDMP-BADRETURN

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Only use 'return' at the end of a FLWOR expression or typeswitch clause

XDMP-BADSCHEMA

W3C XQuery Standard Equivalent: err:XQST0012

W3C XSLT Standard Equivalent: err:XTSE0220

Message Text

Invalid schema "variable1" at "variable2" exception_stack

Cause

The schema variable1 at schema URI variable2, used in an XQuery or XSLT schema import, does not meet the validity requirements of XML Schema Part I, as defined by W3C. In a valid schema, all definitions are valid, complete, and unique.

Response

Review and correct your schema. Check for duplicate or erroneous definitions.

XDMP-BADSCOPE

Message Text

Invalid scope (should be exclusive or shared)

Cause

The scope parameter to xdmp:lock-acquire is not one of "shared" or "exclusive".

Response

Correct your code.

XDMP-BADSECDBVER

Message Text

Bad security database version

XDMP-BADSEMICOLON

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Semicolons are not necessary as a statement separator in XQuery.

Cause

A semicolon was found where the XQuery grammar does not allow one. You might be trying to terminate a statement with a semicolon, like Java and C++ require - but this is not valid in XQuery.

Response

Correct your XQuery. You might find that using a comma (",") is what you want rather than a semicolon.

XDMP-BADSEMISEP

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Semicolons are not necessary as a statement separator in XQuery. Did you mean to use ','?

Cause

A semicolon was found where the XQuery grammar does not allow one. You might be trying to terminate a statement with a semicolon, like Java and C++ require - but this is not valid in XQuery.

Response

Correct your XQuery. You might find that using a comma (",") is what you want rather than a semicolon.

XDMP-BADSTARTUPTOKEN

Message Text

Bad startup token for variable1, variable2 before last journal start variable3

XDMP-BADSTEMMER

Message Text

The stemmer could not be initialized: variable1 stemmer invalid

Cause

The stemmer was misconfigured or cannot be used for that language.

Response

Check your language configuration.

XDMP-BADTOLERANCE

Message Text

Invalid tolerance: variable1

Cause

The provided tolerance is invalid. Tolerance must be a positive real number.

Response

Correct your code.

XDMP-BADWKB

Message Text

Cannot parse binary data as WKB object: WKB 'variable1' is not parsable

Cause

geo:parse-wkb is called with a binary node that cannot be parsed as a WKB object. The data is either malformed or an unsupported WKB type.

Response

Make sure that the data is valid and contains only supported WKB types.

XDMP-BADWKT

Message Text

Cannot parse string as WKT object: WKT 'variable1' is not parsable

Cause

geo:parse-wkt is called with a string that cannot be parsed as a WKT string. The string is either malformed or an unsupported WKT type.

Response

Make sure that the WKT string is valid and contains only supported WKT types.

XDMP-BINARYREAD-EMPTY

Message Text

Binary read returned empty

Cause

Either the binary node is empty or you used incorrect offset/count.

Response

Check the binary node and your code.

XDMP-BINARYSIZE

Message Text

Wrong binary size variable1

Cause

Found a large binary file with wrong size during replication. The server will re-replicate the file.

Response

Refer to the full text of the error for additional information. For more assistance, contact MarkLogic Technical Support.

XDMP-BOUNDS

Message Text

Bounds must be in strictly ascending order

Cause

The latitude and longitude bounds parameters to cts:element-geospatial-boxes or cts:element-child-geospatial-boxes are sequences of numbers. This error occurs if the values in either bounds sequence are not listed in ascending order.

Response

Correct your latitude or longitude bounds values to be in ascending order.

XDMP-BULKNOMERGE

Message Text

Unable to bulk synchronize forests when merge is disabled

Cause

If merges are disabled, bulk replication will not run since it could cause an excessive number of stands.

Response

Enable merges on the database.

XDMP-BULKNOTOPEN

Message Text

Unable to bulk synchronize forest when forest is not open

Cause

The forest must be open to allow bulk synchronization to occur.

Response

Open the forest and try again.

XDMP-CANCELED

Message Text

Canceled variable1 variable2

Cause

This message usually indicates that an operation such as a merge, backup or query was explicitly canceled. The message includes information about what operation was canceled. Cancellation may occur through the Admin Interface or by calling an explicit cancellation function, such as xdmp:request-cancel.

XDMP-CANNOTGEOOP

Message Text

Geospatial operation not supported on that type of object

Cause

An attempt is made to perform some geospatial operation on a geospatial object that does not support that operation. For example, it is not possible to serialize a cts:box in WKT format, as WKT does not support that type.

Response

Change the application to avoid the unsupported operation.

XDMP-CANTDECODEFRAGSETKIND

Message Text

Cannot decode fragset kind variable1

XDMP-CANTDECODELOCATORORDERERKIND

Message Text

Cannot decode locator orderer kind variable1

XDMP-CANTDECODEQUERYKIND

Message Text

Cannot decode query kind variable1

XDMP-CANTDECODESCALARTYPE

Message Text

Cannot decode scalar type variable1

XDMP-CAST

W3C XQuery Standard Equivalent: err:FORG0001

Message Text

Invalid cast: variable1 cast as variable2

Cause

An expression or declaration attempted to cast a value to an incompatible type. For example, passing a value to a constructor of a type illegal for the data type being constructed.

Response

Correct your code.

XDMP-CELLCYCLE

Message Text

A cycle was detected in the variable (cell) update

XDMP-CHARREF

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Invalid character reference variable1

Cause

variable1 is an invalid character reference. A character references identifies a character by its Unicode codepoint in either decimal or hexadecimal. XDMP-CHARREF may occur if the codepoint value is outside the valid range of values for Unicode or the reference is otherwise malformed.

Response

Correct your code.

XDMP-CHARSEARCH

Message Text

Character searches not enabled

XDMP-CHILDDUPNAME

Message Text

Object nodes cannot have two children with the same name

XDMP-CHILDLINK

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Invalid child link node variable1

XDMP-CHILDNODEKIND

W3C XSLT Standard Equivalent: err:XTDE0420

Message Text

variable1 nodes cannot have variable2 node children

Cause

You attempted to insert a node of type variable1 as a child of a node of type variable2 where such insertion is not allowed. This may be occurring through an XQuery builtin, such as xdmp:insert-child, or via an XSLT transformation. One example of such invalid insertion is attempting to add an attribute or namespace node as an immediate child of a document node.

Response

Correct your code.

XDMP-CHILDSEQ

Message Text

Object nodes cannot have sequence children

XDMP-CHILDUNNAMED

Message Text

Object nodes cannot have unnamed children

XDMP-CIRCVAR

W3C XQuery Standard Equivalent: err:XQST0054

W3C XSLT Standard Equivalent: err:XTDE0640

Message Text

Circularly defined variable or parameter variable1

Cause

The variable or parameter variable1 depends upon itself.

For example, this error will occur if the initialization of a variable includes a call to function which references the variable.

Response

Correct your code.

XDMP-CLARKNAME

Message Text

Invalid Clarked qname "variable1"

XDMP-CLOCKSKEW

Message Text

Detected clock skew: host variable1 skewed by variable2 seconds

Cause

Clock skew is typically due to not having NTP properly functioning on all hosts in the cluster.

Response

Review your NTP configuration/settings

XDMP-CODEPOINT

W3C XQuery Standard Equivalent: err:FOCH0001

Message Text

Codepoint not legal

Cause

A character was found that is not a valid XML character while decoding data with fn:codepoints-to-string or xdmp:url-decode.

Response

Correct your code.

XDMP-COLLATION

W3C XQuery Standard Equivalent: err:FOCH0002

Message Text

Unsupported collation: Collation hash variable1 not recognized

Cause

Your database configuration probably includes an invalid collation. For example, the following collation includes contradictory requirements because "S1" specifies case insensitive, but "CU" specifies upper case first:

http://marklogic.com/collation/en/S1/CU/AS/T0020
      

Response

The exact steps required to correct the problem depend upon the circumstances under which the error is encountered. If the error occurs during startup or as part of an upgrade, contact MarkLogic Technical Support for assistance.

XDMP-COLLATIONURI

W3C XQuery Standard Equivalent: err:XQST0038

Message Text

Collation URI variable1 is not valid

Cause

Your XQuery prolog contains more than one default collation declaration, or the default collation declaration specifies an unknown collation.

Response

Correct your code.

XDMP-COLLDIFF

Message Text

String objects have different collations

Cause

The String objects have different collations, and cannot be compaed.

Response

Consider constructing new String objects, specifying the collation required for comparison.

XDMP-COLLNOBINDING

W3C XQuery Standard Equivalent: err:FODC0004

Message Text

Available collections provides no mapping for URI

XDMP-COLLXCNNOTFOUND

Message Text

Collection lexicon not enabled

XDMP-COMMENTHYPHEN

W3C XQuery Standard Equivalent: err:XQDY0072

Message Text

XML comments cannot end with a hyphen

Cause

The text in a comment node ends with a hyphen. For example:

comment { "ends with a hyphen -" }

Response

Remove the trailing hyphen or add additional text after the hyphen.

XDMP-COMMENTHYPHENS

W3C XQuery Standard Equivalent: err:XQDY0072

Message Text

XML comments cannot contain two adjacent hyphens

Cause

The text in a comment node contains two adjacent hypens. For example:

comment { "a -- b" }

Response

Correct your code. For example, remove one of the hyphens.

XDMP-COMMITLIB

Message Text

Commit option cannot be used in library modules

Cause

Commit option was specified in an XQuery library module.

Response

Move the commit option to the main module.

XDMP-COMMITTXNMODE

Message Text

Commit option cannot be specified with transaction mode option

Cause

Commit option was specified in combination with transaction mode option.

Response

Remove the transaction mode option.

XDMP-COMPARE

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Items not comparable: variable1 variable2 variable3

XDMP-COMPLEX

Message Text

Node has complex content

Cause

An attempt was made to atomize an XML element node that cannot be atomized. The element node has complex content that cannot be converted to an atomic value. Some code is attempting to convert the node to an atomic value.

Response

The code should not explicitly atomize the node by calling fn:data on it. The code should not implicitly atomize the node by passing it as a parameter to a function expecting an atomic value.

XDMP-COMPTREECACHEFULL

Message Text

Compressed tree cache full on host variable1

XDMP-COMPUTE

W3C XQuery Standard Equivalent: err:FORG0006

Message Text

Cannot compute variable2((variable1, variable3))

XDMP-CONFLICTINGUPDATES

Message Text

Conflicting updates variable1 and variable2

Cause

The application attempted to perform multiple updates to the same document within the same transaction.

A single statement may not perform more than one update to the same document. For example, you cannot update a node and add a child element to that node in the same statement.

Response

Revise your application code to perform the conflicting operations in two separate statements. For example, use the semicolon transaction delimiter, or execute the second update inside an xdmp:eval with the isolation option set to different-transaction.

For more information, see Understanding Transactions in MarkLogic Server in the Application Developer's Guide.

XDMP-CONFLICTOPT

Message Text

Isolation option value conflicts with transaction mode option

Cause

Isolation option value conflicts with transaction mode option

Response

Remove the transaction mode option.

XDMP-CONSTRNOTFOUND

Message Text

No constraint for variable1

Cause

Your search string included a constraint name that was not found.

Response

Ensure you provide a mapping for the constraint.

XDMP-CONTEXT

W3C XQuery Standard Equivalent: err:XPDY0002

Message Text

Expression depends on the context where none is defined

XDMP-CONTEXTITEMNOTNODE

W3C XQuery Standard Equivalent: err:XPDY0002

Message Text

Context item is not a node

Cause

You tried to operate on the context item as a node when it is an atomic type.

Response

Correct your query.

XDMP-CONVLINK

Message Text

Failed to create soft links for conversion: variable1 'variable2': variable3

XDMP-COPYONVALIDATEOPTVAL

Message Text

Invalid xdmp:copy-on-validate option value, must be "true" or "false"

XDMP-COPYSAMEDIR

Message Text

Forest cannot be copied into the same location as the current data directory: variable1, variable2

XDMP-CORRUPT

Message Text

read variable1:File corrupt, variable2

Cause

File corruption was detected reading a database file.

Response

Check the operating system error log for file system or storage hardware problems. See the MarkLogic technical note on troubleshooting file corruption issues.

XDMP-CREDBADURL

Message Text

Credential variable1 not valid for URL variable2

XDMP-CREDDECRYPT

Message Text

Unable to decrypt credential variable1 variable2

Cause

There is a key encryption key missmatch for this credential

Response

Make sure the text is actually encrypted. If this credential was originally encrypted on a different cluster, importing encryption keys from that cluster may allow decryption. Alternatively, you can update the credential's sensitive information.

XDMP-CREDNOSIGN

Message Text

Credential not valid for signing: variable1

XDMP-CREDNOTENCRYPTED

Message Text

Credential is not encrypted

XDMP-CREDWITHAUTH

Message Text

Credential in combination with other authentication

Cause

A credential ID was specified along with some other authentication information (user, password, client certificate).

Response

Use either a credential, or authentication, but not both.

XDMP-CTXTDEP

W3C XQuery Standard Equivalent: err:XPST0112

Message Text

Function is context dependent: variable1

Cause

You cannot dynamically call a function passed as a value if it depends on aspects of the context in order to execute. Only built-in functions can depend on the context in this way.

Response

You might be able to use another version of the same function where you can explicitly provide the information otherwise used from the context. Or you might want to wrap your call to the function in an explicit inline function such as function($a,$b) { starts-with($a,$b) }.

XDMP-DATABASEDISABLED

Message Text

Database variable1 is disabled

XDMP-DATAGTLIM

Message Text

data>limit

Cause

This is an internal error, indicating corruption in the memory manager.

Response

Contact MarkLogic Technical Support.

XDMP-DATE

Message Text

Invalid Date variable1

Cause

The requested date is before year -9999 or after 9999

Response

Dates outside the range of year -9999 to 9999 are not supported

XDMP-DATETIME

Message Text

Invalid dateTime variable1

Cause

The value is not a valid dateTime

Response

Review the valid formats for dateTime values.

XDMP-DATETIME2TZ

W3C XQuery Standard Equivalent: err:FORG0008

Message Text

Both arguments to xs:dateTime have timezones

Cause

Evaluated fn:dateTime() where both arguments contain an explicit timezone and the timezones are not equivalent.

Response

When using fn:dateTime ensure that if timezones are specified, they are equivalent in both the date and time arguments, or only present in at most one of the date and time arguments.

XDMP-DATETIMEOVERFLOW

W3C XQuery Standard Equivalent: err:FODT0001

Message Text

Overflow in date/time arithmetic

Cause

The date time resulting from a calculation exceeds the range of year -9999 to year 9999

Response

The date time resulting from a calculation exceeds the range of year -9999 to year 9999

XDMP-DATETIMEPARSINGFAILED

Message Text

Failed to parse the dateTime string with the given pattern.

Cause

The dateTime format string was unable to be parsed.

Response

Review the format picture and dateTime string for validity.

XDMP-DBDUPURI

Message Text

URI variable1 found in forests variable2 and variable3 with ts=variable4

Cause

The same URI occurs in multiple forests. This may occur if some forests are unavailable during document insert.

Response

Remove the unwanted duplicate document.

XDMP-DBNOTQUERYPOLICY

Message Text

Assignment policy is not a query policy, on database: variable1

Cause

The assignment policy on the database is not a query policy.

Response

Check your database configuration and make sure it uses the query policy before calling this function.

XDMP-DBTIMESTAMP

Message Text

Query timestamp not yet known for database variable1

XDMP-DEADLOCK

Message Text

Deadlock detected locking variable1

Cause

A deadlock was detected. When this message occurs at the Debug message level, the deadlock was successfully resolved. When the message occurs at the Notice level, the deadlock was unresolvable.

Deadlocks occur when two transactions are each waiting for the other to release a lock and neither can continue until the other releases the lock. Deadlocks are a normal part of database operations.

MarkLogic Server is designed to automatically detect and resolve deadlocks. When a deadlock is detected, one of the deadlocked transactions is retried, allowing the other to acquire the lock and continue. When this expected behavior occurs, XDMP-DEADLOCK is written to the log file as a Debug message, to indicate that a deadlock occurred and was resolved.

If the deadlock cannot be resolved by repeated retries, the XDMP-DEADLOCK message is written to the log file as a Notice message.

Response

If XDMP-DEADLOCK appears as an infrequent Debug message, no action is required. Deadlocks are a normal part of database operations, and the system successfully resolved the deadlock.

If XDMP-DEADLOCK appears frequently as a Debug message, you may have a performance issue. Revise your query or content structure to reduce the frequency of the deadlock.

If XDMP-DEADLOCK appears as a Notice message, the system was unable to resolve the deadlock. Examine the error message for details about the contentious resource. Revise your query or content structure to avoid the deadlock.

XDMP-DEBLOB

Message Text

Cannot construct from blob: variable1

XDMP-DECOMPOUNDEDSEARCH

Message Text

Decompounded word searches not enabled

XDMP-DECOMPOUNDNOSTEM

Message Text

Decompounded word searches cannot be run unstemmed

XDMP-DECOVRFLW

W3C XQuery Standard Equivalent: err:FOAR0002

Message Text

Decimal overflow

XDMP-DECRYPTFAILED

Message Text

Failed to decrypt, variable1

Cause

There is a key encryption key missmatch

Response

Make sure the text is actually encrypted. If this text was originally encrypted on a different cluster, importing encryption keys from that cluster may allow decryption.

XDMP-DEEPEQFUNC

W3C XQuery Standard Equivalent: err:FOTY0015

Message Text

Functions cannot be compared using deep-equal()

XDMP-DEFAULT-COLLATION

Message Text

default-collation option not allowed in this function

XDMP-DEFAULT-COORDINATE-SYSTEM

Message Text

default-coordinate-system option not allowed in this function

XDMP-DEFAULTCALENDARNOTFOUND

Message Text

Failed to find default calendar. Make sure that calendars.xml is not accidentally modified in your configuration.

XDMP-DEFAULTCOUNTRYNOTFOUND

Message Text

Failed to find default country. Make sure that countries.xml is not accidentally modified in your configuration.

XDMP-DEFAULTNSDEFND

Message Text

Default namespace is defined

XDMP-DEFAULTXQUERYVERSION

Message Text

Default XQuery version is not recognized: "variable1" (must be "0.9-ml", "1.0", "1.0-ml" or "app-server")

XDMP-DELCONSTNODES

Message Text

Cannot delete constructed nodes

XDMP-DELETEONLY

Message Text

Forest variable1 can only perform deletes

Cause

An update or insertion operation was attempted on a delete-only forest. Only read and delete operations are available on documents in a delete-only forest.

Response

Move the target document to a forest which permits update operations, or test whether or not the forest allows updates before attempting the update operation. To test the forest status, use the admin:forest-get-updates-allowed function.

XDMP-DELEXTNODES

Message Text

Cannot delete external nodes

XDMP-DEPENDENCY

Message Text

Action on directory failed due to error in processing one of its children: variable2

XDMP-DESTSAMEASSRC

Message Text

Source and Destination are the same

XDMP-DFBUFREAD

Message Text

Data Frame buffered read error: variable1

XDMP-DFBUFWRITE

Message Text

Data Frame buffered write error: variable1

XDMP-DIFFRIDXTYPS

Message Text

variable1 and variable2 have different range index types

Cause

A user can specify multiple values in a range query. This error occurs if all the specified values are not of the same data-type.

Response

All values supplied to a range query must be of the same data-type.

XDMP-DIFFTIMESTAMP

Message Text

Cannot process timestamped requests with same-statement isolation

XDMP-DIRCREATE

Message Text

Directories cannot be created by adding property only

XDMP-DIRELEMENT

Message Text

Directory property cannot be deleted or replaced

XDMP-DIREXISTS

Message Text

Directory already exists

Cause

xdmp:directory-create called with the name of a directory that already exists; or, the directory target of a WebDAV MKCOL directive already exists.

Response

Correct the code or remove the pre-existing directory.

XDMP-DIRNOACCESS

Message Text

Cannot access directory: variable1

XDMP-DIRNOTEMPTY

Message Text

Directory cannot be deleted because it is not empty

XDMP-DIRURI

Message Text

Directory URI path must end with '/'

Cause

The path part of the directory URI provided to xdmp:directory-create or xdmp:directory-delete does not end in with a '/'. For example:

xdmp:directory-create("the_dir")

Response

Correct the code by adding a '/' to the end of the path part of the directory URI. For example:

xdmp:directory-create("the_dir/")

XDMP-DISABLED

Message Text

Service disabled on variable1: variable2

Cause

This message usually indicates the server is shutting down. For example, when you use the Admin Interface to change a configuration parameter that requires a restart, an automatic shtudown and restart occurs. During this shutdown, XDMP-DISABLED may be logged.

Response

If this message appears during an expected shutdown, no action is required. The system is performing as expected.

If this message appears in a context in which shutdown is unexpected, examine the logs for other errors to determine the root cause of the shutdown.

XDMP-DISCTOKEN

Message Text

Discarding token variable1

XDMP-DISFOREIGNREQ

Message Text

Disallowed foreign request: variable1

XDMP-DIVBYZERO

W3C XQuery Standard Equivalent: err:FOAR0001

Message Text

Division by zero

Cause

Denominator was found to be zero.

Response

Check that denominator is not zero before dividing.

XDMP-DOCATTRVALCHAR

Message Text

Invalid attribute value character variable1 or missing close quote at variable2 line variable3

XDMP-DOCBADCHAR

Message Text

Unexpected character found: variable1 at variable2:variable3:variable4

Cause

The document contains syntax errors.

Response

Fix the syntax errors in the document.

XDMP-DOCBADENTITY

Message Text

Incomplete markup in entity value variable1 at variable2 line variable3

XDMP-DOCBADSTR

Message Text

Unescaped newline characters in document string literal: "variable1" at variable2:variable3:variable4

Cause

The document string literal contains unescaped newline characters.

Response

Escape newline characters using "\n", or use the three quote form of string literal available in turtle.

XDMP-DOCCDATA

Message Text

CDATA section outside of content at variable1 line variable2

XDMP-DOCCHARREF

Message Text

Invalid character reference variable1 at variable2 line variable3

XDMP-DOCCOMMENTCHAR

Message Text

Unexpected character variable1 in comment at variable2 line variable3

Cause

Invalid syntax encountered while parsing an XML comment.

Response

Correct the content.

XDMP-DOCDOCTYPE

Message Text

Doctype declaration after element content at variable1 line variable2

XDMP-DOCDUPATTR

W3C XQuery Standard Equivalent: err:XQDY0025

Message Text

Two attributes with the same name at variable1 line variable2

XDMP-DOCENDTAGCHAR

Message Text

Unexpected character variable1 in end tag at variable2 line variable3

XDMP-DOCENTITYREF

Message Text

Invalid entity reference variable1 at variable2 line variable3

XDMP-DOCEXISTS

Message Text

Document exists at destination

XDMP-DOCHEXCHARREF

Message Text

Invalid hex character reference variable1 at variable2 line variable3

XDMP-DOCNOBINDING

W3C XQuery Standard Equivalent: err:FODC0005

Message Text

Available documents provides no mapping for URI

XDMP-DOCNOENDTAG

Message Text

Expecting end tag variable1 at variable2 line variable3

XDMP-DOCNONSBIND

Message Text

No namespace binding for prefix variable1 at variable2 line variable3

XDMP-DOCNOTFOUND

Message Text

Document not found

Cause

No document exists with the document URI specified in an operation such as a document copy, move, or delete.

Response

Correct the URI or code and re-try the operation.

XDMP-DOCPREFIX

Message Text

No namespace binding for prefix: "variable1" at variable2:variable3:variable4

Cause

The document prefix has not been bound to a namespace URI.

Response

Fix the document to include a prefix binding.

XDMP-DOCRECURSE

Message Text

Recursive entity reference variable1 at variable2 line variable3

Cause

The XML parser encountered an entity reference that is self-referential. It is possible to create recursive entity references in a DTD. For example, an input document of this form will throw XDMP-DOCRECURSE if read in by xdmp:document-get because the entities ONE and TWO refer to each other:

<?xml version="1.0"?>
<!DOCTYPE RecursiveDTD[
<!ENTITY ZERO "A">
<!ENTITY ONE "&TWO;">
<!ENTITY TWO "&ONE;">
]>
<data>&TWO;</data>

Response

Correct the content or DTD and re-try the operation.

XDMP-DOCROOTTEXT

Message Text

Invalid root text variable1 at variable2 line variable3

Cause

Text appears at the root of an XML document. For example:

<?xml version="1.0"?>
text at root
<data>text not at root</data>

Response

Repair the content and re-try the operation. For example, insert a root element:

<?xml version="1.0"?>
<added-root>
text at root
<data>text not at root</data>
</added-root>

XDMP-DOCSTARTTAGCHAR

Message Text

Unexpected character variable1 in start tag at variable2 line variable3

XDMP-DOCUNENDTAG

Message Text

Unexpected end tag variable1 at variable2 line variable3

XDMP-DOCUNEOF

Message Text

Unexpected end of file at variable1 line variable2 (variable3 starting at line variable4)

XDMP-DOCUNEXPECTED

Message Text

variable1 at variable2:variable3:variable4

Cause

The document contains syntax errors.

Response

Fix the syntax errors in the document.

XDMP-DOCURI

Message Text

Invalid URI format: "variable1" at variable2:variable3:variable4

Cause

A URI in the document has invalid syntax.

Response

Correct the URI, or parse using "repair" mode.

XDMP-DOCUTF8SEQ

Message Text

Invalid UTF-8 escape sequence at variable1 line variable2 -- document is not UTF-8 encoded

XDMP-DOCUTF8SEQ2

Message Text

Invalid UTF-8 escape sequence variable1 at variable2:variable3:variable4 -- document is not UTF-8 encoded

Cause

A bad UTF-8 byte code sequence was found in the document.

Response

Encode your document in UTF-8 correctly.

XDMP-DOCWHITESPACE

Message Text

Expecting mandatory whitespace at variable1 line variable2

XDMP-DOCXMLCHAR

Message Text

Invalid XML character codepoint variable1 at variable2 line variable3 -- document contains non-XML character

Cause

The XML document contains a codepoint that is not legal XML.

Response

Consider running xdmp:tidy to convert the document to legal XHTML, specifically to replace illegal XML codepoints with benign codepoints.

XDMP-DOLLAR

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Missing $ before variable variable1

XDMP-DOMAIN

Message Text

Domain error

XDMP-DUPATTR

W3C XQuery Standard Equivalent: err:XQDY0025

Message Text

Two attributes with the same name

XDMP-DUPBASEURIDECL

W3C XQuery Standard Equivalent: err:XQST0032

Message Text

Only one base-uri declaration allowed per module

Cause

The XQuery module includes two base-uri declarations.

Response

Remove one of the declarations.

XDMP-DUPCONSTRUCTDECL

W3C XQuery Standard Equivalent: err:XQST0067

Message Text

Only one construction declaration allowed per module

Cause

The XQuery module includes two construction declarations.

Response

Remove one of the declarations.

XDMP-DUPCOPYNSDECL

W3C XQuery Standard Equivalent: err:XQST0055

Message Text

Only one copy-namespaces declaration allowed per module

Cause

The XQuery module includes two copy-namespace declarations.

Response

Remove one of the declarations.

XDMP-DUPDEFCOLLDECL

W3C XQuery Standard Equivalent: err:XQST0038

Message Text

Only one default collation declaration allowed per module

Cause

The XQuery module includes two default collation declarations.

Response

Remove one of the declarations.

XDMP-DUPEMPTYORDERDECL

W3C XQuery Standard Equivalent: err:XQST0069

Message Text

Only one empty order declaration allowed per module

Cause

The XQuery module includes two empty order declarations.

Response

Remove one of the declarations.

XDMP-DUPNSDECL

W3C XQuery Standard Equivalent: err:XQST0071

W3C XSLT Standard Equivalent: err:XTDE0430

Message Text

Duplicate namespace declaration variable1

Cause

The XQuery module includes two namespace declarations for the same prefix.

Response

Remove one of the declarations.

XDMP-DUPORDERINGDECL

W3C XQuery Standard Equivalent: err:XQST0065

Message Text

Only one ordering declaration allowed per module

Cause

The XQuery module includes two ordering declarations.

Response

Remove one of the declarations.

XDMP-DUPPROLOGDECL

Message Text

Only one "variable1" declaration allowed per module

Cause

The XQuery module includes two prolog declarations that are the same.

Response

Remove one of the declarations.

XDMP-DUPRULE

Message Text

Duplicate rule name in ruleset "variable1": "variable2"

Cause

The ruleset has a rule with the same name as another rule in one of the transitively imported rulesets.

Response

MarkLogic tries to avoid duplicate rules as they inefficient and pointless during inference. Either remove the duplicate rule, or if it is actually different rename it.

XDMP-DUPSPACEDECL

W3C XQuery Standard Equivalent: err:XQST0068

Message Text

Only one "variable1" declaration allowed per module

Cause

The XQuery module includes two boundary space declarations.

Response

Remove one of the declarations.

XDMP-DUPVALIDDECL

Message Text

Only one validation declaration allowed per module

Cause

The XQuery module includes two validation declarations.

Response

Remove one of the declarations.

XDMP-DUPXID

Message Text

Transaction with Xid variable1 already exists

Cause

The Xid specified by the XA transaction manager already exists. This indicates that the transaction manager is misbehaving.

Response

Contact your transaction manager vendor with a bug report.

XDMP-DURATIONOVERFLOW

W3C XQuery Standard Equivalent: err:FODT0002

Message Text

Overflow in duration arithmetic

XDMP-EFFBOOLVALUE

W3C XQuery Standard Equivalent: err:FORG0006

Message Text

Effective Boolean Value is undefined for variable1

Cause

The sequence cannot be converted into a boolean value using the implicit XQuery effective boolean value operation.

Response

Use a comparison, universal quantification, or otherwise to determine the correct truth for your condition.

XDMP-ELEMATTRGIDXAMBIGUOUS

Message Text

Ambiguous geospatial variable1 element-attribute index for variable2/@variable3 variable4

Cause

The options provided are not sufficient to uniquely identify an element-attribute geospatial point index.

Response

Specify type, coordinate-system, and/or precision options to uniquely identify an element-attribute geospatial point index.

XDMP-ELEMATTRGIDXNOTCOLL

Message Text

Collations are irrelevant to the geospatial variable1 element-attribute index for variable2/@variable3 variable4

Cause

The options to the query include a collation, but the geospatial point index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMATTRGIDXNOTFOUND

Message Text

No geospatial variable1 element-attribute index for variable2/@variable3 variable4 variable5

Cause

The query requires a geospatial point index that does not exist.

Response

Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMATTRGIDXNOTPOSN

Message Text

Positions are not enabled on the geospatial variable1 element-attribute index for variable2/@variable3 variable4

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.

Response

Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.

XDMP-ELEMATTRLXCNNOTFOUND

Message Text

No element-attribute word lexicon for variable1/@variable2 variable3

Cause

The query requires a lexicon that does not exist.

Response

Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMATTRPAIRGIDXAMBIGUOUS

Message Text

Ambiguous geospatial variable1 element-attribute-pair index for variable2/@variable3 variable2/@variable4 variable5

Cause

The options provided are not sufficient to uniquely identify an element-attribute-pair geospatial point index.

Response

Specify type, coordinate-system, and/or precision options to uniquely identify an element-attribute-pair geospatial point index.

XDMP-ELEMATTRPAIRGIDXNOTCOLL

Message Text

Collations are irrelevant to the geospatial variable1 element-attribute-pair index for variable2/@variable3 variable2/@variable4 variable5

Cause

The options to the query include a collation, but the geospatial point index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMATTRPAIRGIDXNOTFOUND

Message Text

No geospatial variable1 element-attribute-pair index for variable2/@variable3 variable2/@variable4 variable5 variable6

Cause

The query requires a geospatial point index that does not exist.

Response

Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMATTRPAIRGIDXNOTPOSN

Message Text

Positions are not enabled on the geospatial variable1 element-attribute-pair index for variable2/@variable3 variable2/@variable4 variable5

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.

Response

Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.

XDMP-ELEMATTRPAIRLXCNNOTFOUND

Message Text

No element-attribute-pair word lexicon for variable1/@variable2 variable1/@variable3 variable4

Cause

The query requires a lexicon that does not exist.

Response

Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMATTRPAIRRIDXAMBIGUOUS

Message Text

Ambiguous variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5

Cause

The options provided are not sufficient to uniquely identify an element-attribute-pair range index.

Response

Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element-attribute-pair range index.

XDMP-ELEMATTRPAIRRIDXNOTCOLL

Message Text

Collations are irrelevant to the variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5

Cause

The options to the query include a collation, but the range index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMATTRPAIRRIDXNOTCOORD

Message Text

Coordinate systems are irrelevant to the variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5

Cause

The options to the query include a coordinate system, but the range index is not a geospatial data type.

Response

Do not specify a coordinate system in the query's options.

XDMP-ELEMATTRPAIRRIDXNOTFOUND

Message Text

No variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5 variable6

Cause

The query requires a range index that does not exist.

Response

Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMATTRPAIRRIDXNOTPOSN

Message Text

Positions are not enabled on the variable1 element-attribute-pair range index for variable2/@variable3 variable2/@variable4 variable5

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.

Response

Either enable positions on the range index or do not specify "ordered" or "proximity" options.

XDMP-ELEMATTRRIDXAMBIGUOUS

Message Text

Ambiguous variable1 element-attribute range index for variable2/@variable3 variable4

Cause

The options provided are not sufficient to uniquely identify an element-attribute range index.

Response

Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element-attribute range index.

XDMP-ELEMATTRRIDXNOTCOLL

Message Text

Collations are irrelevant to the variable1 element-attribute range index for variable2/@variable3 variable4

Cause

The options to the query include a collation, but the range index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMATTRRIDXNOTCOORD

Message Text

Coordinate systems are irrelevant to the variable1 element-attribute range index for variable2/@variable3 variable4

Cause

The options to the query include a coordinate system, but the range index is not a geospatial data type.

Response

Do not specify a coordinate system in the query's options.

XDMP-ELEMATTRRIDXNOTFOUND

Message Text

No variable1 element-attribute range index for variable2/@variable3 variable4 variable5

Cause

The query requires a range index that does not exist.

Response

Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMATTRRIDXNOTPOSN

Message Text

Positions are not enabled on the variable1 element-attribute range index for variable2/@variable3 variable4

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.

Response

Either enable positions on the range index or do not specify "ordered" or "proximity" options.

XDMP-ELEMCHILDGIDXAMBIGUOUS

Message Text

Ambiguous geospatial variable1 element-child index for variable2/variable3 variable4

Cause

The options provided are not sufficient to uniquely identify an element-child geospatial point index.

Response

Specify type, coordinate-system, and/or precision options to uniquely identify an element-child geospatial point index.

XDMP-ELEMCHILDGIDXNOTCOLL

Message Text

Collations are irrelevant to the geospatial variable1 element-child index for variable2/variable3 variable4

Cause

The options to the query include a collation, but the geospatial point index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMCHILDGIDXNOTFOUND

Message Text

No geospatial variable1 element-child index for variable2/variable3 variable4 variable5

Cause

The query requires a geospatial point index that does not exist.

Response

Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMCHILDGIDXNOTPOSN

Message Text

Positions are not enabled on the geospatial variable1 element-child index for variable2/variable3 variable4

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.

Response

Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.

XDMP-ELEMCHILDLXCNNOTFOUND

Message Text

No element-child word lexicon for variable1/variable2 variable3

Cause

The query requires a lexicon that does not exist.

Response

Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMCHILDRIDXAMBIGUOUS

Message Text

Ambiguous variable1 element-child range index for variable2/variable3 variable4

Cause

The options provided are not sufficient to uniquely identify an element-child range index.

Response

Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element-child range index.

XDMP-ELEMCHILDRIDXNOTCOLL

Message Text

Collations are irrelevant to the variable1 element-child range index for variable2/variable3 variable4

Cause

The options to the query include a collation, but the range index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMCHILDRIDXNOTCOORD

Message Text

Coordinate systems are irrelevant to the variable1 element-child range index for variable2/variable3 variable4

XDMP-ELEMCHILDRIDXNOTFOUND

Message Text

No variable1 element-child range index for variable2/variable3 variable4 variable5

Cause

The query requires a range index that does not exist.

Response

Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMCHILDRIDXNOTPOSN

Message Text

Positions are not enabled on the variable1 element-child range index for variable2/variable3 variable4

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.

Response

Either enable positions on the range index or do not specify "ordered" or "proximity" options.

XDMP-ELEMGIDXAMBIGUOUS

Message Text

Ambiguous geospatial variable1 element index for variable2 variable3

Cause

The options provided are not sufficient to uniquely identify an element geospatial point index.

Response

Specify type, coordinate-system, and/or precision options to uniquely identify an element geospatial point index.

XDMP-ELEMGIDXNOTCOLL

Message Text

Collations are irrelevant to the geospatial variable1 element index for variable2 variable3

Cause

The options to the query include a collation, but the geospatial point index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMGIDXNOTFOUND

Message Text

No geospatial variable1 element index for variable2 variable3 variable4

Cause

The query requires a geospatial point index that does not exist.

Response

Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMGIDXNOTPOSN

Message Text

Positions are not enabled on the geospatial variable1 element index for variable2 variable3

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.

Response

Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.

XDMP-ELEMLXCNNOTFOUND

Message Text

No element word lexicon for variable1 variable2

Cause

The query requires a lexicon that does not exist.

Response

Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMNAME

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Cannot use variable1 as an element name

XDMP-ELEMPAIRGIDXAMBIGUOUS

Message Text

Ambiguous geospatial variable1 element-pair index for variable2/variable3 $2/variable4 variable5

Cause

The options provided are not sufficient to uniquely identify an element-pair geospatial point index.

Response

Specify type, coordinate-system, and/or precision options to uniquely identify an element-pair geospatial point index.

XDMP-ELEMPAIRGIDXNOTCOLL

Message Text

Collations are irrelevant to the geospatial variable1 element-pair index for variable2/variable3 variable2/variable4 variable5

Cause

The options to the query include a collation, but the geospatial point index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMPAIRGIDXNOTFOUND

Message Text

No geospatial variable1 element-pair index for variable2 variable3 variable4 variable5

Cause

The query requires a geospatial point index that does not exist.

Response

Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMPAIRGIDXNOTPOSN

Message Text

Positions are not enabled on the geospatial variable1 element-pair index for variable2/variable3 variable2/variable4 variable5

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.

Response

Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.

XDMP-ELEMPAIRLXCNNOTFOUND

Message Text

No element-pair word lexicon for variable1 variable2 variable3

Cause

The query requires a lexicon that does not exist.

Response

Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMPAIRRIDXAMBIGUOUS

Message Text

Ambiguous variable1 element-pair range index for variable2/variable3 $2/variable4 variable5

Cause

The options provided are not sufficient to uniquely identify an element-pair range index.

Response

Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element-pair range index.

XDMP-ELEMPAIRRIDXNOTCOLL

Message Text

Collations are irrelevant to the variable1 element-pair range index for variable2/variable3 variable2/variable4 variable5

Cause

The options to the query include a collation, but the range index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMPAIRRIDXNOTCOORD

Message Text

Coordinate systems are irrelevant to the variable1 element-pair range index for variable2/variable3 variable2/variable4 variable5

Cause

The options to the query include a coordinate system, but the range index is not a geospatial data type.

Response

Do not specify a coordinate system in the query's options.

XDMP-ELEMPAIRRIDXNOTFOUND

Message Text

No variable1 element-pair range index for variable2 variable3 variable4 variable5

Cause

The query requires a range index that does not exist.

Response

Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMPAIRRIDXNOTPOSN

Message Text

Positions are not enabled on the variable1 element-pair range index for variable2/variable3 variable2/variable4 variable5

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.

Response

Either enable positions on the range index or do not specify "ordered" or "proximity" options.

XDMP-ELEMRIDXAMBIGUOUS

Message Text

Ambiguous variable1 element range index for variable2 variable3

Cause

The options provided are not sufficient to uniquely identify an element range index.

Response

Specify type, collation, coordinate-system, and/or precision options to uniquely identify an element range index.

XDMP-ELEMRIDXNOTCOLL

Message Text

Collations are irrelevant to the variable1 element range index for variable2 variable3

Cause

The options to the query include a collation, but the range index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-ELEMRIDXNOTCOORD

Message Text

Coordinate systems are irrelevant to the variable1 element range index for variable2 variable3

Cause

The options to the query include a coordinate system, but the range index is not a geospatial data type.

Response

Do not specify a coordinate system in the query's options.

XDMP-ELEMRIDXNOTFOUND

Message Text

No variable1 element range index for variable2 variable3 variable4

Cause

The query requires a range index that does not exist.

Response

Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.

XDMP-ELEMRIDXNOTPOSN

Message Text

Positions are not enabled on the variable1 element range index for variable2 variable3

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.

Response

Either enable positions on the range index or do not specify "ordered" or "proximity" options.

XDMP-EMPTY

Message Text

Node is empty: variable1

XDMP-EMPTYBASEURI

W3C XQuery Standard Equivalent: err:XTDE1420

Message Text

Empty sequence not allowed as a base node

XDMP-EMPTYISOL

Message Text

Isolation option is empty: variable1

XDMP-EMPTYROOT

Message Text

Root option is empty: variable1

XDMP-EMPTYUSERID

Message Text

User-id option is empty

XDMP-EMPTYXQUERYVERSION

Message Text

Default XQuery Version option is empty (must be "0.9-ml", "1.0", "1.0-ml" or "app-server"): variable1

XDMP-ENCODING

W3C XQuery Standard Equivalent: err:XQST0087

Message Text

Unsupported character encoding: variable1

XDMP-ENCRYPTFAILED

Message Text

Failed to encrypt, variable1

Cause

There is a key encryption key missmatch

Response

Make sure that there are not keystore configuration issue. see xdmp:keystore-statau()

XDMP-ENDDOCUMENT

Message Text

There is no started document.

XDMP-ENDED

Message Text

Transaction already ended, variable1

XDMP-ENDELEMENT

Message Text

There is no started element.

XDMP-ENDTAG

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

End tag variable2 does not match start tag variable1

XDMP-ENRICHNOTAVAIL

Message Text

Entity enrichment libraries not installed for host variable1

XDMP-ENTITYREF

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Invalid entity reference variable1

XDMP-EVALLIBMOD

Message Text

Cannot evaluate library module: variable1

Cause

The specified library module cannot be evaluated.

Response

This error sometimes occurs when a file exists with the same path under the Modules directory and under the App Server root, and if the one under the Modules directory cannot evaluate for some reason (for example, because it is a library module). If this is the case, either fix the module under the Modules directory or use a different name for the module that does not exist under the Modules directory.

XDMP-EVALQUERY

Message Text

No query to eval

XDMP-EXPNTREECACHEFULL

Message Text

Expanded tree cache full on host variable1 uri variable2

Cause

The expanded tree cache ran out of space, preventing completion of the query.

The expanded tree cache stores XML fragments during query processing. The expanded tree cache must be large enough to hold a copy of all expanded XML fragments needed concurrently during query evaluation. Depending on what the query does and how it is constructed, the set of concurrent fragments may not include every fragment used by the query.

Response

This error may be addressed by modifying your query or your cache configuration.

Tune your query to require fewer expanded XML fragments. For example, tune the query to return fewer results or paginate the results.Tune your query to require fewer concurrent cached fragments.Increase the size of the expanded tree cache, using the setting under Groups > Default > Configure. Since increasing the cache size may strain other system resources, you should first attempt to modify or tune your query.If the error occurs only when processing large documents, consider fragmenting your content.

XDMP-EXPR

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Invalid expression

Cause

XDMP-EXPR occurs when the operands of an expression have incompatible types. For example, attempting to add a numeric value and a string, or when the actual type of an expression does not match a required expected type.

(: generates XDMP-EXPR :)
let $x = 1 + "abc" ...
      

XDMP-EXPR may also occur as the side-effect of another syntax or semantic error.

Response

Correct your code.

XDMP-EXPRONLY

Message Text

xdmp:value only accepts simple expressions

XDMP-EXTENSION

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

MarkLogic extension syntax used, variable1 are not supported in variable2 mode

Cause

The XQuery syntax used is only available with MarkLogic syntax extensions enabled.

Response

MarkLogic extension syntax can be enabled by using a version declaration of "1.0-ml".

XDMP-EXTFUN

Message Text

Undefined external function variable1

Cause

No implementation can be found for the external function declared.

Response

External functions are not currently supported by MarkLogic - you should provide the body of the function using XQuery.

XDMP-EXTIME

Message Text

Time limit exceeded

Cause

A query or other operation exceeded its processing time limit. Inefficient queries frequently cause timeouts.

Surrounding messages in the log file may pinpoint the operation which timed out. In the example below, the timeout occurs during re-indexing:

Warning: XDMP-FORESTERR: Error in reindex of forest some_forest:
  XDMP-REFRAGMENT: Error refragmenting fn:doc("some_doc"):
    XDMP-EXTIME: Time limit exceeded
      

Response

If you determine the cause of the timeout is an inefficient or incorrect query, tune your query.

If you determine the cause of the time is an inadequate processing limit, you may be able to configure a more generous limit through the Admin Interface.

For more information on configuring timeouts, see the Administrator's Guide.

XDMP-EXTNIMPRT

Message Text

Cannot import extension: variable1

XDMP-EXTVAR

W3C XQuery Standard Equivalent: err:XPDY0002

Message Text

Undefined external variable variable1

Cause

The external global variable has not had a value assigned to it.

Response

Provide a value for the variable when calling xdmp:eval, xdmp:invoke etc. If you are not using these functions, then MarkLogic has no method to provide values for external variables - you should assign the global variable a value directly in the query.

XDMP-FATAL

Message Text

Fatal: variable1

XDMP-FEATUREPREFIX

W3C XQuery Standard Equivalent: err:XPST0081

Message Text

Prefix not found in the statically known namespaces: variable1

XDMP-FIELDGIDXAMBIGUOUS

Message Text

Ambiguous geospatial variable1 field index for variable2 variable3

Cause

The options provided are not sufficient to uniquely identify a field geospatial point index.

Response

Specify type, coordinate-system, and/or precision options to uniquely identify a field geospatial point index.

XDMP-FIELDGIDXNOTCOLL

Message Text

Collations are irrelevant to the geospatial variable1 field index for variable2 variable3

Cause

The options to the query include a collation, but the geospatial point index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-FIELDGIDXNOTFOUND

Message Text

No geospatial variable1 field index for variable2 variable3 variable4

Cause

The query requires a geospatial point index that does not exist.

Response

Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.

XDMP-FIELDGIDXNOTPOSN

Message Text

Positions are not enabled on the geospatial variable1 field index for variable2 variable3

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.

Response

Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.

XDMP-FIELDLXCNNOTFOUND

Message Text

No field word lexicon for variable1 variable2

Cause

A user has attempted either of the lexicon functions cts:field-words or cts:field-word-match on a field, when there is no word lexicon built for the field.

Response

Define a word lexicon and wait for reindexing to complete before using the lexicon functions on the field.

XDMP-FIELDRIDXAMBIGUOUS

Message Text

Ambiguous variable1 field range index for variable2 variable3

Cause

The options provided are not sufficient to uniquely identify a field range index.

Response

Specify type, collation, coordinate-system, and/or precision options to uniquely identify a field range index.

XDMP-FIELDRIDXNOTCOLL

Message Text

Collations are irrelevant to the variable1 field range index for variable2 variable3

Cause

The options to the query include a collation, but the range index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-FIELDRIDXNOTCOORD

Message Text

Coordinate systems are irrelevant to the variable1 field range index for variable2 variable3

Cause

The options to the query include a coordinate system, but the range index is not a geospatial data type.

Response

Do not specify a coordinate system in the query's options.

XDMP-FIELDRIDXNOTFOUND

Message Text

No variable1 field range index for variable2 variable3 variable4

Cause

The query requires a range index that does not exist.

Response

Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.

XDMP-FIELDRIDXNOTPOSN

Message Text

Positions are not enabled on the variable1 field range index for variable2 variable3

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.

Response

Either enable positions on the range index or do not specify "ordered" or "proximity" options.

XDMP-FILESIZES

Message Text

Inconsistent file sizes for variable1: variable2

XDMP-FNPUBPRIV

W3C XQuery Standard Equivalent: err:XQST0106

Message Text

A function declaration's annotations cannot contain more than one annotation named %fn:private or %fn:public.

Cause

The function declaration contains duplicate %fn:public or %fn:private annotations, or contains both these annotations.

Response

Remove one or more annotations.

XDMP-FORESTBACKUPFAILED

Message Text

Backup failed for forest variable1: exception_stack

XDMP-FORESTDETACHED

Message Text

Forest must be attached to a database and merge timestamp in the database must be set to non-zero value when restoring with journal archiving and restore-to-time is zero

XDMP-FORESTDISABLED

Message Text

Forest variable1 is disabled

Cause

The forest is disabled.

Response

Enable the forest.

XDMP-FORESTERR

Message Text

Error in variable1 of forest variable2: exception_stack

Cause

An error occurred while processing the named forest, such as during a re-index or checkpoint operation. The underlying error messages are displayed after the forest name.

Response

Refer to the underlying errors for additional information.

XDMP-FORESTINCRBACKUPFAILED

Message Text

Incremental backup failed for forest variable1: exception_stack

XDMP-FORESTMNT

Message Text

Forest variable1 not mounted: exception_stack

Cause

XDMP-FORESTMNT is usually seen as a Debug level message when mounting of a forest fails at startup or during a forest restart.

When any instance of MarkLogic Server in a cluster starts up or a forest restarts, each host tries to mount all the forests configured for the entire cluster. A forest is successfully mounted once MarkLogic Server reads the forest information from the forest. If the mounting of a forest fails, XDMP-FORESTMNT is logged and the system retries the mount.

Response

If the message is reported at the Debug level and is eventually followed by a successful mount report, no action is required.

If this message occurs repeatedly, while attempting to mount a remote forest, you may have a network connectivity issue or the machine hosting the forest on local disk may be down.

XDMP-FORESTNID

Message Text

Specified forest variable1 not in database

XDMP-FORESTNOBACKUPSINCERESTORE

Message Text

Forest variable1 has no backup since last restore

XDMP-FORESTNOT

Message Text

Forest variable1 not available: exception_stack

Cause

The named forest is unavailable for the current operation. The exception_stack shows the underlying errors that caused XDMP-FORESTNOT.

Response

Review the errors in the exception_stack to identify and address the underlying cause. For example, the full error stack might look like:

XDMP-FORESTNOT: Forest Security not available:
  XDMP-FORESTERR: Error in startup of forest Security:
    XDMP-NOJOURNAL: No journal for recovery token {...}

In this case, MarkLogic Server was started by a non-root user, preventing the system from accessing the Security forest.

XDMP-FORESTNOTINDB

Message Text

Forest is not in a database: variable1

Cause

This occurs during replication or journal replay if a forest is not assigned to a database.

Response

Assign the forest to a database.

XDMP-FORESTNOTLOCAL

Message Text

Forest variable1 is not local to host variable2

XDMP-FORESTNOTOPEN

Message Text

$m with identifier variable1

XDMP-FORESTOPIN

Message Text

Forest variable1 has a variable2 operation in progress

Cause

The system attempted to start one forest operation (backup, restore, remove, clear, etc.) while another, exclusive operation was already in progress. For example, starting a new backup while a previous backup is still in progress.

Response

Resolution depends upon the context of the overlapping operations. If you need assistance determing the underlying cause, contact MarkLogic Technical Support.

XDMP-FORESTRESTOREFAILED

Message Text

Restore failed for forest variable1: exception_stack

XDMP-FORESTRETIRED

Message Text

Retired forests don't allow new inserts variable1

XDMP-FORESTSTATE

Message Text

Bad state transition on Forest variable1 state 'variable2' => 'variable3'

XDMP-FORESTTAKEN

Message Text

Forest variable1 unexpectedly taken by host variable2

Cause

More than one host attempted to write to the same forest label. XDMP-FORESTTAKEN most often occurs when the host reporting the error loses connection with the rest of cluster, yet is still up. The failure sequence may be:

The problem host loses connection with the rest of the cluster and its networked storage. This might be due to excessive load or network connectivity problems.The cluster detects that the problem host is offline and fails its forests over to other hosts in the cluster.The problem host rejoins the cluster and discovers its forests have been taken by another host. The problem host then reports XDMP-FORESTTAKEN and restarts.

Response

If the host reporting XDMP-FORESTTAKEN is actually temporarily disconnected from its cluster, the system is performing as expected. No action is required.

If the cluster disconnection is unexpected, investigate the cause of the interruption. Possible causes include network interrupts, heavy load, or thread starvation on the reporting host.

If the cluster disconnection is due to regular, expected load, consider changing the host timeout or XDQP timeout. For more information, see Configuring Failover for a Forest in the Scalabilty, Availability, and Failover Guide. Increasing these timeouts increases how long it takes the system to detect and respond to a real outage.

XDMP-FORESTTASKSTATUSUNKNOWN

Message Text

Task status unknown for forest variable1 on host variable2

XDMP-FORESTTIM

Message Text

Forest variable1 variable2 operation timed out

XDMP-FORMAT

Message Text

Invalid format (must be "xml", "text", or "binary"): variable1

Cause

Occurs when parsing a document and specifying the document format. The format must be one of "xml", "text", or "binary".

Response

Use a valid document format string, "xml", "text", or "binary".

XDMP-FOUNDSTAND

Message Text

Found stand in forest variable1: variable2

XDMP-FOUNDSTANDS

Message Text

Found stands in forest variable1: variable2

XDMP-FRAGMENT

Message Text

Cannot cross fragment boundary

XDMP-FRAGMENTPROTECTEDPATH

Message Text

Fragment with protected path doc("variable1")//variable2

Cause

Fragment with protected path

Response

Check element level security and fragmentation setting for any path overlap.

XDMP-FRAGSET

Message Text

Fragset not found

Cause

When a lexicon function has a query constraint, a request is made to the D-nodes to construct a fragset with the results. If that fragset is not available when later requested the error is thrown. The operation is retried. In normal operations this error is not expected, but may be seen when they a large number of facet-heavy operations occur at one time.

Response

The application or system provisioning need to be adjusted.

XDMP-FRAGTOOLARGE

Message Text

Fragment of variable1 too large for in-memory storage: exception_stack

Cause

The document is too large to load into the database as a single fragment.

Response

Develop and configure a fragmentation strategy or break up the document into smaller pieces.

XDMP-FUNCTIONCYCLE

Message Text

A cycle was detected in the function closure

Cause

A function cannot be member of its own closure, either directly or indirectly.

Response

Do not add the function as a member of itself.

XDMP-FUNNS

W3C XQuery Standard Equivalent: err:XQST0048

Message Text

Function variable1 not in target namespace variable2

XDMP-FUNNSREQ

W3C XQuery Standard Equivalent: err:XQST0060

W3C XSLT Standard Equivalent: err:XTSE0740

Message Text

Functions must be declared in a non-empty namespace

Cause

The function was declared using a name in no namespace.

Response

Use a prefix or a default function namespace to put the function in your chosen namespace.

XDMP-FUNNSRES

W3C XQuery Standard Equivalent: err:XQST0045

W3C XSLT Standard Equivalent: err:XTSE0080

Message Text

Functions may not be declared in a reserved namespace

Cause

A function was declared in a reserved namespace.

Response

Choose a different namespace for your function.

XDMP-FWDVAR

W3C XQuery Standard Equivalent: err:XPST0008

Message Text

Forward reference to global variable variable1

Cause

A global variable has been referenced before its declaration.

Response

Move the global variable declaration before its reference.

XDMP-GEO-WRONGTYPE

Message Text

Scalar type must be either point or long-lat-point.

Cause

Incorrect "type" option is passed into the geospatial cts reference or query call. Geospatial point range indexes can only be of type "point" or "long-lat-point". Element pair and element attribute pair geospatial point indexes can only be of type "point".

Response

Correct the code.

XDMP-GEOHASH-COORD

Message Text

Geohashes cannot be computed for this coordinate system: variable1

Cause

Geohashes can only be calculated for a geographic coordinate system. This error occurs if you attempt to calculate geohashes using a non-geographic coordinate system, such as "raw."

Response

Use a geographic coordinate system, such as "wgs84."

XDMP-GEOHASH-TOLERANCE

Message Text

Goehash error variable1

Cause

Tolerance is too big for the geohash precision.

Response

Use double precision or use a smaller tolerance or use smaller geoshash precision.

XDMP-GEOREGIONIDX

Message Text

Geospatial region index error: variable1 variable2: variable3

Cause

User inserted a document that could not be indexed by the geospatial region index, and the region index is configured to reject invalid values.

Response

Change the data. If the data cannot be changed and you still want to insert the data, then configure the geospatial region index to accept invalid values.

XDMP-GEOREGIONIDX-NOTFOUND

Message Text

No geospatial region index for variable1 variable2

Cause

The query requires a geospatial region index that does not exist.

Response

Make sure the geospatial region index exists and that it uses the coordinate system specified in the query. If the geospatial region index was added recently, make sure reindexing is enabled and has completed.

XDMP-GEOREGIONIDX-TOOBIG

Message Text

Too many entries in geospatial region index variable1

XDMP-GEOVAL

Message Text

Element variable1 contains invalid geospatial value

XDMP-GETOVERLAPRES

Message Text

GetOverlappedResult variable1: variable2

XDMP-GIDXAMBIGUOUS

Message Text

Ambiguous geospatial variable1 index for variable2 variable3

Cause

The options provided are not sufficient to uniquely identify a geospatial point index.

Response

Specify type, coordinate-system, and/or precision options to uniquely identify a geospatial point index.

XDMP-GIDXNOTCOLL

Message Text

Collations are irrelevant to the geospatial variable1 index for variable2 variable3

Cause

The options to cts:reference include a collation, but the geospatial point index is not a string data-type.

Response

Do not specify a collation in the cts:reference's options.

XDMP-GIDXNOTFOUND

Message Text

No geospatial variable1 index for variable2 variable3 variable4

Cause

The query requires a geospatial point index that does not exist.

Response

Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.

XDMP-GIDXNOTPOSN

Message Text

Positions are not enabled on the geospatial variable1 index for variable2 variable3

Cause

User has specified "ordered" or "proximity" options on cts:value-tuples when positions are not enabled on the geospatial point index.

Response

Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options on cts:value-tuples.

XDMP-GSS

Message Text

GSS Error: variable1

XDMP-GZIPCOMPRESSION

Message Text

Error in GZIP compression

XDMP-GZIPDECOMPRESSION

Message Text

Error in GZIP decompression

XDMP-GZIPTOOBIG

Message Text

File is too big to be gzipped

XDMP-HASHLOCKINGRETRY

Message Text

Retry hash locking. Forests config hash does not match.

Cause

Hash locking sometimes need to retry when forest is added to or removed from a database.

Response

Retry until hash locking occurs.

XDMP-HEURCOM

Message Text

Transaction with identifier variable1 is heuristically committed

Cause

The XA transaction has already been heuristically committed.

Response

Your transaction manager should be handling this error automatically. This usually arises because an administrator explicitly committed a prepared XA transaction without the transaction manager.

XDMP-HEURRB

Message Text

Transaction with identifier variable1 is heuristically rolled back

Cause

The XA transaction has already been heuristically rolled back.

Response

Your transaction manager should be handling this error automatically. This usually arises because an administrator explicitly rolled back a prepared XA transaction without the transaction manager.

XDMP-HEXREF

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Invalid hex character reference variable1

XDMP-HOSTDOWN

Message Text

Host variable1 down: exception_stack

XDMP-HOSTOFFLINE

Message Text

Host is offline or not responding

XDMP-HTTP

Message Text

Only valid for an HTTP Server

Cause

Occurs when an API that is only supposed to work on an HTTP Server is called in a non-HTTP context.

Response

Fix the application.

XDMP-HTTP-DATA

Message Text

Can only PUT/POST binary or text data

Cause

Occurs when data that is neither text nor binary is passed as PUT/POST data.

Response

Fix the application.

XDMP-HTTP-MULTIPART

Message Text

Only valid for a HTTP request with the multipart/mixed or multipart/related content type

Cause

Occurs when an API that is only supposed to work for a multipart(mixed or related) request is called for other types of request.

Response

Fix the application.

XDMP-HTTP-PUT-POST

Message Text

Only valid for an HTTP PUT or POST request, not for variable1

Cause

Occurs when an API that is only supposed to work for a HTTP PUT or POST request is called for other types of request.

Response

Fix the application.

XDMP-ICUCONVRTFAILED

Message Text

Failed to convert the date with the given arguments.

XDMP-IGNOREAMPS

Message Text

ignore-amps option not allowed in this function

XDMP-ILLEGALPICTURE1

W3C XQuery Standard Equivalent: err:FOFD1340

W3C XSLT Standard Equivalent: err:XTDE1340

Message Text

Illegal picture format: Numeric presentation marker must end in '1' such as 001

Cause

If a numeric or date/time picture string contains a zero digit then the last digit must be a '1' and corespond to the same unicode range as the zero digit (The codepoint must be one greater than the codepoint used for the zero digit).

Response

When entering the format picture for numeric or date/time formatting functions you must1) use Unicode characters corresponding to the digits '0' and '1'2) they must be in the same Unicode range3) the '1' digit must be the last numeric digit.

XDMP-ILLEGALPICTURE4

W3C XQuery Standard Equivalent: err:FOFD1340

W3C XSLT Standard Equivalent: err:XTDE1340

Message Text

Illegal picture format: Minimum width cannot be more than maximum width

Cause

When specifying a minimum and maximum width such as [M,2-3], the minimum width must be greater or equal to the maximum width

Response

Specify a minimum width greater than or equal to the maximum width or omit both.

XDMP-ILLEGALPICTURE5

W3C XQuery Standard Equivalent: err:FOFD1340

W3C XSLT Standard Equivalent: err:XTDE1340

Message Text

Illegal picture format

Cause

An unexpected character or format in the picture format string.

Response

Check the format string for invalid format or characters.

XDMP-ILLEGALPICTURE6

W3C XQuery Standard Equivalent: err:FOFD1340

W3C XSLT Standard Equivalent: err:XTDE1340

Message Text

Illegal picture format: Variable component in the picture format must close with ']'

Cause

A '[' was found before a matching ']' or no matching ']' was found before the end of the picture string.

Response

Fix the picture string so there are properly matching '[' and ']' characters.

XDMP-ILLEGALPICTURE7

W3C XQuery Standard Equivalent: err:FOFD1340

W3C XSLT Standard Equivalent: err:XTDE1340

Message Text

Illegal picture format: ']' in literal component of the picture must have a following ']'

Cause

*REVIEW: The description is incorrect. should read: Illegal picture format: ']' in literal component of the picture must have a preceding '[' Cause: A ']' was encountered without a matching preceding '['.

Response

Edit the picture string to have matching '[' and ']' or escape the ']' with ']]'

XDMP-ILLEGALPICTURE8

W3C XQuery Standard Equivalent: err:FOFD1340

W3C XSLT Standard Equivalent: err:XTDE1340

Message Text

Illegal picture format. One of the variable markers doesn't have closing square brackets.

Cause

The picture string is missing a closing ']'.

Response

Correct the picture string to properly match '[' and ']'.

XDMP-ILLEGALPIORCOMMENT

Message Text

Binary and Text documents cannot have Processing Instructions or Comments

XDMP-ILLEGALSPECIFIER

W3C XQuery Standard Equivalent: err:FOFD1340

W3C XSLT Standard Equivalent: err:XTDE1340

Message Text

Illegal specifier variable1 in the picture format

Cause

An unrecognized specifier was found in the format picture string.

Response

Check and edit the picture format string for valid specifiers.

XDMP-ILLEGALSPECIFIER2

W3C XQuery Standard Equivalent: err:FOFD1350

W3C XSLT Standard Equivalent: err:XTDE1350

Message Text

Illegal specifier in the picture format

Cause

Caused by including a format specifier inappropriate for the function. For example, using an Hour specifier '[H]' in fn:format-date

Response

Check and correct format specifiers so they are appropriate to the function used.

XDMP-IMPDUPMODNS

W3C XQuery Standard Equivalent: err:XQST0047

Message Text

Namespace "variable1" was named in a previous module import, use a comma-separated list of module locations

XDMP-IMPMODNS

W3C XQuery Standard Equivalent: err:XQST0059

Message Text

Import module namespace variable1 does not match target namespace variable2 of imported module variable3

XDMP-IMPMODURI

W3C XQuery Standard Equivalent: err:XQST0059

Message Text

Cannot import module for namespace URI variable1 without location URI

XDMP-IMPNULMODNS

W3C XQuery Standard Equivalent: err:XQST0088

Message Text

Cannot import module with null namespace

XDMP-IMPORTMOD

Message Text

Cannot import Main Module variable1

XDMP-IMPORTPATH

Message Text

Invalid Module Import path: variable1

XDMP-INCOMPATCOLLATION

Message Text

Incompatible collation settings: variable1 and variable2

XDMP-INCOMPATFIELDS

Message Text

Incompatible fields: variable1 variable2

Cause

You ran a field query with multiple fields having different tokenization rules.

Response

Break the field query into separate field queries.

XDMP-INCOMPATKERNEL

Message Text

Cannot use variable1 kernel function with variable2 classifier

XDMP-INCOMPLETE

Message Text

Document incomplete

XDMP-INCONSCOORD

Message Text

variable1 and variable2 are inconsistent coordinate systems

Cause

A user may specify multiple coordinate-system options for index references, lexicon calls, and queries. This error occurs if the user has specified multiple inconsistent coordinate systems for the same index.

XDMP-INCONSGEOFORMAT

Message Text

variable1 and variable2 are inconsistent geospatial point format options

Cause

A user may specify multiple geospatial point formats for index references, lexicon calls, and queries. This error occurs if the user has specified multiple inconsistent geospatial point format options for the same index.

XDMP-INCONSISTENTIMPORT

Message Text

Inconsistent module imports? variable1

XDMP-INCONSOPTS

Message Text

Inconsistent options variable1 variable2

XDMP-INCONSPRECISION

Message Text

variable1 and variable2 are inconsistent coordinate system precision options

Cause

A user may specify multiple precision options for index references, lexicon calls, and queries. This error occurs if the user has specified multiple inconsistent coordinate system precision options for the same index.

XDMP-INCONSRIDX

Message Text

variable1 and variable2 are inconsistent range indexes

Cause

A user can specify multiple range indexes in cts:values and related functions. This error occurs if all the specified range indexes do not have the same scalar type, collation, and coordinate system.

Response

All range indexes supplied to cts:values or a related function must be consistent.

XDMP-INCONSTYPE

Message Text

variable1 and variable2 are inconsistent scalar types

Cause

A user may specify multiple types for index references, lexicon calls, and queries. This error occurs if the user has specified multiple inconsistent types for the same index.

XDMP-INCREMENTALCACHED

Message Text

Cannot use cached-incremental option with non-zero score function.

XDMP-INDEXATTR

Message Text

Attributes not allowed on element variable1

XDMP-INDEXATTRVAL

Message Text

Index reference attribute contains an invalid value: variable1

XDMP-INDEXELEM

Message Text

Index reference element contains unknown child: variable1

XDMP-INDEXNOCOORD

Message Text

Index reference requires a coordinate system: variable1

XDMP-INDEXNODE

Message Text

Index reference element variable1 contains unknown child

XDMP-INDEXPATHLEAF

Message Text

An indexable path must end with a name test: variable1

Cause

User has supplied a path expression that does not end with a name test.

Response

Correct the syntax of path expression such that it ends with a name test.

XDMP-INDEXPATHSELFAXIS

Message Text

An indexable path must not begin with a self axis: variable1

Cause

User has supplied a path expression that starts with a dot '.'.

Response

Correct the syntax of path expression such that it starts either in an element or a child axis or a descendent axis.

XDMP-INDEXTEXT

Message Text

Index reference element variable1 contains misplaced text

XDMP-INDEXVAL

Message Text

Index reference element contains an invalid value: variable1

XDMP-INFEXPR

W3C XQuery Standard Equivalent: err:FOAR0002

Message Text

A value of +INF or -INF not allowed here

XDMP-INFFULL

Message Text

The size limit for inferred triples in a ruleset store has been exceeded

Cause

The number of triples inferred by a sem:ruleset-store() during query execution has exceeded the maximum size configured.

Response

Increase the size of the inference memory configured for the sem:ruleset-store() using the "size=" option. You can also configure a higher default inference size using admin:appserver-set-max-inference-size() or the AppServer configuration section of the Admin UI.

XDMP-INFOREST

Message Text

Cannot move variable1.Document already in forest variable2

XDMP-INFSIZE

Message Text

Request inference size exceeds the maximum allowed.

XDMP-INITERR

Message Text

Initialization error: variable2 variable3: variable1

XDMP-INMEMSTANDINVSIZE

Message Text

InMemoryStand::recoverRangeIndexes: invalid size variable1

XDMP-INMEMTRPLFULL

Message Text

The size limit for an in-memory triple store has been exceeded

Cause

The number of triples passed to a call to sem:in-memory-store() has exceeded the maximum size allowed.

Response

Use fewer triples in a call to sem:in-memory-store().

XDMP-INMMFULL

Message Text

In-memory storage fullvariable1

Cause

An in-memory list for the index structure filled up and had to be written to disk.

Response

This is a normal artifact when the memory structure fills up. This is a retryable exception and will normally recover seamlessly, causing no problems. If the message occurs infrequently, you can ignore it. If the message occurs frequently, you can raise the cache sizes in the Group configuration, but normally this is not necessary.

XDMP-INMMGEOREGIONIDXFULL

Message Text

In-memory geospatial region index storage full variable1

Cause

The in-memory geospatial region index filled up. The stand will write to disk. This message is informational.

Response

This is a normal artifact when the memory structure fills up. This is a retryable exception and will normally recover seamlessly, causing no problems. If the message occurs infrequently, you can ignore it. If the message occurs frequently, you can raise the in-memory geospatial region index size in the Database configuration.

XDMP-INMMINDXFULL

Message Text

In-memory range-index storage fullvariable1

XDMP-INMMLISTFULL

Message Text

In-memory list storage fullvariable1

Cause

The in-memory list storage filled up. The stand will write to disk. This message is informational.

Response

This message is informational. No action is required.

XDMP-INMMTREEFULL

Message Text

In-memory tree storage fullvariable1

XDMP-INMMTRPLFULL

Message Text

In-memory triple storage fullvariable1

XDMP-INMREVIDXFULL

Message Text

In-memory reverse-index storage fullvariable1

XDMP-INPUTERROR

Message Text

Input error

Cause

An error was returned to MarkLogic while it was processing input to create a document. Details about the error are not known.

Response

Check the contents of the input source. Upgrade to a more recent version of MarkLogic for more error details.

XDMP-INTERNAL

Message Text

Internal error: variable1

Cause

A MarkLogic internal error has occurred.

Response

Report this error to MarkLogic as a bug.

XDMP-INTERNALERROR2

Message Text

Internal error [2] in formatter

Cause

A MarkLogic internal error has occurred.

Response

Report this error to MarkLogic as a bug.

XDMP-INTERNALERROR3

Message Text

Internal error [3] in formatter

Cause

A MarkLogic internal error has occurred.

Response

Report this error to MarkLogic as a bug.

XDMP-INTERNALERROR4

Message Text

Internal error [4] in formatter

Cause

A MarkLogic internal error has occurred.

Response

Report this error to MarkLogic as a bug.

XDMP-INTERNALERROR5

Message Text

Internal error [5] in formatter

Cause

A MarkLogic internal error has occurred.

Response

Report this error to MarkLogic as a bug.

XDMP-INTERNALERROR6

Message Text

Internal error [6] in formatter

Cause

A MarkLogic internal error has occurred.

Response

Report this error to MarkLogic as a bug.

XDMP-INTERNALERROR7

Message Text

Internal error [7] in formatter

Cause

A MarkLogic internal error has occurred.

Response

Report this error to MarkLogic as a bug.

XDMP-INVALDATE

Message Text

Invalid data specified. variable1

XDMP-INVALID-PERCENTAGE

Message Text

Invalid percentage: must be between 0 and 1 (inclusive)

Cause

The percentage is invalid.

Response

Correct your code.

XDMP-INVALID-TRAILINGSEARCH

Message Text

Invalid trailing search pattern: variable1

XDMP-INVALIDDIR

Message Text

Path is invalid as data directory: variable1

XDMP-INVALIDENCODING

Message Text

Expecting an encoding of either hex or base64.

XDMP-INVALIDLOWERBOUND

Message Text

Invalid lower bound: variable1

Cause

The lower bound has a data type that doesn't match the partition key.

Response

Check your configuration.

XDMP-INVALIDRANGEBOUNDARIES

Message Text

Invalid range boundaries: variable1

Cause

The lower bound is not smaller than the upper bound.

Response

Check your configuration.

XDMP-INVALIDTRIPLE

Message Text

The node does not represent a valid triple

Cause

The node is not an element or document node with element child, or it that element does not contain an "s", "p", or "o" child element.

Response

Correct the triple format.

XDMP-INVALIDTRIPLEMAP

Message Text

The JavaScript object or map:map does not represent a valid triple

XDMP-INVALIDTRIPLEOBJECT

Message Text

The object node does not represent a valid triple

XDMP-INVALIDUPPERBOUND

Message Text

Invalid upper bound: variable1

Cause

The upper bound has a data type that doesn't match the partition key.

Response

Check your configuration.

XDMP-INVALIDURITYPE

W3C XQuery Standard Equivalent: err:XTDE1420

Message Text

URI(s) can only be of types xs:string, xs:anyURI, xs:untypedAtomic or base URI of a node.

XDMP-INVALOCK

Message Text

Invalid activeLock element: variable1

XDMP-INVALTXDB

Message Text

Transaction with identifier variable1 references database variable2, but the current database is variable3

Cause

The transaction specified does not reference the specified database.

Response

You may be calling a REST service with a transaction and database specified that do not match.

XDMP-INVAUTHATTRIB

Message Text

Invalid authorization attribute: variable1

XDMP-INVAUTHMETH

Message Text

Invalid authorization method: variable1

XDMP-INVBINDING

Message Text

Invalid binding for key 'variable1'

Cause

Bindings for cts:parse must have values that are strings or range index references.

Response

Put appropriate values into the binding map.

XDMP-INVCALLBACK

Message Text

Invalid callback function for 'variable1'

Cause

The key was bound to a callback function which was not valid.

Response

Fix the callback function or the callback bindings.

XDMP-INVCHARCLASS

Message Text

Invalid character class for default-script: variable1

XDMP-INVCLUSTERS

Message Text

The minimum number of clusters cannot be greater than maximum number

XDMP-INVCONFIG

Message Text

Server has invalid config files: variable1

XDMP-INVCOORD

Message Text

Invalid coordinate system variable1

Cause

An invalid coordinate system name was specified.

Response

Correct the coordinate system name.

XDMP-INVDATABASEONLINEEVENT

Message Text

Invalid Database Online event

Cause

An error occurred during execution of the database online trigger event handler. This error most often occurs when the cpf:restart trigger runs under an invalid user id.

During installation, the Content Processing Framework configures the cpf:restart trigger to run as the admin user at the time of installation. If the configured user id is removed, the XDMP-INVDATABASEONLINEEVENT error is logged.

Response

If you suspect the cpf:restart trigger is running under an invalid user id, check and correct the user id in the trgr:database-online-event/trgr:user element. See the Triggers Module of the XQuery API Reference.

XDMP-INVDATAEVENT

Message Text

Invalid trigger data event definition

XDMP-INVDICT

Message Text

Invalid dictionary variable1

XDMP-INVGEOHASH

Message Text

Invalid geohash variable1

Cause

The specified string is not a valid geohash.

Response

Correct your code.

XDMP-INVGEOHASHTYPE

Message Text

variable1 is an invalid geohash type.

Cause

The provided geohash type is invalid.

Response

Correct your code.

XDMP-INVGEOOP

Message Text

Invalid geospatial operation variable1

Cause

The specified geospatial operation is not valid.

Response

Correct your code.

XDMP-INVGZIP

Message Text

Invalid gzip file

XDMP-INVHTTPOPTS

Message Text

HTTP Options not allowed when not loading from an HTTP source

XDMP-INVLOCK

Message Text

Invalid LockDiscovery document: variable1

XDMP-INVMANATTR

Message Text

Invalid manifest attribute: variable1

XDMP-INVMANNOD

Message Text

Invalid manifest node: variable1

XDMP-INVMANNS

Message Text

Invalid manifest namespace: variable1 node has namespace: variable2

XDMP-INVMANVAL

Message Text

Invalid manifest (expect an array of objects): variable1

XDMP-INVMINCLUSTERS

Message Text

The minimum number of clusters cannot be less than 1

XDMP-INVOKEMODULE

Message Text

No module to invoke

XDMP-INVOKEPATH

Message Text

Invalid invoke path: variable1

XDMP-INVOPTIONS

Message Text

Invalid options node

XDMP-INVOPTNAM

Message Text

Invalid option name: variable1

XDMP-INVOPTNOD

Message Text

Invalid options node: variable1

XDMP-INVOPTNS

Message Text

Invalid option namespace: variable1 node has namespace: variable2

XDMP-INVOPTVAL

Message Text

Invalid option value: option 'variable1' has unexpected value 'variable2'

XDMP-INVPAGERANGE

Message Text

Invalid page range: page start variable1 is greater than page end variable2

XDMP-INVPARTITIONQUERY

Message Text

Invalid Partition Query: doc(variable1)

XDMP-INVQUERY

Message Text

Invalid query at 'variable1'

XDMP-INVSCHEME

Message Text

Invalid protocol scheme: variable1

XDMP-INVTASK

Message Text

Invalid task in Task Server

XDMP-INVTERMS

Message Text

Insufficient number of terms from nodes

XDMP-INVTMPL

Message Text

An invalid format was found while parsing a URL Template: variable1

XDMP-INVTRIGGER

Message Text

Invalid trigger definition

XDMP-INVTRIGGERMODULE

Message Text

Invalid trigger module definition

XDMP-INVTXNOPT

Message Text

Invalid transaction option: variable1

XDMP-INVZIP

Message Text

Invalid zip file

XDMP-IOERR

Message Text

I/O error: variable2 variable3: variable1

Cause

A host operating system I/O function returned an unexpected error. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

XDMP-IRINOTQNAME

Message Text

Conversion from an IRI to a QName failed: variable1

Cause

The IRI provided does not contain a fragment identifier, and therefore cannot be turned into a QName.

Response

Use an IRI that can be converted.

XDMP-ISOLATION

Message Text

Isolation option not allowed in this function

XDMP-JEXC

Message Text

variable3

XDMP-JNLFULL

Message Text

Journal full before in-memory stand for forest variable1variable2

XDMP-JNLNOTOPN

Message Text

Journal not open: variable1 (variable2)

Cause

An unexpected error occurred while journaling a transaction. No open journal file could be found. The server will retry and may succeed.

Response

Check for other error messages that may indicate the root cause of the problem. Check that files and directories have permissions allowing MarkLogic access. Check that adequate free space is available on the file system. Check for any antivirus or backup agents interfering with MarkLogic. Check the operating system error log for file system or storage hardware problems. Try increasing the journal size in the database configuration. The journal should be at least the in-memory list size plus the in-memory tree size. Use of range indexes or lexicons further increases the required journal space.

XDMP-JNLTXNFULL

Message Text

The journal has exceeded its limit for in-process transaction records: txn_size=variable1MB, current_size=variable2MB, limit=variable3MB

Cause

A fixed limit of 1/16th of the journal size is a maximum for information about prepared uncommitted transactions. This size limit has been exceeded by the transaction being committed. No more transactions will be allowed to move to being prepared, until the transactions currently using this space have committed or rolled back successfully.

Response

Explicitly commit or rollback XA transactions waiting in a prepared state. Increase your journal size to allow more space for prepared uncommitted transactions.

XDMP-JOININGHOST

Message Text

Suppress warning when joining host

XDMP-JOURNALARCHIVEAUXDB

Message Text

Cannot specify auxiliary databases when enabling journal archiving.

Cause

When backing up with journal archiving, you cannot include auxiliary databases with the backup. This is to prevent journal archive files for auxiliary databases being scattered among several different database backups.

Response

Backup auxiliary databases separately with a full database backup and journal archiving set to true.

XDMP-JOURNALARCHIVEBADFOREST

Message Text

Expecting all forests to be attached and belong to the same database when enabling journal archiving.

Cause

This error occurs when taking a full backup with journal archiving and not having all forests attached or belonging to the same database.

Response

When taking a full backup with journal archiving, make sure all forests are attached and belong to the same database.

XDMP-JOURNALARCHIVEBADLAGLIMIT

Message Text

Expecting the lag limit to be greater than 5 seconds.

Cause

This error occurs when taking a full database backup with journal archiving and the lag limit is set to less than 5 seconds.

Response

When taking a full database backup with journal archiving set the lag limit to 5 seconds or more.

XDMP-JOURNALARCHIVEBADRESTOREFOLDER

Message Text

Expecting full backup folder and journal archive folder to have the same timestamp when restoring. Got variable1 for full backup folder. Got variable2 for journal archive folder.

Cause

You can store your archived journals and full database backup data in separate locations using the admin API. This message occurs when the restoring from separate full database backup and journal archiving locations. It indicates the journal archive folder does not have a timestamp that matches the full backup folder, which means that it is likely that full backup and archived journals are from separate backups.

Response

When restoring from a full database backup, the system will choose the earliest timestamped backup folder from the restore-to-time value. For the journal archiving path, unless the folder timestamp is explicitly specified, the timestamp chosen for the full backup path will be applied to the journal archiving path.In the case of a flash backup, it is possible for the full database backup folder and the journal archive folder to have different timestamps. In this case, you must specifically select the journal archive timestamped folder when restoring with the admin API.Ex:Error if timestamps don't match - xdmp:database-restore(xdmp:forest("Documents"),"/space/backup",(),true(),"/space/ja")Ok if timestamps don't match - xdmp:database-restore(xdmp:forest("Documents"),"/space/backup",(),true(),"/space/ja/20120206-1152597588850")If you are not trying to restore from flash backup, it is likely that the two folders contain unrelated data. Therefore, modify your journal archiving path to find a folder containing journal archiving data with the correct timestamp. If you did not explicitly choose a different journal archiving location, then the journal archives are likely stored in the same path as the full backup.

XDMP-JOURNALCONSUMERSHUTDOWN

Message Text

Journal consumer has been shut down

XDMP-JOURNALOFF

Message Text

Journaling is set to off: variable1

Cause

Certain operations require journaling to be enabled in order to function

Response

Error message indicates a corrupt journal file. Perhaps a journal archive file from an old system was switched in with a journal archive file from a current system. In this case, the internal structure of the header frame may have changed between versions or the checksum formulas may have changed. Best solution is to take another full backup with journal archiving enabled in order to resume journal archiving.

XDMP-JSONCHAR

Message Text

Unexpected character 'variable1' in JSON at line variable2 char variable3

XDMP-JSONCP

Message Text

Unexpected codepoint variable1 in JSON at line variable2 char variable3

XDMP-JSONDOC

Message Text

Document is not JSON

XDMP-JSONDUPKEY

Message Text

Duplicate key variable1 in JSON at line variable2 char variable3

XDMP-JSONEOF

Message Text

Unexpected end of file in JSON at line variable1 char variable2

XDMP-JSONHEX

Message Text

Invalid hex reference variable1 in JSON at line variable2 char variable3

XDMP-JSONNUM

Message Text

Invalid number variable1 in JSON

XDMP-KERBEROS

Message Text

Kerberos Error: variable1

XDMP-KEYGENFAILED

Message Text

Key generation for embedded KMS failed

XDMP-KEYMISMATCH

Message Text

Key mismatch, variable1 variable2

Cause

This error is often a side-effect of a corrupted forest or file system error, such as running out of file descriptors or disk space on the forest's file system. Key file corruption may also occur if the disk becomes temporarily unavailable while the system is trying sync one of the MarkLogic Server memory mapped files to disk.

Response

Correct the underlying file system problem and restore the corrupted forest. For example, restore the system to a healthy state from a good backup, or delete the corrupted stand to get the forest to a healthy state and then reload missing documents.

If you need assistance determining the extent of the corruption and restoring the system to a good state, contact MarkLogic Technical Support.

XDMP-KEYNOTFOUND

Message Text

Key encryption key was not found: variable1, variable2

XDMP-KMSERROR

Message Text

The configured Key Management Service has returned an error

Cause

The external Key Management Service has returned an error

Response

Validate the Key Management Service configuration. see xdmp:keystore-statau()

XDMP-LABELBADARCH

Message Text

Bad architecture in label: variable1 instead of variable2 in variable3

XDMP-LABELBADMAGIC

Message Text

Bad forest label magic number: variable1 instead of variable2

XDMP-LABELBADPLATFORM

Message Text

Bad platform in label: variable1 instead of variable2 in variable3

XDMP-LABELBADWORDSIZE

Message Text

Bad word size: variable1 instead of variable2

XDMP-LABELDNE

Message Text

Forest label does not exist: variable1

XDMP-LANG

Message Text

Unsupported language variable1

XDMP-LANGCODE

Message Text

Language code missing variable1

XDMP-LASTMODIFIED

Message Text

The last-modified property is read-only and cannot be removed

XDMP-LDAP

Message Text

LDAP Error: variable1

XDMP-LDAP-INVALID-CRED

Message Text

LDAP Error: variable1

XDMP-LEGACYMODULESYNTAX

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

NCName required with module declaration

Cause

You have used a "0.9-ml" syntax for declaring a module. Newer syntax requires a prefix to be specified for the module's namespace.

Response

Specify a prefix to be bound to the module's namespace.

XDMP-LEGACYVARSYNTAX

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Use := to initialize module variables: variable1

Cause

You have used the "0.9-ml" syntax for initializing global variables.

Response

Use ":=" rather than "{ ... }".

XDMP-LEVTOOBIG

Message Text

String too large to calculate levenshtein distance: variable1

XDMP-LEXER

Message Text

Lexer error: variable1

Cause

The XQuery lexer has encountered a fatal error.

Response

Usually this indicates an out of memory condition, although there are other exceptional circumstances for this error.

XDMP-LEXINT

W3C XQuery Standard Equivalent: err:FORG0001

Message Text

variable1 is not a valid lexical representation of an unsignedInt

XDMP-LEXNUM

W3C XQuery Standard Equivalent: err:FORG0001

Message Text

variable1 is not a valid lexical representation of a number

XDMP-LEXVAL

Message Text

Invalid lexical value variable1

Cause

A typed value cannot be parsed from text because the text does not fit the lexical rules of the type.

Response

Change the text or the type.

XDMP-LIMITEXCEEDED

Message Text

Value:variable1 exceeded limit:variable2

XDMP-LISTCACHEFULL

Message Text

List cache full on host variable1

Cause

The query results are too large to fit all of the term lists resulting from the index resolution stage into the list tree cache.

Response

Possible solutions include:

Tune the query to select fewer items during index resolution.Reduce the size of your forest data, which will lead to fewer results per query.Ensure appropriate indexes are enabled. For example, enabling positions may improve multi-term and proximity queries.Increase the size of the list cache in the group configuration.

If you increase your list cache size, be careful not to over-tune your system. If you decide to apply this solution, MarkLogic Technical Support can assist you with selecting an appropriate cache size.

The size of all caches, both group and database related, should usually add up to less than half of physical memory.

XDMP-LITERALNOTLEGAL

W3C XQuery Standard Equivalent: err:FOFD1340

W3C XSLT Standard Equivalent: err:XTDE1340

Message Text

Literal in the picture format contains odd number of square brackets.

XDMP-LOCKCONFLICT

Message Text

A conflicting lock exists on this document

XDMP-LOCKDOC

Message Text

Cannot update lock documents

XDMP-LOCKED

Message Text

Document or Directory is locked

XDMP-MAIL

Message Text

Error sending mail: variable1

XDMP-MAIL-INV-MULTIPART

Message Text

Invalid multipart: variable1

Cause

Invalid multipart for JSON email format.

Response

Change the part to be text or JavaScript object.

XDMP-MAIL-INVATTACHMENT

Message Text

Invalid attachment

Cause

Attachment is not encoded text.

Response

Change attachment to encoded text.

XDMP-MAIL-INVBODY

Message Text

Invalid email body: variable1

Cause

Invalid email body for JSON email format.

Response

Change the body to be either text or JavaScript object.

XDMP-MAIL-INVBOUNDARY

Message Text

Invalid multipart boundary: variable1

Cause

Invalid multipart boundary for JSON email format.

Response

Change the boundary to be text.

XDMP-MAIL-INVENCODING

Message Text

Invalid encoding: variable1

Cause

Encoding not supported.

Response

Change encoding to base64 or hex.

XDMP-MAIL-INVHEADER

Message Text

Invalid header: variable1

Cause

Invalid value for rfc822 header.

Response

Change content of the header.

XDMP-MAIL-NO-RECIPIENTS

Message Text

No recipients

Cause

Tried to send mail without any recipients.

Response

Enter one or more recipients and try again.

XDMP-MAINMOD

Message Text

Main module failed to parse

XDMP-MANYFUNCTIONS

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Ambiguous function name, possible functions include: variable1

Cause

Multiple functions match the given function localname.

Response

Fully qualify the function with a prefix or EQName syntax.

XDMP-MANYITEMSEQ

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Sequence containing more than one item

XDMP-MAP

Message Text

Invalid hash table element

XDMP-MAPCYCLE

Message Text

A cycle was detected in the map entry

Cause

A map cannot be member of itself, either directly or indirectly.

Response

Do not add the map as a member of itself.

XDMP-MAPENTRY

Message Text

Invalid hash table entry element

XDMP-MAPPEDFILEERROR

Message Text

Error mapping file: variable1 variable2: variable3

XDMP-MAPPINGOPTVAL

Message Text

Invalid xdmp:mapping option value, must be "true" or "false"

XDMP-MATCHPRIORITYEXPR

Message Text

Invalid match pattern passed to xdmp:match-priority: variable1

XDMP-MATCHZERO

W3C XQuery Standard Equivalent: err:FORX0003

Message Text

Pattern matches zero-length string

XDMP-MAXATOMS

Message Text

Maximum number of atoms exceeded

XDMP-MAXFRAGMENTS

Message Text

Maximum number of fragments exceeded

XDMP-MAXSTRINGS

Message Text

Maximum number of strings exceeded

XDMP-MAXTASKS

Message Text

Task Server exceeded maximum number of tasks: variable1

Cause

The actions of spawn and or cpf has caused the tasks in the task server queue to be greater than the maximum number allowed.

Response

Examine Task Server utilization and consider either increasing the task queue size or throttling back the workload being put on Task Server.

XDMP-MAXTRIGGERDEPTH

Message Text

Trigger or task spawn exceeded maximum depth: variable1

Cause

Recursive trigger execution has exceeded the depth limit set.

Response

This usually indicates an infinite recursion in your triggers. Otherwise the trigger depth limit can be changed.

XDMP-MEMCANCELED

Message Text

Canceled because of memory usage on host variable1, requestMemory=variable2, totalMemory=variable3, memoryLimit=variable4

Cause

The request was cancelled because its memory usage was too high.

Response

Retry the operation.

XDMP-MEMORY

Message Text

Memory exhausted

Cause

Insufficient contiguous memory address space.

Response

A detailed technical note on troubleshooting out-of-memory issues is available from MarkLogic Technical Support. In brief, you may need to:

Change your swap space allocation. A 2:1 ratio between virtual and physical memory is recommended.Tune your MarkLogic Server cache settings.If you run MarkLogic Server on a 32-bit platform, consider moving to a 64-bit platform.If you are running on 32-bit Windows, increase the virtual address space addressable by applications from 2G to 3G by adding the /3G switch to your boot.ini file. Microsoft has a Support note available about this switch.

XDMP-MERGESPACE

Message Text

Not merging due to disk space limitations, need=variable1MB, have=variable2MB

Cause

There was not enough disk space to complete the merge operation.

Response

You need to free space on or add space to the device in which the forest is stored. If your forest is also in the error state (XDMP-FORESTERR), then you can perform the following to get it out of the error state:

Disable automatic merges on the forest.Restart the forest.Delete some documents from the forest.Start a manual merge on the forest.

XDMP-MERGETIMESTAMPMISSING

Message Text

Merge timestamp must be set to non-zero value when restoring with journal archiving and restore-to-time is zero

XDMP-MERGETIMESTAMPTOOLATE

Message Text

Merge timestamp must be set to a time less than the restore-to-time when restoring with journal archiving.

XDMP-MINVERSIONREQUIRED

Message Text

variable1 cannot be used until the cluster is upgraded to effective version variable2.

XDMP-MISSING-KEY

Message Text

Missing one or more required keys/fields variable1

Cause

A required key was missing from the object

Response

The object is invalid. Add the missing key.

XDMP-MISSINGCONTEXT

W3C XQuery Standard Equivalent: err:XPDY0002

Message Text

Missing context item

XDMP-MISSINGFILE

Message Text

Missing file variable1

XDMP-MISSINGFILES

Message Text

Missing files variable1

Cause

The named files should be present in your stand, but are missing. This may indicate a corrupted stand.

Response

Restore the corrupted stand from backup or otherwise recreate it.

MarkLogic Technical Support can help you determine probable cause. Save a copy of the corrupted stand and related log files to assist Support in debugging your issue.

XDMP-MISSINGIMPORTATTR

Message Text

No xs:import for namespace: variable1 on attribute 'variable2'

XDMP-MISSINGIMPORTELT

Message Text

No xs:import for namespace: variable1 on element 'variable2'

XDMP-MISSINGSTAND

Message Text

Missing stand in forest variable1: variable2

XDMP-MISSINGSTANDS

Message Text

Missing stands in forest variable1: variable2

XDMP-MIXED

Message Text

Mixed variable1

XDMP-MIXEDPATH

W3C XQuery Standard Equivalent: err:XPTY0018

Message Text

Path expressions cannot return a mix of nodes and atomic values

XDMP-MODNOTFOUND

W3C XQuery Standard Equivalent: err:XQST0059

Message Text

Module variable1 not found

Cause

The module document being requested does not exist or the user does not have execute permissions on the module.

Response

Make sure the module exists and grants execute permissions if it is stored in a database.

XDMP-MODNOTTEXT

Message Text

Module variable1 is not a text document

XDMP-MORETHANONEITEM

Message Text

fn:zero-or-one called with a sequence containing more than one item

XDMP-MULTIDBSTMT

Message Text

Cannot process different-database requests with same-statement isolation

XDMP-MULTIMATCH

Message Text

Multiple matches for variable1 at variable2 and variable3

XDMP-MULTIPART-BOUNDARY

Message Text

Ending of the boundary is incorrect

Cause

Occurs when a part is not corrected ended.

Response

Fix the application.

XDMP-MULTIPART-DONE

Message Text

All parts are already processed

Cause

Occurs when trying to stream the next part body after all parts are processed.

Response

Fix the code.

XDMP-MULTIPART-MODE

Message Text

The current HTTP request is in multipart mode

Cause

Occurs when an API that is only supposed to work for an HTTP request in non-multipart mode is called for multipart mode.

Response

Fix the code.

XDMP-MULTIPART-READ-BODY-FIRST

Message Text

Body of the current part is not read yet

Cause

Occurs if try to read the headers of the next part when the body of the current part is not read yet.

Response

Fix the code.

XDMP-MULTIPART-READ-HEADERS-FIRST

Message Text

Headers of the current part is not read yet

Cause

Occurs if try to read the body of the current part when the headers are not read yet.

Response

Fix the code.

XDMP-MULTIPARTCOUNT

Message Text

Invalid multipart encoding, mismatched counts: variable2 parts, but variable1 nodes

XDMP-MULTIROOT

Message Text

Document nodes cannot have multiple roots

XDMP-MULTISTMTVALUE

Message Text

Cannot evaluate multiple statements

XDMP-MUSTHAVEUPDATE

Message Text

Document must have at least one update permission. Assigned permissions: variable1

Cause

When creating a document as a user without the admin role, the document must include at least one update permission. You can specify permissions explicitly in your update built-in call (for example, xdmp:document-insert), or with the set of default permissions for the user performing the update operation.

Response

When loading a document, ensure the named role has update permissions. Documents created by non-admin users must be created with at least one update permission. If the document has no permissions, then only users with the admin role will be able to update or delete the document.

You can create the permissions in several ways, including:

Passing them as option parameters to functions such as xdmp:document-load and xdmp:document-insert.Setting default permissions on a user or role.Using the permissions APIs, such as xdmp:document-add-permissions or xdmp:document-set-permissions.

For more information, see the Understanding and Using Security Guide or the Application Developer's Guide.

XDMP-MUSTUNDERSTAND

Message Text

Do not understand element marked mustUnderstand

XDMP-NANEXPR

W3C XQuery Standard Equivalent: err:FOAR0002

Message Text

Expression contains a NaN (not-a-number)

XDMP-NCNAME

Message Text

Invalid NCName "variable1"

XDMP-NESTEDMULTI

Message Text

Cannot create a nested multi-statement transaction inside a multi-statement transaction.

Cause

An eval or invoke with transaction-mode update was attempted in a multi-statement transaction.

Response

Use transaction-mode update-auto-commit instead.

XDMP-NEWSTAMP

Message Text

Timestamp too new for forest variable1 (variable2)

Cause

When a transaction commits, it advances the commit timestamp. After the transaction commits and advances the commit timestamp, however, any queries running at the advanced commit timestamp wait for all transactions with earlier timestamps to commit, during which time they will get this exception.

Response

XDMP-NEWSTAMP is a retryable exception, so retrying the query is appropriate after this exception. You can retry after the App Server request timeout is reached (the default is 30 seconds) until the Group retry timeout is reached (the default is 180 seconds). If you have an XCC application that uses DocInsertStream, you should automatically handle and retry the insert; that is, if you get a retryable exception when using DocInsertStream, you should try the operation again, not treat the exception as an error.

XDMP-NOAGGREGATE

Message Text

The aggregate does not exist: variable1:variable2, host: variable3

Cause

The specified aggregate function cannot be found.

Response

Use an aggregate function that exists.

XDMP-NOARCHIVEDJOURNALS

Message Text

Canceled restore. Forest variable1 did not have archived journals.

Cause

Error occurs when restoring to a point in time from a full database backup with journal archiving. At least one forest does not have archived journals in its Journals directory.

Response

When restoring to a point in time from a full database backup with journal archiving:1) All forests must have been backed up with journal archiving enabled.2) The Journals directory must contain archived journals.

XDMP-NOARCINTERSECT

Message Text

The two arcs do not intersect

XDMP-NOBASEURI

W3C XQuery Standard Equivalent: err:FONS0005

Message Text

Base uri undefined in the static context

XDMP-NOBEARING

Message Text

Cannot compute bearing from point to itself

XDMP-NOBOOTSTRAPHOST

Message Text

No bootstrap host in cluster variable1

Cause

There is no bootstrap host in this cluster.

Response

Add a bootstrap host to this cluster.

XDMP-NOCLUSTER

Message Text

No cluster with identifier variable1 with hostname variable2

Cause

A cluster with the identifier is not couple with this cluster.

Response

Examine the foreing cluster trying to connect to this cluster

XDMP-NOCONTEXTDOC

Message Text

No context document

XDMP-NOCRED

Message Text

Credential does not exist: variable1

XDMP-NODB

Message Text

No database with identifier variable1

XDMP-NODBREPFORESTMAP

Message Text

Database does not have a foreign forest map: variable1

Cause

This occurs during database replication and is normally transient

Response

Normally resolves on its own

XDMP-NODEFOL

Message Text

variable1 nodes cannot be followed by variable2 nodes

XDMP-NODEKIND

Message Text

Invalid node kind variable1, expected variable2

XDMP-NODEMATCHESEXPR

Message Text

Invalid match pattern passed to xdmp:node-matches

XDMP-NODEPREC

Message Text

variable1 nodes cannot be preceded by variable2 nodes

XDMP-NODEREP

Message Text

variable1 nodes cannot be replaced with variable2 nodes

XDMP-NODICTIONARY

Message Text

The stemming dictionary could not be loaded: variable1 dictionary at variable2 not loaded

Cause

The specified stemming dictionary cannot found or there was some problem with it.

Response

Check your language configuration.

XDMP-NODIR

Message Text

No such directory: variable1

Cause

Directory does not exist.

Response

Check directory and try again.

XDMP-NODOCROOT

W3C XQuery Standard Equivalent: err:FODC0001

Message Text

The node is in a tree whose root is not a document node

Cause

The node is in a tree whose root is not a document node.

Response

Make sure node is in a tree whose root is a document node.

XDMP-NODOMESTICFOREST

Message Text

No domestic forest: variable1

Cause

This occurs during database replication, either as a transient problem or due to incomplete matching of foreign forests to domestic forests

Response

Configure database replication to match all database forests

XDMP-NOELEMNODE

Message Text

No element node: variable1

XDMP-NOEMPTYPARTITIONFORUPDATE

Message Text

No forests with empty partition number allow updates

XDMP-NOENDDOCUMENT

Message Text

There is still a started document.

XDMP-NOENDELEMENT

Message Text

There is still a started element.

XDMP-NOEXECUTE

Message Text

Document is not of executable mimetype. URI: variable1

XDMP-NOFIELD

Message Text

Field not defined: variable1

Cause

You ran a field query with an undefined field.

Response

Try the query again after defining the field and appropriate indexes.

XDMP-NOFOREST

Message Text

No forest with identifier variable1

XDMP-NOFORESTS

Message Text

Database variable1 contains no forests

Cause

You tried to upload to a database that is not attached to a forest.

Response

Add at least one forest to the database and try again.

XDMP-NOGROUP

Message Text

No group with identifier variable1

XDMP-NOGROUPCONFIG

Message Text

No group configuration

XDMP-NOHOST

Message Text

No host with identifier variable1

XDMP-NOJOB

Message Text

No job with identifier variable1

XDMP-NOJOURNAL

Message Text

No journal for recovery token variable1

Cause

MarkLogic Server cannot find the journal files for a forest.

This could be caused by a bad disk drive, by two hosts attempting to mount the same forest, or by other disk-related corruption.

Response

The following procedures may resolve the problem. Contact MarkLogic Technical Support for assistance, if needed.

Restore from backup.Shut down MarkLogic Server, delete the journals, delete the label file in the forest directory (not in the stand directories), and restart MarkLogic Server.

XDMP-NOLABELCLASS

Message Text

Invalid classification label value: missing class name

XDMP-NOLEXER

Message Text

The lexer does not exist: variable1:variable2, host: variable3

Cause

The specified lexer function cannot be found.

Response

Use a lexer function that exists.

XDMP-NOLIBRARY

Message Text

The shared library cannot be loaded: variable1, host: variable2

Cause

The specified shared library cannot be loaded.

Response

Check spelling. Read the extended error message for further details of the error.

XDMP-NOLOCK

Message Text

Lock on thie document or directory no longer exists

XDMP-NOMATCH

Message Text

No matches for variable1 in variable2

XDMP-NOMERGE

Message Text

No merge with identifier variable1

XDMP-NOMODULES

W3C XQuery Standard Equivalent: err:XQST0016

Message Text

The modules feature has been disabled

XDMP-NONAMESPACEBIND

W3C XQuery Standard Equivalent: err:FONS0004

Message Text

No namespace binding for prefix

XDMP-NONMIXEDCOMPLEXCONT

Message Text

Node has complex type with non-mixed complex content

Cause

An attempt was made to atomize an XML element node that cannot be atomized. The in-scope XML schema specifies that the element node has non-mixed complex content. Some code is attempting to convert the node to an atomic value. Element nodes with non-mixed complex content cannot be converted to atomic values.

Response

If the schema is correct, fix the code so it does not attempt to atomize the element node. The code should not explicitly atomize the node by calling fn:data on it. The code should not implicitly atomize the node by passing it as a parameter to a function expecting an atomic value. If the code is correct, fix the schema so that the complex type for the element node is mixed.

XDMP-NONODES

Message Text

Insufficient number of nodes

XDMP-NONTRAILINGWILDCARD

Message Text

Wildcards can only be at the end of the node name

XDMP-NONVAR

Message Text

Not a variable

XDMP-NOPARAM

Message Text

Bad parameter position, function has variable1 parameters, but got variable2

Cause

The parameter position provided was too high or too low for the function.

Response

Correct the position.

XDMP-NOPARENTNODE

Message Text

No parent node

XDMP-NOPARTITIONFORUPDATE

Message Text

No forests with partition number variable1 allow updates

XDMP-NOPARTITIONKEY

Message Text

Database variable1 has no range assignment policy partition key

XDMP-NOPROGRAM

Message Text

Server unable to build program from request

Cause

The requested XQuery document does not exist or the user does not have execute permissions on the module.

Response

Make sure the module exists. If the module is stored in a modules database, make sure the module execute permissions.

XDMP-NOPROHIBIT

W3C XQuery Standard Equivalent: err:XQST0128

Message Text

The specified feature cannot be disabled: variable1

XDMP-NOQRY

Message Text

No valid query could be created for 'variable1'

Cause

The key was bound to an index, field, or callback, which could not produce a valid query in this context. Either the bindings have a problem, or the key is being misused.

Response

Fix the bindings or the query, as appropriate.

XDMP-NOQUORUM

Message Text

No quorum: variable1

Cause

Unable to communicate with at least 50% of hosts in cluster

XDMP-NOREQUEST

Message Text

No request with identifier variable1

XDMP-NOREQUIRE

W3C XQuery Standard Equivalent: err:XQST0120

Message Text

The specified feature is not supported: variable1

XDMP-NOROOT

Message Text

Database does not have root directory

XDMP-NOSCHEMAIMPORT

W3C XQuery Standard Equivalent: err:XQST0009

Message Text

The schema import feature has been disabled

XDMP-NOSCHEMAVALIDATION

W3C XQuery Standard Equivalent: err:XQST0075

Message Text

The schema validation feature has been disabled

XDMP-NOSEARCHTERM

Message Text

No searchable term found in the search pattern: variable1

XDMP-NOSERVER

Message Text

No server with identifier variable1

XDMP-NOSTEMMER

Message Text

The stemmer does not exist: variable1:variable2, host: variable3

Cause

The specified stemmer function cannot be found.

Response

Use a stemmer function that exists.

XDMP-NOSUCHCLUSTER

Message Text

No such cluster variable1

Cause

The cluster does not exist or the cluster is not coupled with the local cluster.

Response

Make sure the cluster id is correct and the cluster is coupled with the local cluster.

XDMP-NOSUCHCONFIGURATION

Message Text

No such configuration variable1

XDMP-NOSUCHDB

Message Text

No such database variable1

Cause

The database you are trying to operate on does not exist (or you misspelled the name of an existing database).

Response

Either create a new database with this name and try again, or use a different, existing, database.

XDMP-NOSUCHDICT

Message Text

No such dictionary variable1

XDMP-NOSUCHFOREST

Message Text

No such forest variable1

Cause

Called xdmp:forest with an invalid forest name argument.

Response

Check the spelling of the forest name passed to xdmp:forest. Check that the forest has been created.

XDMP-NOSUCHGROUP

Message Text

No such group variable1

Cause

Called xdmp:group with an invalid group name.

Response

Check spelling and existence of group name passed to xdmp:group.

XDMP-NOSUCHHOST

Message Text

No such host variable1

Cause

Called xdmp:host with an invalid host name.

Response

Check the spelling of the host name. Check that you defined the host.

XDMP-NOSUCHSERVER

Message Text

No such server variable1

Cause

Called xdmp:server with an invalid server name.

Response

Check the spelling of the server name passed to xdmp:server . Check that the server was created.

XDMP-NOT-MULTIPART-MODE

Message Text

The current HTTP request is not in multipart mode

Cause

Occurs when an API that is only supposed to work for an HTTP request in multipart mode is called for none-multipart mode.

Response

Fix the code.

XDMP-NOTANODE

W3C XQuery Standard Equivalent: err:XPTY0019

Message Text

variable1 is not a node

Cause

You are trying to use data that is not a node when a node is required.

Response

Rewrite your query so it submits a node.

XDMP-NOTASKSERVER

Message Text

This host's group does not contain a configured Task Server

Cause

The task server does not exist or is improperly configured for this group.

Response

Use the Admin Interface to check the task server configuration for this group.

XDMP-NOTATOMIC

W3C XQuery Standard Equivalent: err:XPST0051

Message Text

Invalid cast to non-atomic type variable1

XDMP-NOTCURRENT

Message Text

Transaction with Xid variable1 is not the current transaction

XDMP-NOTFILE

Message Text

The path passed to xdmp:logfile-scan() is not a file.: variable1

XDMP-NOTFOUNDCHARCLASS

Message Text

Character class not found: no character class for 'variable1'

XDMP-NOTFUNC

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Not a singleton function value

Cause

A dynamic function call can only be made against a sequence consisting of a single function item.

Response

Use the head function to choose the first function in the sequence, or iterate over all the functions using for or !.

XDMP-NOTIDY

Message Text

No tidy in this MarkLogic Server instance

XDMP-NOTLOCKED

Message Text

Document not locked

XDMP-NOTMPENVVAR

Message Text

No TEMP or TMP environment variable

XDMP-NOTONEITEM

W3C XQuery Standard Equivalent: err:FORG0005

Message Text

fn:exactly-one called with a sequence containing zero or more than one item

XDMP-NOTPLUGIN

Message Text

The shared library does not contain a "marklogicPlugin" function: variable1, host: variable2

Cause

The "marklogicPlugin" registration function cannot be found in the shared library.

Response

Implement the registration function in shared libraries designed to be used as MarkLogic native plugins.

XDMP-NOTPREPARED

Message Text

Transaction with identifier variable1 is not a prepared XA transaction

XDMP-NOTQUERY

Message Text

Element variable1 is not a query (expecting a cts:query)

XDMP-NOTRANGEPOLICY

Message Text

This API works only with the range assignment policy.

XDMP-NOTRANS

Message Text

No transaction

XDMP-NOTREMEMBERED

Message Text

Transaction with identifier variable1 is not a remembered completed XA transaction

XDMP-NOTSIMPLE

Message Text

Node does not have simple content: variable1

XDMP-NOTSUPPORTEDKMS

Message Text

variable1 not supported for variable2

XDMP-NOTXN

Message Text

No transaction with identifier variable1

Cause

No transaction with the given ID exists on this host.

Response

You may be connecting to a different host than the one where the transaction was created, as transactions are host specific. It may be that the transaction has already been committed or rolled back.

XDMP-NOUSER

Message Text

A user must be authenticated to perform this task

XDMP-NOZIP

Message Text

No zip support in this MarkLogic Server instance

XDMP-NSLITERAL

W3C XQuery Standard Equivalent: err:XPST0022

Message Text

Namespace declaration attribute variable1 must be a URILiteral

Cause

A namespace declaration attribute (for example, xmlns) must have a value that is a URI Literal value.

Response

If you want to compute the URI Literal value, use a computed element constructor or the xdmp:with-namespaces function to compute the value.

XDMP-NSSENSITIVE

W3C XQuery Standard Equivalent: err:XPTY0117

Message Text

Namespace sensitive cast: variable1 cast as variable2

Cause

An expression or declaration attempted to cast a node to a namespace sensitive type like xs:QName and types derived from xs:NOTATION.

Response

Use fn:data() or fn:resolve-QName() instead.

XDMP-OBJCONSTRUCTCHILDSEQ

Message Text

Object nodes cannot have sequence children: variable1

XDMP-OFFLINE

Message Text

Forest variable1 is offline

XDMP-OLDCONFIG

Message Text

Config files are old, variable1 has newer config files

XDMP-OLDJOURNAL

Message Text

Backup data directory contains an incompatible journal: variable1

XDMP-OLDJOURNALARCHIVE

Message Text

The journal archive is too old to be updated from the active journals: variable1

Cause

There are 2 active journal files. When one fills up, it begins to overwrite the other. When a system fails, the archived journal may not be caught up with the active journal. When resuming journal archiving, the archived journals at startup rely on streaming frames from the active journal to get caught up with any that it missed. When the active journal overwrites itself, it may overwrite frames that the archived journal needs. If this is the case, it is not possible for the archived journal to get caught up with the active journal, and journal archiving must stop.

Response

You must do a new full backup with journal archiving. This error message is deprecated since the active journal now waits to roll over if it is going to overwrite frames needed by the archived journal. However, this message is still included for completeness.

XDMP-OLDKMS

Message Text

variable1 has a more recent version of the embedded KMS

Response

Retry the operation after the embedded KMS has completed synchronizing. If hosts are unavailable wait for all to be online before retrying.

XDMP-OLDSTAMP

Message Text

Timestamp too old for forest variable1 (variable2)

Cause

A timestamp less than the oldest timestamp preserved in the database was specified for a point-in-time query or rollback.

Note: If the merge timestamp is set to the default of 0 and the database has completed all merges since the last update or delete, then query statements that specify any timestamp older than the current system timestamp will throw the XDMP-OLDSTAMP exception. The error occurs because a merge timestamp value of 0 specifies that no obsolete fragments are to be retained.

Response

Modify the query or rollback operation timestamp. For example, change the timestamp parameter passed to xdmp:eval, xdmp:invoke, or xdmp:spawn.

XDMP-ONEBINARYNODE

Message Text

Documents can only have one binary node

Cause

The document already contains a binary node

Response

Check why a second binary node is being added into the document or use the existing binary node.

XDMP-OPNURL

Message Text

Open URL error: variable1: variable2

XDMP-OPSDIR-INTERR

Message Text

An internal error was encountered communicating with Ops Director: variable1

XDMP-OPSDIR-INTERR2

Message Text

An internal error was encountered communicating with Ops Director: variable1 variable2 variable3 variable4 variable5

XDMP-OPSDIR-INVENDP

Message Text

No valid endpoint was found to connect to Ops Director: variable1

XDMP-OPSDIR-INVMSG

Message Text

Not a valid JSON structure in: variable1

XDMP-OPSDIR-INVREQ

Message Text

An invalid request error was returned as a response to communicating with Ops Director: method variable1, variable2

XDMP-OPSDIR-INVRESP

Message Text

The response received from Ops Director is invalid: variable1

XDMP-OPSDIR-RETRY

Message Text

The maximum number of retries exceeded while connecting to Ops Director: variable1

XDMP-OPSDIR-SEC

Message Text

An attempt to connect to Ops Director using https requires SSL: variable1, $2

XDMP-OPTATTNOTNAME

Message Text

Tidy option nodes can only have name attributes: variable1

XDMP-OPTION

Message Text

Invalid option variable1

XDMP-OPTNOSPACES

Message Text

This option value cannot contain spaces: option 'variable1' cannot have spaces in 'variable2'.

XDMP-OPTPRFX

W3C XQuery Standard Equivalent: err:XPST0081

Message Text

Prefix required on option name

XDMP-ORDERBYVAL

Message Text

Invalid 'order by' value variable1

XDMP-ORDERCLAUSEELEM

Message Text

Ordering clause element contains unknown child: variable1

XDMP-ORDERCLAUSENODE

Message Text

Ordering clause node variable1 contains unknown child

XDMP-ORDERCLAUSETEXT

Message Text

Ordering clause element variable1 contains misplaced text

XDMP-ORDERSPECELEM

Message Text

Order specification element contains unknown child: variable1

XDMP-ORDERSPECNODE

Message Text

Order specification node variable1 contains unknown child

XDMP-ORDERSPECTEXT

Message Text

Order specification element variable1 contains misplaced text

XDMP-OUTOFORDER

Message Text

write variable1:Out of order, variable2

XDMP-OUTPUTOPTVAL

Message Text

Invalid xdmp:output option parameter

XDMP-OWNTXN

Message Text

Operation not allowed on the currently executing transaction with identifier variable1

XDMP-PARENTDIR

Message Text

Parent directory variable1 is missing for creation of child

XDMP-PARENTLINK

Message Text

Invalid parent link node doc("variable1")//variable2

XDMP-PARSE

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Parse error

XDMP-PARSEBACKUP

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Syntax error: cannot back up

XDMP-PARTICIPANTNOLOCK

Message Text

Some write locks are not held for session variable1

XDMP-PATHGIDXAMBIGUOUS

Message Text

Ambiguous geospatial variable1 path index for variable2 variable3

Cause

The options provided are not sufficient to uniquely identify a path geospatial point index.

Response

Specify type, coordinate-system, and/or precision options to uniquely identify a path geospatial point index.

XDMP-PATHGIDXNOTCOLL

Message Text

Collations are irrelevant to the geospatial variable1 path index for variable2 variable3

Cause

The options to the query include a collation, but the geospatial point index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-PATHGIDXNOTFOUND

Message Text

No geospatial variable1 path index for variable2 variable3 variable4

Cause

The query requires a geospatial point index that does not exist.

Response

Make sure the geospatial point index exists and that it uses the coordinate system specified in the query. If the geospatial point index was added recently, make sure reindexing is enabled and has completed.

XDMP-PATHGIDXNOTPOSN

Message Text

Positions are not enabled on the geospatial variable1 path index for variable2 variable3

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the geospatial point index.

Response

Either enable positions on the geospatial point index or do not specify "ordered" or "proximity" options.

XDMP-PATHLXCNNOTFOUND

Message Text

No path word lexicon for variable1 variable2

Cause

The query requires a lexicon that does not exist.

Response

Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.

XDMP-PATHNSATTR

Message Text

Attributes not allowed on element variable1

XDMP-PATHNSATTRVAL

Message Text

Path-namespaces attribute contains an invalid value: variable1

XDMP-PATHNSELEM

Message Text

Path-namespaces element contains unknown child: variable1

XDMP-PATHNSNODE

Message Text

Path-namespaces element variable1 contains unknown child

XDMP-PATHNSTEXT

Message Text

Path-namespaces element variable1 contains misplaced text

XDMP-PATHNSVAL

Message Text

Path-namespaces element contains an invalid value: variable1

XDMP-PATHRIDXAMBIGUOUS

Message Text

Ambiguous variable1 path range index for variable2 variable3

Cause

The options provided are not sufficient to uniquely identify a path range index.

Response

Specify type, collation, coordinate-system, and/or precision options to uniquely identify a path range index.

XDMP-PATHRIDXNOTCOLL

Message Text

Collations are irrelevant to the variable1 path range index for variable2 variable3

Cause

The options to the query include a collation, but the range index is not a string data-type.

Response

Do not specify a collation in the query's options.

XDMP-PATHRIDXNOTCOORD

Message Text

Coordinate systems are irrelevant to the variable1 path range index for variable2 variable3

Cause

The options to the query include a coordinate system, but the range index is not a geospatial data type.

Response

Do not specify a coordinate system in the query's options.

XDMP-PATHRIDXNOTFOUND

Message Text

No variable1 path range index for variable2 variable3 variable4

Cause

The query requires a range index that does not exist.

Response

Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.

XDMP-PATHRIDXNOTPOSN

Message Text

Positions are not enabled on the variable1 path range index for variable2 variable3

Cause

User has specified "ordered" or "proximity" options on a query or lexicon function when positions are not enabled on the range index.

Response

Either enable positions on the range index or do not specify "ordered" or "proximity" options.

XDMP-PATTERNVALUEMISMATCH

Message Text

Given value doesn't match with the specified pattern for parsing dateTime string.

XDMP-PICHARS

W3C XQuery Standard Equivalent: err:XQDY0026

Message Text

XML processing instructions cannot contain '?>'

XDMP-PICTUREAPPLY

Message Text

Illegal character in the picture format

XDMP-PLACEKEYSLOCKING

Message Text

Fast locking cannot be used with place keys.

XDMP-POS

Message Text

Invalid position

XDMP-PRERELEXP

Message Text

This pre-release version of MarkLogic Server has expired

XDMP-PREVDL

Message Text

prevent-deadlocks option not allowed in this function

XDMP-PREVENTDEADLOCKS

Message Text

Processing an update from an update with different-transaction isolation could deadlock

XDMP-PRGPRFX

Message Text

Prefix required on pragma name

XDMP-PROLOGORDER

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Prolog options in the wrong order

XDMP-PROPSNODE

Message Text

Top-level property element cannot be deleted or replaced

XDMP-PROTECTEDQUERY

Message Text

Protected query element not indexed

Cause

Protected query element not indexed

Response

Check element level protection on the query and try again.

XDMP-PROTECTEDTRIPLE

Message Text

Protected triple element not indexed

Cause

Protected triple element not indexed

Response

Check element level protection on the triple and try again.

XDMP-QNAME

Message Text

Invalid QName "variable1"

XDMP-QNAMEKEYFORM

Message Text

Invalid lexical form for QName key

XDMP-QNAMELEXFORM

Message Text

Invalid lexical form for QName

XDMP-QNAMELIT

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

A non-QName value must be a string literal to be cast to a QName

XDMP-QNMURI

Message Text

QName URI is not empty variable1

XDMP-QRYTOODEEP

Message Text

Query has too many nesting levels

XDMP-QRYUTF8SEQ

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Invalid UTF-8 escape sequence -- query is not UTF-8 encoded variable1

Cause

A bad UTF-8 byte code sequence was found in the XQuery.

Response

Encode your query in UTF-8 correctly.

XDMP-QRYXMLCHAR

Message Text

Invalid XML character -- query contains non-XML character

XDMP-QUERYATTR

Message Text

Attributes not allowed on element variable1

XDMP-QUERYATTRVAL

Message Text

Query attribute contains an invalid value: variable1

XDMP-QUERYELEM

Message Text

Query element contains unknown child: variable1

XDMP-QUERYNOCOORD

Message Text

Query requires a coordinate system: variable1

XDMP-QUERYNODE

Message Text

Query element variable1 contains unknown child

XDMP-QUERYNOGEOOP

Message Text

Query requires a geospatial operation: variable1

XDMP-QUERYNOVALS

Message Text

The range query must have one or more cts:values: variable1

XDMP-QUERYTEXT

Message Text

Query element variable1 contains misplaced text

XDMP-QUERYVAL

Message Text

Query element contains an invalid value: variable1

XDMP-RANGEINDEX

Message Text

Range index error: variable1 variable2: exception_stack

Cause

User inserted a document where certain data doesn't match the data-type of the corresponding range index. Also user didn't set the invalid-values option in the range index configuration.

Response

Either change the data-type of the index or data. If both of those cannot be changed and you still want to insert the data, set the invalid-values option in the index configuration.

XDMP-RANGEINDEXELEM

Message Text

Range index element contains unknown child: variable1

XDMP-RANGEINDEXNAN

Message Text

Range indexes cannot store NaNs

XDMP-RANGEINDEXNODE

Message Text

Range index element variable1 contains unknown child

XDMP-RANGEINDEXTEXT

Message Text

Range index element variable1 contains misplaced text

XDMP-RANGEINDEXTYP

Message Text

Unsupported range index type: variable1

XDMP-RANGEINDEXVAL

Message Text

Range index element contains an invalid value: variable1

XDMP-RANGEPARTIALOVERLAP

Message Text

Ranges partially overlap: variable1 and variable2

Cause

The two ranges partially overlap.

Response

Check your configuration.

XDMP-READ

Message Text

variable1:Invalid read, variable2

Cause

An inconsistency was detected while reading a memory-mapped index file. Details about the inconsistency are included in the error report. A memory-mapped index file may be corrupt.

Response

Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear an incosistency in memory. Merging on the affected forest may clear an inconsistency on disk. Reindexing the affected forest may clear an inconsistency on disk.

XDMP-READCONFIG

Message Text

Error reading configuration file: variable1

XDMP-READFILE

Message Text

ReadFile variable1: variable2

Cause

The server encountered a problem that prevented reading a file.

Response

Resolve the problem with the file. If the file is not in UTF-8 and you are using xdmp:filesystem-file, try xdmp:document-get, which has options for converting from other character encodings.

XDMP-READONLY

Message Text

Forest variable1 can only perform reads

XDMP-READONLY-COMMIT

Message Text

Forest %1 is read-only or flash-backup when %2 committing transaction %3

XDMP-READONLYLABEL

Message Text

Forest label is read only: variable1

XDMP-REBALANCE

Message Text

Error rebalancing variable1: exception_stack

XDMP-RECENTHANG

Message Text

Host hung recently

Cause

The host was probably hung recently.

Response

The system will get back to normal shortly.

XDMP-RECOVERY

Message Text

Recovery error on forest variable1 after variable2 redo records -- variable3 exception_stack

XDMP-REDATTRDECL

Message Text

Redefined element declaration: variable1

XDMP-REDATTRGROUP

Message Text

Redefined attribute group: variable1

XDMP-REDBUILTIN

W3C XQuery Standard Equivalent: err:XQST0045

Message Text

Redefined builtin variable1

XDMP-REDCOMPLEXTYPE

Message Text

Redefined complex type: variable1

XDMP-REDCONSTR

W3C XQuery Standard Equivalent: err:XQST0045

Message Text

Redefined constructor variable1

XDMP-REDDEFELMNS

W3C XQuery Standard Equivalent: err:XQST0066

Message Text

Redefined default element namespace

XDMP-REDDEFFUNNS

W3C XQuery Standard Equivalent: err:XQST0066

Message Text

Redefined default function namespace

XDMP-REDELEMDECL

Message Text

Redefined element declaration: variable1

XDMP-REDFUN

W3C XQuery Standard Equivalent: err:XQST0034

Message Text

Redefined function variable1

XDMP-REDGROUP

Message Text

Redefined named model group: variable1

XDMP-REDMOD

W3C XQuery Standard Equivalent: err:XQST0047

Message Text

Redefined module variable1

XDMP-REDPRFX

W3C XQuery Standard Equivalent: err:XQST0033

Message Text

Redefined prefix variable1

XDMP-REDRESPRFX

W3C XQuery Standard Equivalent: err:XQST0070

Message Text

Redefined reserved prefix variable1

XDMP-REDRESURI

W3C XQuery Standard Equivalent: err:XQST0070

Message Text

Redefined reserved URI variable1

XDMP-REDSCHM

W3C XQuery Standard Equivalent: err:XQST0058

Message Text

Redefined schema variable1

XDMP-REDSIMPLETYPE

Message Text

Redefined simple type: variable1

XDMP-REDVAR

W3C XQuery Standard Equivalent: err:XQST0039

W3C XSLT Standard Equivalent: err:XTSE0670

Message Text

Redefined variable variable1

XDMP-REDVAR2

W3C XQuery Standard Equivalent: err:XQST0039

W3C XSLT Standard Equivalent: err:XTSE0580

Message Text

Redefined variable variable1

XDMP-REDVAR3

W3C XQuery Standard Equivalent: err:XQST0039

W3C XSLT Standard Equivalent: err:XTSE0630

Message Text

Redefined variable variable1

XDMP-REFANDNAMEATTR

Message Text

Cannot have both @ref and @name on xs:attribute

XDMP-REFANDNAMEELT

Message Text

Cannot have both @ref and @name on xs:element

XDMP-REFERENCE-NOCOL

Message Text

Collation is not specified for the cts reference.

Cause

No "collation" option is passed into the cts reference call.

Response

Correct the code.

XDMP-REFERENCE-NOCOORD

Message Text

Coordinate system is not specified for the cts reference.

Cause

No "coordinate-system" option is passed into the cts reference call.

Response

Correct the code.

XDMP-REFERENCE-NOPATHEXPR

Message Text

Path expression is not specified for the cts path reference.

Cause

No path expression argument is passed into the cts path reference call.

Response

Correct the code.

XDMP-REFERENCE-NOTYPE

Message Text

Scalar type is not specified for the cts reference.

Cause

No "type" option is passed into the cts reference call.

Response

Correct the code.

XDMP-REFRAGMENT

Message Text

Error refragmenting variable1: exception_stack

XDMP-REGEX

W3C XQuery Standard Equivalent: err:FORX0002

Message Text

Invalid regular expression

XDMP-REGEXFLAGS

W3C XQuery Standard Equivalent: err:FORX0001

Message Text

Invalid regular expression flags

XDMP-REGFLT

Message Text

Registered queries require the "unfiltered" option

XDMP-REINDEX

Message Text

Error reindexing variable1: exception_stack

XDMP-RELPATH

Message Text

Relative pathname: variable1

XDMP-RELURIBASEARG

Message Text

Relative URI base argument to resolve-uri

XDMP-REMOTEHOST

Message Text

Host variable1(variable2) is remote to host variable3(variable4)

XDMP-REPLNOTALLOWED

Message Text

Replication is currently not allowed: variable1

XDMP-REQUESTBLACKOUT

Message Text

Requests are currently forbidden

XDMP-REQUESTLIMIT

Message Text

Concurrent request limit for user has been reached

XDMP-REQUIREALL

W3C XQuery Standard Equivalent: err:XQST0126

Message Text

The all-extensions feature is not allowed in a require-feature option: variable1

XDMP-REQUTF8SEQ

Message Text

Invalid UTF-8 escape sequence -- requests are not UTF-8 encoded

XDMP-RESECUREDECRYPT

Message Text

Unable to decrypt credential during resecure

Cause

An encrypted secret could not be resecured because it failed to decrypt. This could be due to the passed string not actually being encrypted, or due to not having access to the key that was originally used for encryption.

Response

Make sure the text is actually encrypted. If this credential was originally encrypted on a different cluster, importing encryption keys from that cluster may allow decryption.

XDMP-RESOLVEBADARG

W3C XQuery Standard Equivalent: err:FORG0002

Message Text

Invalid argument to fn:resolve-uri()

XDMP-RESTORENOMASTER

Message Text

Unable to restore replica forest variable1 because the master forest variable2 is not also restored, or is not acting master.

XDMP-RESULT

Message Text

result option not allowed in this function

XDMP-RETHROW

Message Text

Nothing to rethrow

XDMP-RETURNTYPE

Message Text

variable1 returned variable2 which is not of type variable3

XDMP-REVIDXBADQRY

Message Text

Reverse index bad query: variable1

XDMP-RIDXAMBIGUOUS

Message Text

Ambiguous variable1 range index for variable2 variable3

Cause

The options provided are not sufficient to uniquely identify a range index.

Response

Specify type, collation, coordinate-system, and/or precision options to uniquely identify a range index.

XDMP-RIDXNOTCOLL

Message Text

Collations are irrelevant to the variable1 range index for variable2 variable3

Cause

The options to cts:reference include a collation, but the range index is not a string data-type.

Response

Do not specify a collation in the cts:reference's options.

XDMP-RIDXNOTCOORD

Message Text

Coordinate systems are irrelevant to the variable1 range index for variable2 variable3

Cause

The options to cts:reference include a coordinate system, but the range index is not a geospatial data type.

Response

Do not specify a coordinate system in the cts:reference's options.

XDMP-RIDXNOTFOUND

Message Text

No variable1 range index for variable2 variable3 variable4

Cause

The query requires a range index that does not exist.

Response

Make sure the range index exists. If the range index is of type string, make sure it uses the collation specified in the query. If the range index is a geospatial index, make sure it uses the coordinate system specified in the query. If the range index was added recently, make sure reindexing is enabled and has completed.

XDMP-RIDXNOTPOSN

Message Text

Positions are not enabled on the variable1 range index for variable2 variable3

Cause

User has specified "ordered" or "proximity" options on cts:value-tuples when positions are not enabled on the range index.

Response

Either enable positions on the range index or do not specify "ordered" or "proximity" options on cts:value-tuples.

XDMP-RIDXTOOBIG

Message Text

Too many entries in range index variable1

XDMP-RMINVOP

Message Text

Recovery Manager invalid operation: variable1

XDMP-RMRECORD

Message Text

Journal record too large: variable1

XDMP-ROLLBACK

Message Text

Transaction rollback

XDMP-ROLLBACKBADTIME

Message Text

Bad rollback time: rollback timestamp (variable1) must be between database merge timestamp (variable2) and current timestamp (variable3)

XDMP-ROLLBACKNOMERGETIME

Message Text

Rollback requires database merge timestamp to be set

XDMP-RSLVNOTHTTP

Message Text

It's not http compatible to resolve entities embedded in document

Cause

Document is inserted through XCC in HTTP compatible mode, while ResolveEntities is set to true

Response

Disable HTTP compatible mode in XCC or set ResolveEntities to false

XDMP-RULEOP

Message Text

Invalid syntax for a rule definition: variable1

Cause

Rule definitions only allow a subset of SPARQL syntax.

Response

Restrict your rule definitions to use the correct syntax subset.

XDMP-RULESNOTFOUND

Message Text

The ruleset file cannot be found: variable1

Cause

The ruleset file referenced cannot be found.

Response

MarkLogic searches for rulesets in the schemas database configured for the queried database, as well as in the MarkLogic install directory for standard rulesets shipped the product. Check that the ruleset you are trying to use exists and has the correct name.

XDMP-RWANYALL

Message Text

One of the attributes any-of [variable1] or all-of [variable2] must be specified in rule: variable3

XDMP-RWATTRBLANK

Message Text

The attribute 'variable1' in rule: 'variable2' must not be empty or blank.

XDMP-RWATTRNOTSET

Message Text

The attribute 'variable1' in rule: variable2 must be explicitly provided.

XDMP-RWATTRNOTSET3

Message Text

At most one matching attribute of 'variable1', 'variable2', 'variable3' is allowed in rule: variable4.

XDMP-RWEMPTY

Message Text

The value of expression 'variable1' is required to be non-empty in rule: variable2

XDMP-RWINVAL0

Message Text

The value of expression 'variable1' is required to be non-zero in rule: variable2

XDMP-RWONEOF

Message Text

Only one of the attributes 'variable1' or 'variable2' may be supplied in rule: variable3

XDMP-RWREGEX

Message Text

Attempted evaluate an invalid regular expression: 'variable1' in rule: variable2 - error: variable3

XDMP-RWREPVAL

Message Text

The expression 'variable1' evaluated to multiple values in rule: variable2

XDMP-RWREQUNAVAIL

Message Text

The requested method name: 'variable1' is invalid in rule: variable2

XDMP-RWRPTPARAM

Message Text

Repeated values are not allowed for the variable1 attribute in rule: variable2.

XDMP-RWSYSVAR

Message Text

Attempted to set a system variable name: 'variable1' in rule: variable2

XDMP-SAMEARC

Message Text

Arcs must not be part of same great circle

Cause

geo:arc-intersection is called on two arcs that are on the same Great Circle.

Response

The error is reporting a state of nature. It is up to the application to decide what to make of that state of nature.

XDMP-SCHEDEVENTINPUT

Message Text

variable1

XDMP-SCHEMA-CANNOT

Message Text

Cannot variable1 -- variable2

XDMP-SCHMNSMISMATCH

Message Text

Namespace "variable1" does not match namespace in schema at "variable2"

XDMP-SCHPRFX

W3C XQuery Standard Equivalent: err:XQST0057

Message Text

Cannot declare a prefix for the empty namespace URI in a schema import

XDMP-SEARCH

Message Text

Searches not enabled

Cause

Neither stemmed nor word searches are enabled for the database.

Response

Use the Admin Interface to check and correct the database configuration.

If the database settings appear correct, ensure that any database re-indexing operations are completing correctly. In rare cases, this error has been seen when there is a re-indexing failure.

XDMP-SECDB

Message Text

Security database unavailable: exception_stack

XDMP-SECSTAMP

Message Text

Security timestamp too old

XDMP-SEEK

Message Text

variable1:Invalid lseek64, variable2

Cause

A host operating system file function returned an unexpected error while MarkLogic was accessing a file. The host operating system function, file name, and error message are included in the error report.

Response

See the host operating system documentation for the precise meaning of the error message. Check the operating system error log for file system or storage hardware problems. Restarting MarkLogic on the host may clear a persistent error condition. Restarting the operating system on the host may clear a persistent error condition.

XDMP-SERVERERR

Message Text

Error in server variable1

Cause

There is an app server or task server with that identifier, but not on this host. The identified host is not in the same group as the identified app server or task server.

Response

Choose a server identifier from the group the host belongs to.

XDMP-SERVERFIELDDATABASENODE

Message Text

Cannot put a database node or an object containing a database node in a server field

XDMP-SESSIONTXN

Message Text

Another request in the same session has concurrently started a multi-statement transaction

XDMP-SHUTDOWN

Message Text

Shutdown

XDMP-SPAWNMODULE

Message Text

No module to spawn

XDMP-SPAWNPATH

Message Text

Invalid spawn path: variable1

XDMP-SPECIALPROP

Message Text

Cannot update server-maintained properties

Cause

An attempt was made to update a server-maintained property, and user code cannot update those properties (for example, prop:last-modified, prop:content-length, and prop:directory).

Response

Change your code to not update these properties.

XDMP-SPQLBAD

Message Text

Grammar error in SPARQL: variable1

Cause

Grammar error

Response

Fix grammar error(s).

XDMP-SPQLBADAGG

Message Text

An aggregate function cannot be used in this position

Cause

You have used an aggregate function outside of a SELECT expression, HAVING clause, or ORDER BY clause.

Response

Move the use of the aggregate function to a permitted position.

XDMP-SPQLBADDATASET

Message Text

RDF Dataset is set inappropriately

Cause

Dataset is set in both the query and the options, making the SPARQL request not compliant with SPARQL 1.1 specification.

Response

Check the query and the options

XDMP-SPQLBADSTR

Message Text

Unescaped newline characters in SPARQL string literal: "variable1"

Cause

The SPARQL string contains unescaped newline characters.

Response

Escape newline characters using "\n", or use the three quote form of triple string literal.

XDMP-SPQLBINDVAR

Message Text

The BIND variable is already bound by an earlier clause in the group graph pattern: variable1

Cause

A variable bound by a BIND clause is already bound by an earlier clause in the group graph pattern, and its value cannot be changed.

Response

Use a different variable name in the BIND clause, or remove the clause entirely.

XDMP-SPQLBOUND

Message Text

Variable value supplied by the calling environment: variable1

Cause

A variable bound by a VALUES or BIND clause is already bound in the map passed into the call to sem:sparql() or sem:sparql-triples().

Response

Use a different variable name in the VALUES or BIND clause, or remove the clause entirely.

XDMP-SPQLGRAPHEXIST

Message Text

Graph already exists: variable1

Cause

The graph to create already exists.

Response

Check graph iri.

XDMP-SPQLINVALIDGRAPH

Message Text

Invalid format in Graph Document: variable1

Cause

Graph Document already exists but does not conform to schema.

Response

Check the Graph Document.

XDMP-SPQLNOINEQ

Message Text

Inequality operations are not supported on values of unknown type, unsupport type, or schema invalid values: variable1

XDMP-SPQLNOSUCHGRAPH

Message Text

No such RDF Graph: variable1

Cause

The graph does not exist.

Response

Check graph iri.

XDMP-SPQLSTRCOMPAT

Message Text

Incompatible string arguments

Cause

The string arguments to the SPARQL function have incompatible language tags.

Response

Use identical language tags, or strings without language tags.

XDMP-SPQLUPDATEINMEMORY

Message Text

Cannot use SPARQL Update on in-memory sem:store

Cause

Run SPARQL Update against in-memory sem:store

XDMP-SPQLUPDATESTMT

Message Text

Cannot execute multiple SPARQL Update statements with same-statement isolation

XDMP-SPQLVALUES

Message Text

The VALUES clause contains a row with the wrong number of values: variable1

Cause

All the rows of a VALUES clause must contain the same number of values.

Response

Add extra values or use UNDEF.

XDMP-STACK

Message Text

Parser stack overflow

XDMP-STACKOVERFLOW

Message Text

Stack overflow

XDMP-STANDVER

Message Text

Unsupported stand version variable1 for variable2

Cause

The version of this stand is outside the range supported by this version of Marklogic. Newer MarkLogic versions understand stands written from older MarkLogic versions, but older MarkLogic versions do not necessarily understand stands from newer MarkLogic versions.

Response

Check the compatibility of versions of MarkLogic you are switching between. The capability of MarkLogic understanding stands written by newer versions is limited. Generally patch versions are compatible, but major versions are not.

XDMP-STARTDOCUMENT

Message Text

A document node must be the first node.

XDMP-STARTELEMENT

Message Text

There can be only one root node.

XDMP-STATICCHECK

Message Text

static-check option not allowed in this function

XDMP-STEMSEARCH

Message Text

Stemmed word searches not enabled

XDMP-STEPCONTEXTITEMNOTNODE

W3C XQuery Standard Equivalent: err:XPTY0020

Message Text

Context item is not a node

XDMP-STRINGFUNC

W3C XQuery Standard Equivalent: err:FOTY0014

Message Text

You cannot take the string value of a function

XDMP-SUBDBTIMESTAMP

Message Text

Sub-databases have different timestamps

XDMP-TAINTEDCACHEDMODULE

Message Text

Detected stale XSLT module: variable1

Cause

An XSLT module on the filesystem, or a module that uses an XSLT module, has been detected as being out of date.

Response

If XDMP-TAINTEDCACHEMODULE appears as an infrequent Debug message, no action is required. Cache invalidation is a normal part of database operations.

If XDMP-TAINTEDCACHEMODULE appears frequently as a Debug message, you may have a performance issue. You should avoid modifying your modules so frequently, so that you get the advantage of module caching.

XDMP-TARGETEXISTS

Message Text

The target path already exists: "variable1"

XDMP-TASKMODULE

Message Text

Modules database for Task does not exist

XDMP-TELEM-INTERR

Message Text

An internal error was encountered communicating with Telemetry: variable1

XDMP-TELEM-INTERR2

Message Text

An internal error was encountered communicating with Telemetry: variable1 variable2 variable3 variable4 variable5

XDMP-TELEM-INVENDP

Message Text

No valid endpoint was found to connect to Telemetry: variable1

XDMP-TELEM-INVMSG

Message Text

Not a valid JSON structure in: variable1

XDMP-TELEM-INVREQ

Message Text

An invalid request error was returned as a response to communicating with Telemetry: method variable1, variable2

XDMP-TELEM-INVRESP

Message Text

The response received from Telemetry is invalid: variable1

XDMP-TELEM-RETRY

Message Text

The maximum number of retries exceeded while connecting to Telemetry: variable1

XDMP-TELEM-SEC

Message Text

An attempt to connect to Telemetry using https requires SSL: variable1, $2

XDMP-TEXTNODE

Message Text

Server unable to build program from non-text document

Cause

MarkLogic server is unable to construct a program from the module at the indicated location. Possible causes include:

There is no module at the indicated location.The module was not loaded as a text file.An imported module could not be found.

Response

Verify your module location is consistent with the root configured into your app server.

Make sure you upload modules into the app server as text. Usually, using the .xqy suffix and no type is sufficient.

Ensure your app server and your code are in agreement. For example, if you place your code in the file system, your app server should reference it in the file system, not in a database. If you place your code in a database, ensure your app server references the same database.

XDMP-TIDYERR

Message Text

An error occured trying to run tidy: code=variable1 message='variable2'

XDMP-TIME

Message Text

Invalid time

XDMP-TIMELIMIT

Message Text

Request time limit exceeds the maximum allowed.

XDMP-TIMEZONEVAL

W3C XQuery Standard Equivalent: err:FODT0003

Message Text

Invalid timezone value

XDMP-TONODE

Message Text

There is no node to build.

XDMP-TOOBIG

Message Text

Document size exceeds variable1 document size limit of variable2 megabytes

XDMP-TOOFEWARGS

W3C XQuery Standard Equivalent: err:XPST0017

Message Text

Too few args, expected variable1 but got variable3

Cause

The function call provided too few arguments for the function.

Response

Check the documentation for expected arguments, and provide the correct number.

XDMP-TOOFEWLABELS

Message Text

Too few labels, expected variable1 but got variable2

XDMP-TOOMANYARGS

W3C XQuery Standard Equivalent: err:XPST0017

Message Text

Too many args, expected variable2 but got variable3

Cause

The function call provided too many arguments for the function.

Response

Check the documentation for expected arguments, and provide the correct number.

XDMP-TOOMANYATOMS

Message Text

Document contains too many atoms

XDMP-TOOMANYCHARCLASS

Message Text

Too many character classes: variable1

XDMP-TOOMANYCHARS

Message Text

Document contains too many characters

Cause

A document cannot contain more than 2^32 (4294967296) total characters of unique tokens.

Response

Make your document smaller and/or break the document into multiple smaller documents.

XDMP-TOOMANYLABELS

Message Text

Too many labels, expected variable1 but got variable2

XDMP-TOOMANYNODES

Message Text

Document contains too many variable1 nodes

Cause

A document cannot contain more than 2^28 (268435456) total nodes (text nodes, element nodes, attribute nodes, and so on).

Response

Make your document smaller and/or break the document into multiple smaller documents.

XDMP-TOOMANYPOSITIONS

Message Text

Too many positions

XDMP-TOOMANYSTANDS

Message Text

Too many stands

Cause

The forest has reached the 64-stand limit.

Response

This error can occur if the system has not been allowed to merge and has accumulated more stands than the stand limit. Make sure that merging is enabled, and that your MERGE MAX SIZE is not set to such a low number that the system cannot merge (the default of 48GB is recommended for MERGE MAX SIZE). Merging reduces the number of stands in a forest, and merging is needed to get past this error.

XDMP-TOOMUCHTEXT

Message Text

Document contains too much text

Cause

A document cannot contain more than 2^28 (268435456) memorywords, which are used to encode atom IDs. This translates to roughly 200 million text nodes, depending on how big the text nodes are. This limit is for a document constructed in memory; when you save a document to the database, the limit is 512MB per fragment.

Response

Make your document smaller and/or break the document into multiple smaller documents.

XDMP-TREAT

W3C XQuery Standard Equivalent: err:XPDY0050

Message Text

Invalid treat: variable1 treat as variable2

XDMP-TRIGGERMODULE

Message Text

Could not find trigger module: variable1

XDMP-TRIGGERPATH

Message Text

Invalid trigger path: variable1

XDMP-TRIPLE

Message Text

Invalid triple element

Cause

Invalid triple element.

Response

Check element and try again.

XDMP-TRIPLEOPCOUNT

Message Text

Wrong number of operators specified for the triple index function, variable1 operators supplied

Cause

The wrong number of operator string have been given.

Response

Use either one operator or three.

XDMP-TRIPLESDOC

Message Text

Invalid triples document

Cause

Invalid triples document.

Response

Check triples document and try again.

XDMP-TRPLCACHEFULL

Message Text

Triple cache full on host variable1

XDMP-TRPLIDXBADTRPL

Message Text

Triple index bad triple: variable1: variable2

XDMP-TRPLIDXNOTFOUND

Message Text

Triple index not enabled

XDMP-TRPLIDXTOOBIG

Message Text

Too many entries in triple index variable1

Cause

The settings for maximum stand size are set too large, resulting in a stand with more than 2^32 distinct values in the triple index.

Response

Review your settings for maximum stand size.

XDMP-TRPLPERMNOTFOUND

Message Text

Triple index permutation not enabled

Cause

Forests created on versions of MarkLogic before 9.0-1 did not support some triple index sort orders.

Response

Reindex the database.

XDMP-TRPLVALCACHEFULL

Message Text

Triple value cache full: variable1

XDMP-TSOVERFLOW

Message Text

Timestamp overflow

XDMP-TXNCOMPLETED

Message Text

Transaction with identifier variable1 already completed

Cause

A statement waiting to execute using an explicit transaction ID has found that the transaction has already been committed or rolled back before it could execute.

Response

Do not commit or rollback the transaction until all statements have finished executing using it.

XDMP-TXNMODELIB

Message Text

Transaction mode options cannot be used in library modules

Cause

A transaction mode option was specified in an XQuery library module.

Response

Move the transaction mode option to the main module.

XDMP-TXNMODEOPTVAL

Message Text

Invalid transaction-mode value: must be "auto", "query", or "update"

Cause

A transaction mode was specified with an incorrect value.

Response

Correct the transaction mode.

XDMP-UDFBADCAST

Message Text

The TupleIterator tuple member accessor is not defined for that type

Cause

The wrong TupleIterator accessor has been called for the type of that tuple member.

Response

Use the correct accessor for the type.

XDMP-UDFBOUND

Message Text

TupleIterator index out of bounds: variable1

Cause

The specified index is greater than the width of the tuple.

Response

Add code to handle smaller tuple widths than expected.

XDMP-UDFENCSIZE

Message Text

Encoder capacity exceeded. host: variable1

Cause

The Encoder has a limit of 512Mb of data permitted in one message.

Response

This may indicate a bug in your encoding algorithm.

XDMP-UDFERR

Message Text

An error occured in the user-defined function plugin: variable1

Cause

A user defined function from a plugin reported an error.

Response

Consult the error message.

XDMP-UDFEXPIRED

Message Text

The plugin API value has expired

Cause

Plugin API values like Map and Sequence have defined lifetimes, after which they cannot be used.

Response

Copy the values you need out of the plugin API values.

XDMP-UDFOUTSEQ

Message Text

Invalid OutputSequence usage: variable1

Cause

The methods of OutputSequence have been called in an order that does not make sense.

Response

Fix the code using the OutputSequence instance.

XDMP-UDFSEQEND

Message Text

Member access on a Sequence object when Sequence::done() is true.

Cause

The Sequence object has moved past the end of the sequence. This can happen because it is an empty sequence, or because Sequence::next() has been called until the end of Sequence has been reached.

Response

Only access Sequence members if Sequence::done() returns false.

XDMP-UKOPT

Message Text

Unknown xdmp:tidy option or bad option value: variable1

XDMP-UNBPRFX

W3C XQuery Standard Equivalent: err:XPST0081

W3C XSLT Standard Equivalent: err:XTSE0280

Message Text

Prefix variable1 has no namespace binding

Cause

A namespace prefix appears in your code for which there is no declared namespace binding.

Response

Declare your namespaces explicitly.

XDMP-UNCTHRW

Message Text

variable1:Uncaught throw

XDMP-UNDAGGFUN

Message Text

Undefined aggregate function variable1

Cause

You have used an aggregate function name that does not exist.

Response

Examine your code for typos, or ensure that the requisite aggregate is defined.

XDMP-UNDCOMTYP

Message Text

Undefined complex type variable1

XDMP-UNDFUN

W3C XQuery Standard Equivalent: err:XPST0017

Message Text

Undefined function variable1

Cause

You have used a function name that is not in scope.

Response

Examine your code for typos, missing namespace qualifications, or missing module imports.

XDMP-UNDSCHM

W3C XQuery Standard Equivalent: err:XQST0059

Message Text

Undefined schema "variable1"

XDMP-UNDSCHMAT

W3C XQuery Standard Equivalent: err:XQST0059

Message Text

Undefined schema "variable1" at "variable2" resolved to "variable3"

XDMP-UNDSIMTYP

W3C XQuery Standard Equivalent: err:XPST0051

Message Text

Undefined simple type variable1

XDMP-UNDTYP

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Undefined type variable1

XDMP-UNDVAR

W3C XQuery Standard Equivalent: err:XPST0008

Message Text

Undefined variable variable1

XDMP-UNEXPECTED

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Unexpected token variable1

XDMP-UNEXPECTEDSTANDS

Message Text

Unexpected stands in forest variable1: missing=variable2 found=variable3

XDMP-UNINDEXABLEPATH

Message Text

Invalid syntax for path index: variable1 exception_stack

Cause

Only a subset of XPath 2.0 syntax is allowed in index creation. User has supplied a path expression that has some non-permitted syntax.

Response

Check the syntax of path expression. Only a sub-set of XPath 2.0 grammar is allowed in index creation.

XDMP-UNKNOWNCHARCLASS

Message Text

Unknown character class: variable1

XDMP-UNKNOWNDIR

Message Text

Unknown directory variable1 in backup directory

XDMP-UNKNOWNFEATURE

W3C XQuery Standard Equivalent: err:XQST0123

Message Text

Unknown required feature: variable1

XDMP-UNKNOWNFILE

Message Text

Unknown file variable1 in backup directory

XDMP-UNKVAR

Message Text

An unknown URL template expansion variable was encountered connecting to Ops Director: variable2

XDMP-UNLOCKED

Message Text

Unlocked, variable1

Cause

During a read or write operation, the system encountered an unlocked node or other resource where a lock was expected. For example, during cts:eval, the system expects a read lock on the node being evaluated.

Response

Correct your code. The context for the error is included in the message. To learn more about locking in MarkLogic Server, see the Application Developer's Guide.

XDMP-UNPATH

Message Text

Invalid format for unpath

Cause

xdmp:unpath function supports a subset of XPath syntax. User has specified a path expression that uses XPath operators xdmp:unpath does not support.

Response

Refer to MarkLogic Server documentation for the xdmp:unpath supported XPath syntax.

XDMP-UNREGISTERED

Message Text

Query variable1 is not registered

XDMP-UNSEARCHABLE

Message Text

Expression is unsearchable

XDMP-UNSUPPORTED

Message Text

Unsupported

XDMP-UNSUPPORTED-TYPE

Message Text

Unsupported lexicon type: variable1

Cause

The type of the lexicon input is not supported.

Response

Correct your code.

XDMP-UNSUPPORTED-TYPE-FIRST-ITEM

Message Text

Unsupported data type

Cause

The data type of the first item is not supported.

Response

Correct your code.

XDMP-UNSUPPORTEDLANGUAGE

Message Text

Number formatter doesn't support this language.

Cause

User has specified an unsupported language.

Response

Use one of the supported languages.

XDMP-UNWILLINGFOREIGNREPLICA

Message Text

Unwilling foreign replica: forest variable1 does not accept update from forest variable2 in cluster variable3 (variable4)

Cause

This occurs during database replication when a forest in the replica database receives an update from an unexpected forest in the master database. Typically, this is due to the asynchronous nature of replication and communication within the cluster and the issue will resolve automatically.

Response

If the issue does not resolve automatically within a few minutes, contact support.

XDMP-UNWILLINGREPLICA

Message Text

Unwilling replica: forest variable1 does not accept update from forest variable2 (variable3)

Cause

This occurs during local-disk fail-over forest replication when a replica forest receives an update from an unexpected forest. Typically, this is due to the asynchronous nature of replication and communication within the cluster and will resolve automatically.

Response

If the issue does not resolve within a few minutes, contact support.

XDMP-UPCONSTNODES

Message Text

Cannot update constructed nodes

XDMP-UPDATEFROMQUERY

Message Text

Cannot process updates from queries with same-statement isolation

Cause

A transaction being run as a query attempted to perform an update. For example, using xdmp:apply to execute an update function when the xdmp:apply is in a query transaction.

This error also occurs if you use xdmp:eval or xdmp:invoke with same-statement isolation in a query transaction. You may only use same-statement isolation with update transactions.

For more information, see the discussion of Isolation option to xdmp:eval/invoke in the Application Developer's Guide.

Response

Possible solutions to this error include:

Use different-transaction isolation in the problem xdmp:eval or xdmp:invoke.Use xdmp:eval instead of xdmp:apply if you know the applied function may be an update.If the problem occurs with xdmp:apply, and you know the applied function will perform an update, force the transaction to be an update. For example:
let $force-update :=
  if (fn:true())
  then ()
  else xdmp:document-insert('/fake.xml', <fake></fake>)

XDMP-UPDATEFUNCTIONFROMQUERY

Message Text

Cannot apply an update function from a query

Cause

A dynamic function call was made to a function that might perform database updates. This is not allowed from a statement executing under a query (read-only) transaction.

Response

Execute the calling statement under an update transaction. Define the function so that it does not update the database.

XDMP-UPDATEOPTVAL

Message Text

Invalid xdmp:update option value, must be "true" or "false"

XDMP-UPDATESNOTALLOWED

Message Text

No forests allow updates variable1

XDMP-UPDATETIMESTAMP

Message Text

Cannot process timestamped updates

XDMP-UPEXTNODES

Message Text

Cannot update external nodes

XDMP-URI

Message Text

Invalid URI format: variable1

XDMP-URILXCNNOTFOUND

Message Text

URI lexicon not enabled

XDMP-URIRESNFAILED

W3C XQuery Standard Equivalent: err:XTDE1420

Message Text

Failed to resolve URI(s)

XDMP-USEAPPSRVRLDAPWITHURL

Message Text

Cannot use app server LDAP configuration with user specified URL

Cause

An LDAP operation was attempted that specified both a server URL and requested that the app server configuration be used.

Response

Either specify an empty URL, or don't use the app server configuration

XDMP-USEDECLARE

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Use 'declare' rather than 'define' (declare variable1)

XDMP-USEEMPTYSEQ

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Use 'empty-sequence()' rather than 'empty()'

XDMP-USERCHANGEONLYDIFFTRANS

Message Text

User change is only allowed for a different transaction

XDMP-UTF8SEQ

Message Text

Invalid UTF-8 escape sequence

Cause

A string contains an invalid UTF-8 byte sequence.

Response

Encode the string in UTF-8 correctly.

XDMP-VALIDATEABSTRACT

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Instance of abstract element: Element variable1 is abstract using schema variable2

Cause

Validation determined that an element in the instance was declared as abstract in the schema. This means that the specific element name should not appear in a valid document. Typically such an element is a substitution group head and the document should contain specific members of that substitution group instead.

Response

Fix the instance to that it does not contain abstract elements.

XDMP-VALIDATEABSTRACTTYPE

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Instance of abstract type: Type variable1 of element variable2 is abstract using schema variable3

Cause

Validation determined that an element had a complex type declared in the schema as abstract. This may reflect the case where the intention is that the instance include an xsi:type selecting a specific concrete subtype.

Response

Fix the element in the instance to be valid, perhaps by adding an xsi:type attribute.

XDMP-VALIDATEBADARG

W3C XQuery Standard Equivalent: err:XQTY0030

Message Text

Argument to validate expression must be document or element node

Cause

An attempt was made to validate something that was not a document node, element node, or (in XSLT) an attribute node.

Response

Fix the application to avoid validation of inappropriate items.

XDMP-VALIDATEBADDERIV

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Invalidly derived type: Element variable1 xsi:type variable2 not validly derived from variable3 using schema variable4

Cause

Validation detected an element with an xsi:type attribute where the type referred to in that attribute was not validly derived from the declared type of the element. This could be because the type is not a subtype of the declared type at all, or because the schema prohibits the derivation explicitly.

Response

Fix the instance to use an appropriate type in the xsi:type attribute, or fix the schema to allow the derivation, if appropriate.

XDMP-VALIDATEBADDOCNODE

W3C XQuery Standard Equivalent: err:XQST0061

Message Text

A validated document node must contain exactly one root element

Cause

Validation was attempted on a document node that was a binary document, a text document, or had more than one root element.

Response

Validation only applies to XML documents.

XDMP-VALIDATEBADFIELD

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

Bad field specification: Bad field specification variable1 at variable2 using schema variable3

Cause

Validation detected an identity constraint definition whose field was not a valid XPath expression.

Response

Fix the identity constraint definition in the schema.

XDMP-VALIDATEBADFIELDTYPE

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

Bad field type: Bad type for field variable1 at variable2 using schema variable3

Cause

Validation detected an identity constraint definition whose field failed to select a single element node with simple content.

Response

The instance is invalid. Fix the instance.

XDMP-VALIDATEBADFIXED

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Invalid fixed type: variable1 lexical value variable2 invalid for expected fixed value variable3 at variable4 using schema variable5

Cause

Validation detected an attribute or element that was declared to have a fixed value in the schema, but the attribute or element did not have that value.

Response

The instance is invalid. Replace the offending value with the correct fixed value.

XDMP-VALIDATEBADKEY

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

Bad key: Non-referring key field variable1 at variable2 using schema variable3

Cause

Validation detected a key constraint that failed to select any elements.

Response

The instance is invalid. Make sure that all key values refer properly.

XDMP-VALIDATEBADKEYREF

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

Bad referenced key: Bad referenced key for keyref variable1 at variable2 using schema variable3

Cause

Validation detected a keyref constraint that failed to refer to node value for a key.

Response

The instance is invalid. Make sure that all elements with keyref constraints properly refer to node value for a key.

XDMP-VALIDATEBADSCHEMA

Message Text

Invalid schema "variable1" at "variable2": exception_stack

Cause

The schema variable1 at schema URI variable2, used in a validation episode, does not meet the validity requirements of XML Schema Part I, as defined by W3C. In a valid schema, all definitions are valid, complete, and unique.

Response

Review and correct your schema. Check for duplicate or erroneous definitions.

XDMP-VALIDATEBADSELECTOR

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

Bad selector specification: Bad selector specification variable1 at variable2 using schema variable3

Cause

Validation encountered an identity constraint definition with a selector that was not a valid XPath expression.

Response

The schema is invalid. Ensure that the XPath expressions on the identity constraint selectors are valid.

XDMP-VALIDATEBADTYPE

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Invalid node type: variable1 lexical value variable2 invalid for expected type variable3 at variable4 using schema variable5

Cause

Validation encountered an element or attribute simple value that was not lexically valid per the declared type.

Response

The instance is invalid. Ensure that the content of the element or attribute has the correct lexical form for its declared type.

XDMP-VALIDATEDUPID

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

Duplicate ID: ID value variable1 is a duplicate at variable2 using schema variable3

Cause

Validation determined that the same ID was used more than once in a document.

Response

The document is invalid. Make sure there is only one definition of each ID.

XDMP-VALIDATEDUPKEY

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

Duplicate key: Duplicate key variable1 for identity constraint variable2 at variable3 using schema variable4

Cause

Validation determined that a uniqueness constraint was violated. For some identity constraint definition declared with unique keys, a key was used in the document more than once.

Response

The document is invalid. Make sure each key that is supposed to be unique is defined only once in the document.

XDMP-VALIDATEFAILED

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

Validated node was not valid: variable1 (variable2)

Cause

Validation failed for some reason not specifically called out. For example, if an attribute is declared as having a fixed value and the type xs:ID, this error occurs. The error gives more information for the reason for the failure.

Response

Depending on the specific reason for the error, the instance may be invalid and need fixing, or the schema may be invalid and need fixing.

XDMP-VALIDATEMISSINGATTR

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Missing required attribute: Found variable1 but required variable2 at variable3 using schema variable4

Cause

Validation detected an element that was missing a required attribute.

Response

The instance is invalid. Add the required attribute to the element.

XDMP-VALIDATEMISSINGELT

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Missing required elements: Expected variable1 at variable2 using schema variable3

Cause

Validation detected an element that was missing a required child element.

Response

The instance is invalid. Add the missing element.

XDMP-VALIDATENILLED

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Nilled element has content: Element variable1 nilled but has content

Cause

Validation detected an element that was declared as nillable and had an xsi:nil element, but which had child elements or text content anyway.

Response

The instance is invalid. Either remove the xsi:nil attribute or remove the non-nilled content from the element.

XDMP-VALIDATENODECL

W3C XQuery Standard Equivalent: err:XQDY0084

Message Text

Missing element declaration: Expected declaration for node variable1 in non-lax mode using schema variable2

Cause

Validation failed because an element or attribute was found without a corresponding declaration. In some cases this can occur because an element somewhere within the subtree of the element was missing a declaration. This can be either because the schema is missing the declaration, the proper schema could not be located, or the element or attribute is incorrect (misspelled, for example).

Response

Fix the schema or the content or the schema location as appropriate.

XDMP-VALIDATENOID

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

No ID for IDREF: IDREF value variable1 has no corresponding ID using schema variable2

Cause

Validation detected the use of an IDREF with no corresponding ID in the document.

Response

The document is invalid. Make sure that every reference to an ID matches up with some ID in the document.

XDMP-VALIDATENOKEYREF

W3C XQuery Standard Equivalent: err:XQDY0027

W3C XSLT Standard Equivalent: err:XTTE1555

Message Text

No matching key for keyref: No matching key for keyref variable1 for identity constraint variable2 at variable3 using schema variable4

Cause

Validation detected a keyref value that had no corresponding key value in the document.

Response

The document is invalid. Make sure that every keyref matches some key in the document.

XDMP-VALIDATENONILLABLE

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Element not nillable: Element variable1 disallows @xsi:nil using schema variable2

Cause

Validation detected an element with xsi:nil set to true where the element declaration does not allow for nilled instances.

Response

The instance is invalid. Either remove the xsi:nil attribute or add appropriate content to the element to make it valid with respect to its declaration.

XDMP-VALIDATEUNDTYPE

W3C XQuery Standard Equivalent: err:XQDY0084

W3C XSLT Standard Equivalent: err:XTSE1520

Message Text

Missing type definition: Expected type definition for variable1 for node variable2 using schema variable3

Cause

Validation could not find a type definition for an element or attribute. This could be because the element or attribute is spelled incorrectly or misplaced, because the schema lacked a definition, or because the proper schema could not be located.

Response

Fix the instance, the schema, or the schema location as appropriate.

XDMP-VALIDATEUNEXPECTED

W3C XQuery Standard Equivalent: err:XQDY0027

Message Text

Invalid node: Found variable1 but expected variable2 at variable3 using schema variable4

Cause

Validation detected unexpected content (element, attribute, or text).

Response

The instance is invalid. Fix the content to be valid. Check the name of the element or attribute reported as unexpected, or remove the unexpected text.

XDMP-VALIDATIONERRORS

W3C XQuery Standard Equivalent: err:XQDT0027

Message Text

Validation failed: variable1 exception_stack

Cause

Reserved for XQDT error.

Response

Reserved for XQDT error.

XDMP-VARNS

W3C XQuery Standard Equivalent: err:XQST0048

Message Text

Variable variable1 not in target namespace variable2

XDMP-VARPUBPRIV

W3C XQuery Standard Equivalent: err:XQST0116

Message Text

A variable declaration's annotations cannot contain more than one annotation named %fn:private or %fn:public.

XDMP-WINREGERR

Message Text

Windows registry error: variable1 variable2: variable3

XDMP-WINSVCERR

Message Text

Windows service error: variable1: variable2

Cause

MarkLogic Server, running as a service on the Windows platform, received an unexpected error. variable1 names the internal operation which encountered an error, and variable2 describes the specific problem. For example:

XDMP-WINSVCERR OpenSCManager Access is denied.

In this example, an access denied error occurred while the server was attempting to connect to the Windows Service Control Manager. The underlying cause was starting the server without Windows Administrator privileges.

Response

Corrective action varies, depending upon the specific Windows service error encountered. Contact MarkLogic Technical Support if you are uncertain how to proceed.

XDMP-WORDLXCNNOTFOUND

Message Text

No word lexicon for variable1

Cause

The query requires a lexicon that does not exist.

Response

Make sure the lexicon exists. If the lexicon was added recently, make sure reindexing is enabled and has completed.

XDMP-WORDSEARCH

Message Text

Unstemmed word searches not enabled

XDMP-WRITE

Message Text

variable1:Invalid write, variable2

Cause

An inconsistency was detected while writing an index file. Details about the inconsistency are included in the error report.

Response

Restarting MarkLogic on the host may clear an incosistency in memory. Merging on the affected forest may clear an inconsistency on disk. Reindexing the affected forest may clear an inconsistency on disk.

XDMP-WRONGARITY

W3C XQuery Standard Equivalent: err:XPTY0004

Message Text

Wrong number of arguments specified, expected variable1 but got variable2

Cause

The dynamic function call provided the wrong number of arguments for the function.

Response

Check the documentation for expected arguments, and provide the correct number.

XDMP-WRONGCLUSTER

Message Text

cluster variable1(variable2) thinks it is really cluster variable3(variable4)

Cause

A host connects to another host and thinks that host is in the same cluster. But the cluster id does not match. This can happen if some hosts are using an older configuration and other hosts are using a new configuration.

Response

Check if configurations on the hosts are correct.

XDMP-WRONGHOST

Message Text

Host variable1(variable2) thinks it is really host variable3(variable4)

XDMP-XATXN

Message Text

Operation not allowed on the XA transaction with identifier variable1

Cause

The function xdmp:commit and xdmp:transaction-commit cannot be executed against an XA transaction.

Response

Commit the transaction using the transaction manager that started it. In exceptional circumstances, an administrator can call xdmp:transaction-rollback to remove the transaction from the system.

XDMP-XDBCVER

Message Text

XDBC client version is incompatible with server: client version: variable1

XDMP-XDQPBADLOCALITY

Message Text

Bad XDQP Locality for connection from variable1 variable2 in cluster variable3 on variable4 port

XDMP-XDQPDIFFPLATARCH

Message Text

XDQP cannot communicate with different platform/architecture

XDMP-XDQPDISC

Message Text

XDQP connection disconnected, variable1

Cause

The internal cluster protocol connection (XDQP) between two nodes in the cluster was unexpectedly closed. This is a retryable exception.

Response

Normally, the nodes in the cluster will automatically reconnect without manual intervention. This is a retryable exception, and if a client application runs into the exception it can retry the request. If there is a problem with one of the nodes, then the other node cannot reconnect and the problem node will be dropped from the cluster. After the problem node is dropped, correct the problem and reconnect the affected node to the cluster.

XDMP-XDQPINVREQ

Message Text

Invalid XDQP request, variable1

Cause

XDQP is a MarkLogic internal protocol used for communicating between e-node and d-node hosts. Possible causes of this error include:

Another application is using the port assigned to XDQP.A query, join, or other operation in your MarkLogic application attempted to pass more than 160M of data in a single remote request.

Response

If you suspect another application is using the XDQP port, disable the application or move it to another port.

If you suspect your application is exceeding the 160M transmission limit, refactor your operation to pass data in smaller chunks. For example, optimize your query to fetch fewer unwanted results from the d-node.

XDMP-XDQPINVRESP

Message Text

Invalid XDQP response, variable1

Cause

XDQP is a MarkLogic internal protocol used for communicating between e-node and d-node hosts. Possible causes of this error include:

Another application is using the port assigned to XDQP.A query, join, or other operation in your MarkLogic application attempted to return more than 160M of data in a single remote request.

Response

If you suspect another application is using the XDQP port, disable the application or move it to another port.

If you suspect your application is exceeding the 160M transmission limit, refactor your operation to pass data in smaller chunks. For example, optimize your query to fetch fewer unwanted results from the d-node.

XDMP-XDQPMAX

Message Text

Too many XDQP listeners on host variable1

Cause

The maximum number of hosts connecting to this host through XDQP has been exceeded. No more than 255 other hosts may connect to this host through XDQP. Hosts in local clusters connect to every other host in the cluster. Hosts in foreign clusters connect to hosts with replica forests. Hosts in foreign clusters also connect through bootstrap hosts.

Response

Avoid creating large single clusters of hosts. Instead use super-clusters and super-databases. For example, 1024 hosts can be organized into 32 clusters of 32 hosts. See the MarkLogic Administrators Guide Chapter about Super Databases and Clusters.

XDMP-XDQPNORESULTS

Message Text

No XDQP results, variable1

XDMP-XDQPNOSESSION

Message Text

No XDQP session on host variable1, variable2

Cause

An XDQP message referenced an XDQP session that does not exist. This can happen if an XDQP session timed out (for example, if the network is really busy) or if an XDQP session was terminated (for example, if a node restarted).

Response

If the message shows as a debug message in the ErrorLog.txt file, and if there are a small number of these messages, then it indicates that there was a transient problem that corrected itself. If you see many messages for a large period of time, it might be an indication of a system that is resource bound, and you should find the cause of the resourse contention and correct it.

XDMP-XDQPVER

Message Text

XDQP version mismatch: variable1

Cause

XDQP is a MarkLogic internal protocol used for communicating between e-node and d-node hosts. This message indicates the two hosts involved in the communication are running incompatible versions of MarkLogic Server.

Response

Check the compatibility of the versions of MarkLogic Server running on the affected hosts and upgrade or downgrade one host, if appropriate.

XDMP-XIDNOTFOUND

Message Text

No transaction with Xid variable1

Cause

A transaction with the given Xid was not found.

Response

This usually indicates an error in the transaction manager being used. You should report this as a bug to the transaction manager vendor.

XDMP-XMLCHAR

Message Text

Invalid XML character variable1

XDMP-XMLFUNC

W3C XQuery Standard Equivalent: err:XQTY0105

Message Text

Functions cannot be used in the content of an element constructor

XDMP-XMLNSATTR

W3C XQuery Standard Equivalent: err:XQDY0044

Message Text

Cannot create xmlns attribute with computed attribute constructor

XDMP-XMLPI

W3C XQuery Standard Equivalent: err:XPST0003

Message Text

Processing instructions may not have the target 'XML'

XDMP-XPATH2TOOMANYBASENODES

W3C XQuery Standard Equivalent: err:XTDE1420

Message Text

XPath 2.0 prohibits a sequence of more than one nodes as a base node

XDMP-XQUERYVERSION

W3C XQuery Standard Equivalent: err:XQST0031

Message Text

XQuery version is not recognized: "variable1" (must be "0.9-ml", "1.0" or "1.0-ml")

XDMP-XQUERYVERSIONMISMATCH

Message Text

Declared XQuery version (variable1) does not match this parser (variable2)

XDMP-XQUERYVERSIONSWITCH

Message Text

All modules in a module sequence must use the same XQuery version: first="variable1", this="variable2"

XDMP-XSDFRG

Message Text

Fragmented schema

XDMP-XSDNONSBIND

Message Text

No namespace binding for prefix in schema reference: Prefix in reference to 'variable1' not bound

XDMP-ZEROITEMS

W3C XQuery Standard Equivalent: err:FORG0004

Message Text

fn:one-or-more called with a sequence containing zero items

XDMP-ZIPCLOSE

Message Text

Error closing zip file

XDMP-ZIPCOUNT

Message Text

Mismatched counts: variable2 parts, but variable1 nodes

XDMP-ZIPCRYPT

Message Text

File in zip is encryped: variable1

XDMP-ZIPDUPNAME

Message Text

Duplicate names not allowed in zip files: variable1

XDMP-ZIPFNF

Message Text

File not found in zip: variable1

XDMP-ZIPPATH

Message Text

Path of a ZIP part is empty

XDMP-ZIPTOOBIG

Message Text

File is too big to add to zip

XDMP-ZIPWRITE

Message Text

Error adding file to zip

« Previous chapter
Next chapter »
Powered by MarkLogic Server 7.0-4.1 and rundmc | Terms of Use | Privacy Policy