![[BACK]](/cvsweb/icons/back.gif){kind=icon}
Return to 05dbu.nr CVS log ![[TXT]](/cvsweb/icons/text.gif){kind=icon}
![[DIR]](/cvsweb/icons/dir.gif){kind=icon}
Up to [CSRG BSD Unix] / 42BSD / ingres / doc / error|
Return to 05dbu.nr CVS log | Up to [CSRG BSD Unix] / 42BSD / ingres / doc / error |
1.1 root 1: .th DBU ERROR 3/30/79
2: .sh NAME
3: Data Base Utility error message summary
4: .sh SYNOPSIS
5: Error numbers 5000 \- 5999
6: .sh DESCRIPTION
7: The Data Base Utility functions
8: perform almost all tasks
9: which are not directly associated
10: with processing queries.
11: The error messages which they can generate
12: result from some syntax checking
13: and a considerable amount of semantic checking.
14: .sh ERRORS
15: .lp +8 8
16: 5001 PRINT: bad relation name %0
17: .s3
18: You are trying to print a relation which doesn't exist.
19: .s3
20: .lp +8 8
21: 5002 PRINT: %0 is a view and can't be printed
22: .s3
23: The only way to print a view
24: is by retrieving it.
25: .s3
26: .lp +8 8
27: 5003 PRINT: Relation %0 is protected.
28: .s3
29: You are not authorized to access this relation.
30: .s3
31: .lp +8 8
32: 5102 CREATE: duplicate relation name %0
33: .s3
34: You are trying to create a relation which already exists.
35: .s3
36: .lp +8 8
37: 5103 CREATE: %0 is a system relation
38: .s3
39: You cannot create a relation with the same name as a system relation.
40: The
41: system depends on the fact that the system relations are unique.
42: .s3
43: .lp +8 8
44: 5104 CREATE %0: invalid attribute name %1
45: .s3
46: This will happen if you try to create a relation with an attribute longer
47: than 12 characters.
48: .s3
49: .lp +8 8
50: 5105 CREATE %0: duplicate attribute name %1
51: .s3
52: Attribute names in a relation must be unique.
53: You are trying to create one
54: with a duplicated name.
55: .s3
56: .lp +8 8
57: 5106 CREATE %0: invalid attribute format "%2" on attribute %1
58: .s3
59: The allowed formats for a domain are c1\-c255, i1, i2, i4, f4 and f8.
60: Any other
61: format will generate this error.
62: .s3
63: .lp +8 8
64: 5107 CREATE %0: excessive domain count on attribute %1
65: .s3
66: A relation cannot have more than 49 domains.
67: The origin of this magic number
68: is obscure.
69: This is very difficult to change.
70: .s3
71: .lp +8 8
72: 5108 CREATE %0: excessive relation width on attribute %1
73: .s3
74: The maximum number of bytes allowed in a tuple is 1010.
75: This results from the
76: decision that a tuple must fit on one \*(UU "page".
77: Assorted pointers
78: require the 14 bytes which separates 1010 from 1024.
79: This "magic number" is
80: very hard to change.
81: .s3
82: .lp +8 8
83: 5201 DESTROY: %0 is a system relation
84: .s3
85: The system would immediately stop working if you were allowed to do this.
86: .s3
87: .lp +8 8
88: 5202 DESTROY: %0 does not exist or is not owned by you
89: .s3
90: To destroy a relation,
91: it must exist,
92: and you must own it.
93: .s3
94: .lp +8 8
95: 5203 DESTROY: %0 is an invalid integrity constraint identifier
96: .s3
97: Integers given do not identify integrity constraints on the specified relation.
98: For example: If you were to type "destroy permit parts 1, 2, 3",
99: and 1, 2, or 3 were not the numbers "help permit parts"
100: prints out for permissions on parts, you would get this error.
101: .s3
102: .lp +8 8
103: 5204 DESTROY: %0 is an invalid protection constraint identifier
104: .s3
105: Integers given do not identify protection constraints on the specified relation.
106: Example as for error 5203.
107: .s3
108: .lp +8 8
109: 5300 INDEX: cannot find primary relation
110: .s3
111: The relation does not exist \- check your spelling.
112: .s3
113: .lp +8 8
114: 5301 INDEX: more than maximum number of domains
115: .s3
116: A secondary index can be created on at most six domains.
117: .s3
118: .lp +8 8
119: 5302 INDEX: invalid domain %0
120: .s3
121: You have tried to create an index
122: on a domain which does not exist.
123: .s3
124: .lp +8 8
125: 5303 INDEX: relation %0 not owned by you
126: .s3
127: You must own relations
128: to put indicies on them.
129: .s3
130: .lp +8 8
131: 5304 INDEX: relation %0 is already an index
132: .s3
133: \*(II does not permit tertiary indicies.
134: .s3
135: .lp +8 8
136: 5305 INDEX: relation %0 is a system relation
137: .s3
138: Secondary indices cannot be created on system relations.
139: .s3
140: .lp +8 8
141: 5306 INDEX: %0 is a view and an index can't be built on it
142: .s3
143: Since views are not physically stored
144: in the database,
145: you cannot build indicies on them.
146: .s3
147: .lp +8 8
148: 5401 HELP: relation %0 does not exist
149: .s3
150: .lp +8 8
151: 5402 HELP: cannot find manual section "%0"
152: .s3
153: Either the desired manual section does not exist,
154: or your system does not have any on-line documentation.
155: .s3
156: .lp +8 8
157: 5403 HELP: relation %0 is not a view
158: .s3
159: Did a "help view" (which prints view definition) on a nonview.
160: For example: "help view overpaidv" prints out overpaidv's view definition.
161: .s3
162: .lp +8 8
163: 5404 HELP: relation %0 has no permissions on it granted
164: .lp +8 8
165: 5405 HELP: relation %0 has no integrity constraints on it
166: .s3
167: You have tried to print the permissions
168: or integrity constraints
169: on a relation
170: which has none specified.
171: .s3
172: .lp +8 8
173: 5410 HELP: tree buffer overflowed
174: .lp +8 8
175: 5411 HELP: tree stack overflowed
176: .s3
177: Still more buffer overflows.
178: .s3
179: .lp +8 8
180: 5500 MODIFY: relation %0 does not exist
181: .s3
182: .lp +8 8
183: 5501 MODIFY: you do not own relation %0
184: .s3
185: You cannot modify
186: the storage structure
187: of a relation you do not own.
188: .s3
189: .lp +8 8
190: 5502 MODIFY %0: you may not provide keys on a heap
191: .s3
192: By definition,
193: heaps do not have keys.
194: .s3
195: .lp +8 8
196: 5503 MODIFY %0: too many keys provided
197: .s3
198: You can only have
199: 49
200: keys on any relation.
201: .s3
202: .lp +8 8
203: 5504 MODIFY %0: cannot modify system relation
204: .s3
205: System relations can only be modified
206: by using the
207: .it sysmod
208: command to the shell;
209: for example
210: .s3
211: sysmod
212: .it dbname
213: .s3
214: .lp +8 8
215: 5507 MODIFY %0: duplicate key "%1"
216: .s3
217: You may only specify a domain as a key once.
218: .s3
219: .lp +8 8
220: 5508 MODIFY %0: key width (%1) too large for isam
221: .s3
222: When modifying a relation to isam, the sum of the
223: width of the key fields cannot exceed 245 bytes.
224: .s3
225: .lp +8 8
226: 5510 MODIFY %0: bad storage structure "%1"
227: .s3
228: The valid storage structure names are heap, cheap, isam,
229: cisam, hash, and chash.
230: .s3
231: .lp +8 8
232: 5511 MODIFY %0: bad attribute name "%1"
233: .s3
234: You have specified an attribute
235: that does not exist
236: in the relation.
237: .s3
238: .lp +8 8
239: 5512 MODIFY %0: "%1" not allowed or specified more than once
240: .s3
241: You have specified a parameter
242: which conflicts with another parameter,
243: is inconsistant with the storage mode,
244: or which has already been specified.
245: .s3
246: .lp +8 8
247: 5513 MODIFY %0: fillfactor value %1 out of bounds
248: .s3
249: .it Fillfactor
250: must be between 1 and 100 percent.
251: .s3
252: .lp +8 8
253: 5514 MODIFY %0: minpages value %1 out of bounds
254: .s3
255: .it Minpages
256: must be greater than zero.
257: .s3
258: .lp +8 8
259: 5515 MODIFY %0: "%1" should be "fillfactor", "maxpages", or "minpages"
260: .s3
261: You have specified an unknown parameter
262: to
263: .it modify.
264: .s3
265: .lp +8 8
266: 5516 MODIFY %0: maxpages value %1 out of bounds
267: .s3
268: .lp +8 8
269: 5517 MODIFY %0: minpages value exceeds maxpages value
270: .s3
271: .lp +8 8
272: 5518 MODIFY %0: invalid sequence specifier "%1" for domain %2.
273: .s3
274: Sequence specifier may be ``ascending''
275: (or ``a'')
276: or ``descending''
277: (or ``d'')
278: in a
279: .it modify.
280: For example:
281: .s3
282: .nf
283: modify parts to heapsort on
284: pnum:ascending,
285: pname:descending
286: .fi
287: .s3
288: .lp +8 8
289: 5519 MODIFY: %0 is a view and can't be modified
290: .s3
291: Only physical relations can be modified.
292: .s3
293: .lp +8 8
294: 5520 MODIFY: %0: sequence specifier "%1" on domain %2
295: is not allowed with the specified storage structure.
296: .s3
297: Sortorder may be supplied only when modifying to
298: .bd heapsort
299: or
300: .bd cheapsort.
301: .s3
302: .lp +8 8
303: 5600 SAVE: cannot save system relation "%0"
304: .s3
305: System relations have no save date and
306: are guaranteed to stay for the lifetime of the data base.
307: .s3
308: .lp +8 8
309: 5601 SAVE: bad month "%0"
310: .lp +8 8
311: 5602 SAVE: bad day "%0"
312: .lp +8 8
313: 5603 SAVE: bad year "%0"
314: .s3
315: This was a bad month, bad day, or maybe even a bad year
316: for \*(II.
317: .s3
318: .lp +8 8
319: 5604 SAVE: relation %0 does not exist or is not owned by you
320: .s3
321: .lp +8 8
322: 5800 COPY: relation %0 doesn't exist
323: .s3
324: .lp +8 8
325: 5801 COPY: attribute %0 in relation %1 doesn't exist
326: or it has been listed twice
327: .s3
328: .lp +8 8
329: 5803 COPY: too many attributes
330: .s3
331: Each dummy domain and real domain listed in the copy statement
332: count as one attribute.
333: The limit is 150 attributes.
334: .s3
335: .lp +8 8
336: 5804 COPY: bad length for attribute %0. Length="%1"
337: .s3
338: .lp +8 8
339: 5805 COPY: can't open file %0
340: .s3
341: On a copy "from", the file is not readable by the user.
342: .s3
343: .lp +8 8
344: 5806 COPY: can't create file %0
345: .s3
346: On a copy "into", the file is not creatable by
347: the user.
348: This is usually caused by the user not having write
349: permission in the specified directory.
350: .s3
351: .lp +8 8
352: 5807 COPY: unrecognizable dummy domain "%0"
353: .s3
354: On a copy "into", a dummy domain name is used to
355: insert certain characters into the unix file.
356: The domain name given is not valid.
357: .s3
358: .lp +8 8
359: 5808 COPY: domain %0 size too small for conversion.
360: .br
361: There were %2 tuples successfully copied from %3 into %4
362: .s3
363: When doing any copy except character to character,
364: copy checks that the field is large enough
365: to hold the value being copied.
366: .s3
367: .lp +8 8
368: 5809 COPY: bad input string for domain %0. Input was "%1".
369: There were %2 tuples successfully copied from %3 into %4
370: .s3
371: This occurs when converting character strings to
372: integers or floating point numbers.
373: The character string contains something other
374: than numeric characters (0-9,+,\*-,blank,etc.).
375: .s3
376: .lp +8 8
377: 5810 COPY: unexpected end of file while filling domain %0.
378: .br
379: There were %1 tuples successfully copied from %2 into %3
380: .s3
381: .lp +8 8
382: 5811 COPY: bad type for attribute %0. Type="%1"
383: .s3
384: The only accepted types are i, f, c, and d.
385: .s3
386: .lp +8 8
387: 5812 COPY: The relation "%0" has a secondary index.
388: The index(es) must be destroyed before doing a copy "from"
389: .s3
390: Copy cannot update secondary indices.
391: Therefore, a copy "from" cannot be done on an indexed relation.
392: .s3
393: .lp +8 8
394: 5813 COPY: You are not allowed to update the
395: relation %0
396: .s3
397: You cannot copy into a system relation or secondary index.
398: .s3
399: .lp +8 8
400: 5814 COPY: You do not own the relation %0.
401: .s3
402: You cannot use copy to update a relation
403: which you do not own.
404: A copy "into" is allowed but a copy "from" is not.
405: .s3
406: .lp +8 8
407: 5815 COPY: An unterminated "c0" field occurred while filling domain %0.
408: There were %1 tuples successfully copied from %2 into %3
409: .s3
410: A string read on a copy "from" using the
411: "c0" option cannot be longer than 1024 characters.
412: .s3
413: .lp +8 8
414: 5816 COPY: The full pathname must be specified for
415: the file %0
416: .s3
417: The file name for copy must start with a "/".
418: .s3
419: .lp +8 8
420: 5817 COPY: The maximum width of the output file cannot
421: exceed 1024 bytes per tuple
422: .s3
423: The amount of data to be output
424: to the file for each tuple exceeds
425: 1024.
426: This usually happens only if a format was
427: mistyped or a lot of large
428: dummy domains were specified.
429: .s3
430: .lp +8 8
431: 5818 COPY: %0 is a view and can't be copied
432: .s3
433: Only physical relations
434: can be copied.
435: .s3
436: .lp +8 8
437: 5819 COPY: Warning: %0 duplicate tuples were ignored.
438: .s3
439: On a copy "from", duplicate tuples were present in the relation.
440: .s3
441: .lp +8 8
442: 5820 COPY: Warning: %0 domains had control characters
443: which were converted to blanks.
444: .s3
445: .lp +8 8
446: 5821 COPY: Warning: %0 c0 character domains were truncated.
447: .s3
448: Character domains in c0 format are of the same length as the
449: domain length. You had a domain value greater than this
450: length, and it was truncated.
451: .s3
452: .lp +8 8
453: 5822 COPY: Relation %0 is protected.
454: .s3
455: You are not authorized to access this relation.
This archive runs on limited infrastructure. Preserving old code on modern bandwidth. Automated agents are requested to crawl responsibly.