General Error Messages - InterSystems Documentation

More documents

Recommendations

Info

TSQL Error MessagesError Code68136814681568166817681868196820682168246825682668276828682968306831683268336834DescriptionFOR XML EXPLICIT cannot combine multiple occurrences of ID, IDREF, IDREFS,NMTOKEN, and/or NMTOKENS in column name '%.*ls'.In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, andNMTOKENS require attribute names in '%.*ls'.In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, andNMTOKENS attributes cannot be hidden in '%.*ls'.In the FOR XML EXPLICIT clause, ID, IDREF, IDREFS, NMTOKEN, andNMTOKENS attributes cannot be generated as CDATA, XML, or XMLTEXT in'%.*ls'.FOR XML EXPLICIT cannot combine multiple occurrences of ELEMENT, XML,XMLTEXT, and CDATA in column name '%.*ls'.In the FOR XML EXPLICIT clause, CDATA attributes must be unnamed in '%.*ls'.The FOR XML clause is not allowed in a %ls statement.FOR XML EXPLICIT requires column %d to be named '%ls' instead of '%.*ls'.GROUP BY and aggregate functions are currently not supported with FOR XMLAUTO.In the FOR XML EXPLICIT clause, mode '%.*ls' in a column name is invalid.ELEMENTS mode requires FOR XML AUTO.Every IDREFS or NMTOKENS column in a FOR XML EXPLICIT query mustappear in a separate SELECT clause, and the instances must be ordered directlyafter the element to which they belong.FOR XML EXPLICIT queries allow only one XMLTEXT column per tag. Column'%.*ls' declares another XMLTEXT column that is not permitted.XMLTEXT column '%.*ls' must be of a string data type.FOR XML EXPLICIT and RAW modes currently do not support addressing binarydata as URLs in column '%.*ls'. Remove the column, or use the BINARY BASE64mode, or create the URL directly using the'dbobject/TABLE[@PK1="V1"]/@COLUMN' syntax.FOR XML AUTO could not find the table owning the following column '%.*ls' tocreate a URL address for it. Remove the column, or use the BINARY BASE64mode, or create the URL directly using the'dbobject/TABLE[@PK1="V1"]/@COLUMN' syntax.FOR XML AUTO requires primary keys to create references for '%.*ls'. Selectprimary keys, or use BINARY BASE64 to obtain binary data in encoded form ifno primary keys exist.FOR XML AUTO cannot generate a URL address for binary data if a primary keyis also binary.Parent tag ID %d is not among the open tags. FOR XML EXPLICIT requiresparent tags to be opened first. Check the ordering of the result set.XMLTEXT field '%.*ls' contains an invalid XML document. Check the root tag andits attributes.148 Caché Error Reference
TSQL Error MessagesError Code683568366837683868396840DescriptionFOR XML EXPLICIT field '%.*ls' can specify the directive HIDE only once.FOR XML EXPLICIT requires attribute-centric IDREFS or NMTOKENS field '%.*ls'to precede element-centric IDREFS/NMTOKEN fields.The XMLTEXT document attribute that starts with '%.*ls' is too long. Maximumlength is %d.Attribute-centric IDREFS or NMTOKENS field not supported on tags havingelement-centric field '%.*ls' of type TEXT/NTEXT or IMAGE. Either specifyELEMENT on IDREFS/NMTOKENS field or remove the ELEMENT directive.FOR XML EXPLICIT does not support XMLTEXT field on tag '%.*ls' that hasIDREFS or NMTOKENS fields.XMLDATA does not support namespace elements or attributes such as '%.*ls'.Run the SELECT FOR XML statement without XMLDATA or remove thenamespace prefix declaration.Table 3–53:TSQL Error Codes - 7000 to 7099Error Code7000700170027003700470057006700770087009DescriptionOPENXML document handle parameter must be of data type int.OPENXML flags parameter must be of data type int.OPENXML XPath must be of a string data type, such as nvarchar.Only one OPENXML column can be of type %ls.OPENXML does not support retrieving schema from remote tables, as in '%.*ls'.OPENXML requires a metaproperty namespace to be declared if 'mp' is used foranother namespace in sp_xml_preparedocument.OPENXML encountered a problem identifying the metaproperty namespace prefix.Consider removing the namespace parameter from the correspondingsp_xml_preparedocument statement.OPENXML encountered unknown metaproperty '%.*ls'.The OPENXML EDGETABLE is incompatible with the XMLTEXT OVERFLOWflag.OPENXML allows only one metaproperty namespace prefix declaration insp_xml_preparedocument.Table 3–54:TSQL Error Codes - 7100 to 7199Error Code7101710271037104DescriptionYou cannot use a text pointer for a table with option 'text in row' set to ON.SQL Server Internal Error. Text manager cannot continue with current statement.You cannot set option 'text in row' for table %s.Offset or size type is invalid. Must be int or smallint data type.Caché Error Reference 149
Page 3 and 4:
Table of Contents1 General Error Me
Page 5 and 6:
Table 3-15: TSQL Error Codes - 1600
Page 7 and 8:
1General Error MessagesThis documen
Page 9 and 10:
General Error MessagesError Code686
Page 11 and 12:
Page 13 and 14:
Page 15 and 16:
Page 17 and 18:
Page 19 and 20:
Page 21 and 22:
General Error MessagesTable 1-5: Ge
Page 23 and 24:
Page 25 and 26:
Page 27 and 28:
Page 29 and 30:
Page 31 and 32:
Page 33 and 34:
Page 35 and 36:
Page 37:
Page 40:
Page 44 and 45:
Page 46 and 47:
Page 48 and 49:
Page 50 and 51:
Page 52 and 53:
Page 54 and 55:
Page 56 and 57:
Page 58 and 59:
Page 60 and 61:
Page 62 and 63:
Page 64 and 65:
Page 66 and 67:
Page 68 and 69:
Page 70 and 71:
Page 72 and 73:
Page 74 and 75:
Page 76 and 77:
Page 78 and 79:
Page 80 and 81:
Page 82 and 83:
Page 84 and 85:
General Error MessagesTable 1-28: M
Page 86 and 87:
SQL Error MessagesThe message texts
Page 88 and 89:
SQL Error MessagesError Code-47-48-
Page 90 and 91:
SQL Error MessagesError Code-109-11
Page 92 and 93:
Page 94 and 95:
Page 96 and 97:
TSQL Error MessagesError Code114116
Page 98 and 99:
Page 100 and 101:
Page 102 and 103:
TSQL Error MessagesTable 3-5:TSQL E
Page 104 and 105: TSQL Error MessagesError Code515516
Page 112 and 113: TSQL Error MessagesTable 3-13:TSQL
Page 176 and 177: TSQL Error MessagesError Code8999De
Page 204 and 205:
Page 206 and 207:
Page 208 and 209:
Page 210 and 211:
Page 212 and 213:
TSQL Error MessagesTable 3-82:TSQL
Page 214 and 215:
Page 216 and 217:
Page 218 and 219:
Page 220 and 221:
Page 222 and 223:
Page 224 and 225:
Page 226 and 227:
Page 228 and 229:
TSQL Error MessagesError Code20100D
Page 230 and 231:
Page 232 and 233:
Page 234 and 235:
Page 236 and 237:
Page 238 and 239:
Page 240 and 241:
Page 242 and 243:
Page 244 and 245:
Page 246 and 247:
Page 248 and 249:
Page 251 and 252:
4System Error MessagesThis document
Page 253 and 254:
General System Error MessagesError
Page 255 and 256:
Page 257 and 258:
Page 259 and 260:
Page 261 and 262:
M Programming Language Errors4.3 M
Page 263:
IndexSSQLCODE, 79SQLCODE values, 79
show all

General Error Messages - InterSystems Documentation

You also want an ePaper? Increase the reach of your titles

Delete template?

Save as template?