Error codes 500 - 599

Indicates a duplicate server.

A Linux (Unix) server needs to create or take over /tmp/ctreedbs for shared memory on server startup. This error will be returned if this folder already exists, but the current server doesn't have permission to take it over - or if you launch the server under one user, then move it to another user.

To correct this, remove the folder, or launch the server with SUDO so it can take it over.

Indicates index logical EOF error.

The index end of file error gives warning when a B-tree index node appears to be past the logical end of the index file. Such an error indicates that the index is corrupted. Note the following points:

Indicates the index must be rebuilt. See CTSTATUS.FCS.

In V11.0 you can get this error trying to rebuild. A check was incorrectly returning this error; this was fixed in V11.5.

Indicates client does not match server.

There are some incompatibilities between certain versions of our client library and versions of our server, i.e. V7 clients can't connect to a V8 or later server.

Indicates transaction log collision.

FairCom DB is having trouble getting and locking the log files. It is possible the drive is full.

In some cases, this error will be seen if the logs can’t be created. Check CTSTATUS.FCS for additional information if the creation of transaction logs fails.

Indicates NULL parameter.

One or more of the required parameters passed to one of our functions was null.

Indicates an attempt to add a record beginning with either a delete flag (0xFF) or a resource mark (0xFEFE) failed.

This capability can be disabled as follows:

Indicates inconsistent SerialNum definition info.

You can get this error if you are trying to add a serial index segment (auto increment) to a file that doesn't have one. These have to be defined when the file is created.

It is inappropriate (regardless of partitioned files or not) to use PRMIIDX to add indexes that use SRLSEG if SRLSEG based indexes do not already exist. First, a SRLSEG index requires space in the data record. Second, none of the existing records would have SRLSEG data already in place, even if space had been reserved. ISRL_ERR (554) is returned when PRMIIDX attempts to add indexes with SRLSEG when SRLSEG has not already been used.

SYSMON: dynamic dump ends (due to errors).

At the end of automatic recovery, the following conditions (errors 570-576) may be detected which require cleanup before continuing. The specifics are reported in CTSTATUS.FCS:

Indicates context ID exists.

If you are getting this returned from a c-treeDB function to get a record, you have started 32,728 simultaneous c-treeDB contexts and their context ID wrapped.

To correct this, change your code to lower the number of contexts going at the same time. You should also clear and reuse c-treeDB Table, or Record handles within a loop and not allocate ones.