Product Documentation

Knowledgebase

Previous Topic

Next Topic

2xx Internal Error Codes

The internal error codes in the 2xx range should not occur during 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.

200

Neither LOW_HIGH nor HIGH_LOW defined in ctoptn.h.

201

Both LOW_HIGH and HIGH_LOW defined in ctoptn.h.

202

NOTFORCE, FPUTONLY, nor FPUTFGET defined in ctoptn.h.

203

More than one of NOTFORCE, FPUTONLY, and FPUTFGET defined in ctoptn.h.

206

Update flag inconsistency between index file header and buffer status information.

207

Corrupt node found in nodser() function.

208

Updated (but not written) node found in FPUTFGET disk I/O mode.

210

Undefined key type found in compar.

211

Negative number of key values indicated in node.

212

No leaf node found during FirstKey() operation.

213

No leaf node found during LastKey() operation.

214

Corrupt tree found in fndkey().

215

No leaf node found in fndkey().

216

Attempt to save node with negative number of key values.

217

Attempt to transfer key values between buffers for different index files.

218

Corrupt tree found in .

219

No leaf node found in .

220

Corrupt tree found in .

221

No leaf node found in .

222

Undefined file access flag found: filacs member of file control structure must be set ‘y’ (active), ‘v’ (active, temporarily closed), or ‘n’ (inactive).

225

VARLDATA not defined in ctoptn.h. Add VARLDATA option and recompile ctaddk.c.

226

Undefined key segment translation mode.

227

While extending the size of a fixed-length data file, delete flags could not be written into new (but unused) records at the end of the file.

228

Expected deleted record mark not found while collapsing consecutive deleted areas.

230

B-Tree node has conflicting member number value during write operation.

231

B-tree node has conflicting member number value during read operation.

232

Attempt to expand non-existent compressed key value.

233

Illegal value for key compression bytes.

235

Illegal comparison value during node insert.

236

Illegal key value shift detected with compressed keys.

237

Attempt to get an index node at byte offset zero.

238

Illegal key value shift detected with compressed keys.

239

Variable key expansion request with NO_VARLK.

240

Exceeded maximum b-tree levels. Increase number or size of node sectors, or increase MAXLEV. In standalone models, may be a symptom of adding index entries sequentially, creating a badly balanced tree. Compact the index or shift to a client/server model.

TOCIndex