Skip to main content

Error codes 17600 - 17699

FairCom SQL error codes 17600 - 17699

Abstract

FairCom SQL error codes 17600 - 17699

Table 1. SQL errors 17600 - 17697: FSS

Error code

SQLSTATE value

Class condition

Subclass message

17600

00600

FairCom DB FSS error

CT - No more client threads

17601

00601

FairCom DB FSS error

CT - ctVERIFY detected problems with idx

17602

00602

FairCom DB FSS error

CT - No memory for system lock table

17603

00603

FairCom DB FSS error

CT - Could not allocate FCB

17604

00604

FairCom DB FSS error

CT - Could not increase user files

17605

00605

FairCom DB FSS error

CT - Records with bad (all FF) serial #s

17606

00606

FairCom DB FSS error

CT - Could not handle file encoding

17607

00607

FairCom DB FSS error

CT - Recovery could not enable encoding

17608

00608

FairCom DB FSS error

CT - IIDX attributes do not match file

17609

00609

FairCom DB FSS error

CT - one-use temp password failure

17610

00610

FairCom DB FSS error

CT - CTHIST targetNULL

17611

00611

FairCom DB FSS error

CT - CTHIST could not access log

17612

00612

FairCom DB FSS error

CT - CTHIST must be called with ctHISTfirst

17613

00613

FairCom DB FSS error

CT - CTHIST can only access data or index

17614

00614

FairCom DB FSS error

CT - No valid ISAM map from index to data

17615

00615

FairCom DB FSS error

CT - Cannot get index info from data filno

17616

00616

FairCom DB FSS error

CT - CTHIST cannot be called during a tran

17617

00617

FairCom DB FSS error

CT - Did not find target

17618

00618

FairCom DB FSS error

CT - Log scan terminated - EOF or bad entry

17619

00619

FairCom DB FSS error

CT - CTHIST on data file - recbyt0

17620

00620

FairCom DB FSS error

CT - bufsiz too small

17621

00621

FairCom DB FSS error

CT - Transaction type not expected

17622

00622

FairCom DB FSS error

CT - Must reset CTHIST first

17623

00623

FairCom DB FSS error

CT - Not enough memory for CTHIST

17624

00624

FairCom DB FSS error

CT - Net change only applies to specific match of key or record position

17625

00625

FairCom DB FSS error

CT - Must specify exactly one matching criteria (user & node may be combined)

17626

00626

FairCom DB FSS error

CT - Encountered an UNDTRAN going forward must completely restart this CTHIST sequence

17627

00627

FairCom DB FSS error

CT - Unknown type of request

17628

00628

FairCom DB FSS error

CT - Must specify filno

17629

00629

FairCom DB FSS error

CT - Could not initialize internal file ID

17630

00630

FairCom DB FSS error

CT - Unexpected length in log entry

17631

00631

FairCom DB FSS error

CT - Could not get SS_LOCK on file

17632

00632

FairCom DB FSS error

CT - User lost locks found on close

17633

00633

FairCom DB FSS error

CT - Null plen (pointer to size)

17634

00634

FairCom DB FSS error

CT - Negative length specified

17635

00635

FairCom DB FSS error

CT - Could not create thread sync object

17636

00636

FairCom DB FSS error

CT - Thread sync object ‘get’ failed

17637

00637

FairCom DB FSS error

CT - Thread sync object ‘rel’ failed

17638

00638

FairCom DB FSS error

CT - Queue message truncated to fit

17639

00639

FairCom DB FSS error

CT - Semaphore must be init with count>0

17640

00640

FairCom DB FSS error

CT - Semaphore already initialized

17641

00641

FairCom DB FSS error

CT - Thread sync object ‘cls’ failed

17642

00642

FairCom DB FSS error

CT - Must use exact file name

17643

00643

FairCom DB FSS error

CT - Accessing a file pending delete

17644

00644

FairCom DB FSS error

CT - Reversible TRANDEP delete

17645

00645

FairCom DB FSS error

CT - File number changed after deferred close

17646

00646

FairCom DB FSS error

CT - Superfile member/host TRANDEP specification conflict

17647

00647

