The internal error codes in the 200-240 range should not occur during the proper operation of FairCom DB. Their main function is to help find programming bugs, especially if you modify FairCom DB code. Experience shows that almost all occurrences of an internal error are caused by memory overwrites from the application code.
Table 1. Error codes 200 - 240: internal errors
| Value | Description |
|---|---|
| 200 | Indicates neither LOW_HIGH nor HIGH_LOW are defined in ctoptn.h. |
| 201 | Indicates LOW_HIGH and HIGH_LOW are both defined in ctoptn.h. |
| 202 | Indicates NOTFORCE, FPUTONLY, and FPUTFGET are not defined in ctoptn.h. |
| 203 | Indicates more than one of NOTFORCE, FPUTONLY, and FPUTFGET are defined in ctoptn.h. |
| 206 | Indicates there is an update flag inconsistency between the index file header and the buffer status information. |
| 207 | Indicates a corrupt node was found in the nodser() function. |
| 208 | Indicates there is an updated (but not written) node found in the FPUTFGET disk I/O mode. |
| 210 | Indicates an undefined key type was found in compar. |
| 211 | Indicates there is a negative number of key values indicated in node. |
| 212 | Indicates there was no leaf node found during the FirstKey() operation. |
| 213 | Indicates there was no leaf node found during the LastKey() operation. |
| 214 | Indicates a corrupt tree was found in fndkey(). |
| 215 | Indicates there is no leaf node found in fndkey(). |
| 216 | Indicates there was an attempt to save node with a negative number of key values. |
| 217 | Indicates there was an attempt to transfer key values between buffers for different index files. |
| 218 | Indicates a corrupt tree was found. |
| 219 | Indicates no leaf node was found. |
| 220 | Indicates a corrupt tree was found. |
| 221 | Indicates no leaf node was found. |
| 222 | Indicates an undefined file access flag found. filacs member of the file control structure must be set to ‘y’ (active), ‘v’ (active, temporarily closed), or ‘n’ (inactive). |
| 225 | Indicates VARLDATA is not defined in ctoptn.h. You can add a VARLDATA option and recompile ctaddk.c. |
| 226 | Indicates an undefined key segment translation mode. |
| 227 | Indicates the delete flags could not be written into new (but unused) records at the end of the file while extending the size of a fixed-length data file. |
| 228 | Indicates an expected deleted record mark could not be found while collapsing consecutive deleted areas. |
| 230 | Indicates the b-Tree node has a conflicting member number value during write operation. |
| 231 | Indicates the b-tree node has a conflicting member number value during read operation. |
| 232 | Indicates there was an attempt to expand a non-existent compressed key value. |
| 233 | Indicates an illegal value for key compression bytes. |
| 235 | Indicates an illegal comparison value during a node insert. |
| 236 | Indicates an illegal key value shift was detected with compressed keys. |
| 237 | Indicates there was an attempt to get an index node at byte offset zero. |
| 238 | Indicates an illegal key value shift has been detected with compressed keys. |
| 239 | Indicates the variable key expansion request is with NO_VARLK. |
| 240 |
Indicates the maximum b-tree levels were exceeded. You can increase the number or size of node sectors or increase MAXLEV. In standalone models this could be a symptom of adding index entries sequentially, creating a badly balanced tree. You can compact the index, or shift to a client/server model. |