Error codes 600 - 799

Indicates IIDX attributes do not match file.

To correct this, rebuild the indexes.

In V11.0 you can incorrectly get this error trying to rebuild, though this was fixed in V11.5.

Indicates negative length specified.

A length parameter passed to one of our functions was negative when a positive value was required.

Indicates duplicate keys purged and logged.

During an index rebuild, duplicates were found for unique indexes and auto removal of duplicates was specified. This means records were removed.

Indicates duplicate keys rejected and listed.

An index rebuild failed because duplicate records were found for a unique index.

To correct this, examine the duplicate file to see what records are involved. Remove one manually or turn on auto removal of duplicate records.

Indicates incompatible log format. See FREL_ERR (744). 

Certain versions introduce an incompatibility in the log file format:

This error is returned if you try to open a database from a previous version that has open log files, (i.e. was not shut down cleanly) with a new enough version.

To correct this, go back to the old version and achieve a clean shutdown, or remove the log files (this will lose some transactions).

This error can also be returned when restoring a dump from V7 with V8 utilities. To avoid it, restore a V7 dump with V7 ctrdmp, ctfdmp and then open with V8.

Indicates an inconsistency between file attr & sys version.

This error can be returned when trying to open an old table with a new server (i.e. a pre-V7 file on a V11.5 server), or when trying to open a bigendian database on a littleendian server or vice versa.

Indicates additional file segments needed.

This error can be returned due to one of the following:

To correct this, Add DIAGNOSTICS TRAN_RECOVERY (if it's a V10 or newer server) to find out which file is causing the problem.

Indicates 1st & 2nd headers out of sync.

You can get this error if you revert the .dat files to an older copy but keep the newer logs.

Indicates invalid source type.

You can get this error in V11.5 / V11.6 by creating a fixed-length table with the only variable set to auto timestamp.

Indicates bad parameter value.

You can get this error trying to enable a server keyword dynamically that can only be enabled by taking down the server and editing the .cfg file. Not all keywords can be turned on dynamically.

This error has been seen from a bad FAIRCOM.FCS file that had become corrupt.

Indicates fixed length record offset not aligned.

In V11.5 an later, this error will be returned if you are attempting to write to a fixed-length file offset that does not match a field boundary. You can turn this off with COMPATIBILITY NO_FIXED_OFFSET_CHECK.

Indicates no UNQKEY support for REPLICATION.

If a low-level file open call that requests write access to a FairCom DB data file fails with this error, it is because the data file has replication enabled. A FairCom DB data file that has replication enabled can only be opened for write access at the ISAM level. A read-only low-level call is allowed: use the ctREADFIL | ctSHARED filemodes when opening the file in addition to the other filemode options that you are using.

This is a copy of a replicated database and you are trying to do something to it that can't be done under replication. If you are opening it single user, use the command-line util to reset the replication flag. Technically removing the indexes and rebuilding them will also update the file header and turn off the replication flag.

Indicates external server shutdown disabled.

If replication is running on a server, it should be stopped before trying to stop the server.

Indicates an attempt to update data with missing key buffer constraints.

This error is returned when deleting a record with v-length portion when the current FairCom DB record was loaded with LoadRec() instead of LoadVRec(). This was introduced with c-tree V8.