FairCom DB FSS error

CT - No support above 2GB

17648

00648

FairCom DB FSS error

CT - No support above 4GB

17650

00650

FairCom DB FSS error

CT - Duplicate keys purged and logged

17651

00651

FairCom DB FSS error

CT - Could not process dup key log

17652

00652

FairCom DB FSS error

CT - Duplicate keys rejected and listed

17653

00653

FairCom DB FSS error

CT - Attempt to exceed mapped lock limit

17654

00654

FairCom DB FSS error

CT - Record length too long for log size

17655

00655

FairCom DB FSS error

CT - Could not reopen using freopen

17656

00656

FairCom DB FSS error

CT - Transaction log header is bad

17657

00657

FairCom DB FSS error

CT - Could not create copy file

17658

00658

FairCom DB FSS error

CT - Could not write copy file

17659

00659

FairCom DB FSS error

CT - Could not read entire original file

17660

00660

FairCom DB FSS error

CT - rbld complete, but failed mirror copy

17661

00661

FairCom DB FSS error

CT - Failed process dup log and copy mirror

17662

00662

FairCom DB FSS error

CT - dup purged, but could not copy mirror

17663

00663

FairCom DB FSS error

CT - dup rejected, but could not copy mirror

17664

00664

FairCom DB FSS error

CT - Primary log (or start) file failed

17665

00665

FairCom DB FSS error

CT - Mirrored log (or start) file failed

17666

00666

FairCom DB FSS error

CT - Incompatible log format

17667

00667

FairCom DB FSS error

CT - Attempt to exceed max file size

17668

00668

FairCom DB FSS error

CT - Large page size not a multiple of 16K

17669

00669

FairCom DB FSS error

CT - Inconsistent XCREblk

17670

00670

FairCom DB FSS error

CT - Node sectors too small for huge file

17671

00671

FairCom DB FSS error

CT - Non-zero high long with non-huge file

17672

00672

FairCom DB FSS error

CT - Inconsistency between xflmod & x8hdr

17673

00673

FairCom DB FSS error

CT - Extended header bad signature

17674

00674

FairCom DB FSS error

CT - Additional file segments needed

17675

00675

FairCom DB FSS error

CT - File segments not supported

17676

00676

FairCom DB FSS error

CT - Could not open segment

17677

00677

FairCom DB FSS error

CT - Cannot directly operate on seg def

17678

00678

FairCom DB FSS error

CT - Bad file segment name

17679

00679

FairCom DB FSS error

CT - Bad file segment size

17680

00680

FairCom DB FSS error

CT - Could not create file segment

17681

00681

FairCom DB FSS error

CT - Could not process segment header

17682

00682

FairCom DB FSS error

CT - seg resource cannot move

17683

00683

FairCom DB FSS error

CT - seg update invalid, see CTSTATUS.FCS

17684

00684

FairCom DB FSS error

CT - Segment update already in progress

17685

00685

FairCom DB FSS error

CT - I/O on segmented file terminated

17686

00686

FairCom DB FSS error

CT - Segment definition too large

17687

00687

FairCom DB FSS error

CT - Unexpected value during recovery

17688

00688

FairCom DB FSS error

CT - Pending segment mismatch

17689

00689

FairCom DB FSS error

CT - 1st & 2nd headers out of sync

17690

00690

FairCom DB FSS error

Bad request header CheckSum

17691

00691

FairCom DB FSS error

Bad response header CheckSum

17692

00692

FairCom DB FSS error

Bad request (to server), CRC error

The field handle has failed a CRC check and is likely corrupted.

Suggested fix: If the internal fields of a c-treeDB handle are modified outside of FairCom code, we will return this error and refuse to use the handle. Double-check that the c-treeDB handle is not modified by your code or affected by buffer overruns.

17693

00693

FairCom DB FSS error

Bad response (from server) CRC

17694

00694

FairCom DB FSS error

No Unicode support

17695

00695

FairCom DB FSS error

Could not get work buffer for blk I/O

17696

00696

FairCom DB FSS error

OPNFIL called for a segment

17697

00697

FairCom DB FSS error

Could not allocate encoding buff