FairCom error codes 1000 - 1299
Value | Symbolic constant | Description | |||||||||
|---|---|---|---|---|---|---|---|---|---|---|---|
1000 | IDFL_MOD | Indicates the specified identity field mode could not be enabled due to a conflicting mode that is already in effect. For example, identity field override and identity field preservation are mutually exclusive. | |||||||||
1001 | NOISMKEYUPD_ERR | Indicates the specified key value could not be updated because this index does not allow an ISAM record update to change the key value. | |||||||||
1002 | IDVR_ERR | Indicates IDfield overflows (or underflows if delta is negative). | |||||||||
1003 | IDXA_ERR | Indicates Invalid IDfield extended attribute (xtdatr). sysiocod indicates the validation issue:
| |||||||||
1004 | IBLK_ERR | Indicates file is temporarily blocked from being opened by an internal thread. | |||||||||
1005 | SINT_ERR | Indicates system-dependent initialization failed, see CTSTATUS.FCS for details. | |||||||||
1006 | COFL_ERR | Indicates all co-file opens for a given file by the same thread must agree on the ctXOPN_COFILE_FILELOCK attribute. | |||||||||
1007 | COFS_ERR | Indicates SUPERFILE hosts cannot be opened as co-files (i.e., same SUPERFILE cannot be opened by the same user with different file numbers). When members of a SUPERFILE are opened, the open request does not use the SUPERFILE host user file number. | |||||||||
1008 | COFP_ERR | Indicates Partition Hosts cannot be opened as co-files (i.e., same Partition Host cannot be opened by the same user with different file numbers). | |||||||||
-1009 | COFL_COD | Indicates special internal file open cannot use ctXOPN_COFILE_FILELOCK attribute. | |||||||||
1010 | DTPC_ERR | Indicates this file uses data types that your client library does not support. Update your client library. | |||||||||
1011 | DTPS_ERR | Indicates this client library uses data type support that your server does not support. Update your FairCom DB server. | |||||||||
1012 | SCRIT_STATE_ERR | Indicates the Shared Critical has an unexpected internal state. | |||||||||
1013 | SCPY_ERR | Indicates the file copy API function does not allow copying a FairCom system file. | |||||||||
1014 | DCPY_ERR | Indicates the source data and index files must reside in one directory when using the file copy API option to copy files to a new directory. | |||||||||
1015 | CBKTRM_ERR | Indicates a user-defined callback function terminated the operation. | |||||||||
1016 | GFSZ_ERR | Indicates error getting file size. Check sysiocod for system error code value. | |||||||||
1017 | FDIF_ERR | Indicates the file comparison detected differences between the two files. | |||||||||
1018 | XPND_ERR | Indicates the specified operation cannot be completed because an index exists that has not yet been made permanent. To correct this, physically close the data file so that the index can be made permanent. | |||||||||
1019 | TUXP_ERR | Indicates transaction log entry has valid transaction type but unexpected contents. | |||||||||
1020 | NORP_ERR | Indicates DELAYED_DURABILITY on at time of system crash, and RECOVER_TO_RESTORE_POINT YES entry in configuration at time of automatic recovery, and no active restore points. To avoid NORP_ERR, and recovery without a rollback to the last active restore point, enter RECOVER_TO_RESTORE_POINT NO in the configuration. | |||||||||
1021 | NORB_ERR | Indicates DELAYED_DURABILITY on at time of system crash and active restore points exist, but no RECOVER_TO_RESTORE_POINT entry in configuration at time of automatic recovery. To avoid NORB_ERR, and recovery without a rollback to the last active restore point, enter RECOVER_TO_RESTORE_POINT NO in the configuration. To start up the server and rollback to the last active restore point, enter RECOVER_TO_RESTORE_POINT YES in the configuration. | |||||||||
1022 | XMLP_ERR | Indicates failure to parse the XML file. Check error message buffer for details. | |||||||||
1023 | XMLI_ERR | Indicates the XML document was successfully parsed, but an error occurred when interpreting the contents of the XML document. Check error message buffer for details. | |||||||||
-1024 | DLKT_COD | Indicates table lock could not be obtained because the table is locked, or a request to lock the table is pending, or a conflicting data record read or write lock exists. | |||||||||
1025 | TLOK_ERR | Indicates table lock could not be obtained because the table is locked, or a request to lock the table is pending, or a conflicting data record read or write lock exists. | |||||||||
1026 | REDT_ERR | Indicates table could not be updated because it is locked. | |||||||||
1027 | LWRP_ERR | Indicates Lightweight Restore Point cannot be used in this context — for example, as a Roll Forward target. | |||||||||
1028 | RPSK_ERR | Indicates the skip forward information stored in a Restore Point (during a recovery to a Restore Point) is inconsistent with the state of the log files during a subsequent roll forward operation. | |||||||||
-1029 | UPDM_COD | Indicates index node split has been deferred, the key marks cleaned up to the extent possible, and the add key will be retried. | |||||||||
1030 | MACT_ERR | Indicates maximum concurrent active connections exceeded. | |||||||||
1031 | QTFA_ERR | Indicates a call to ALCRNG() failed because improper options were specified. Check sysiocod for one of the following values:
| |||||||||
1032 | RBAD_ERR | Check sysiocod for one of the following values:
| |||||||||
-1033 | QREP_COD | Indicates sysiocod value when ctReplGetNextChange() returns NTIM_ERR and quiesce is waiting for replication readers to finish process committed transactions. | |||||||||
1034 | SEQFIL_ERR | Indicates the sequence file is not available because it could not be created or converted to the current format. Check CTSTATUS.FCS for error messages. | |||||||||
1035 | DFOP_ERR | Indicates a failure to parse output of DISK_FULL_ACTION script. | |||||||||
1036 | SEQNCR_ERR | Indicates the sequence was created with the requirement that ctGetNextSequenceValue() must be called before ctGetCurrentSequenceValue() is called. | |||||||||
1037 | SCHV_ERR | Indicates a failure to replicate a record add, delete, or update operation because the source record image contains a record schema ID that does not match the record schema ID in the target data file. | |||||||||
-1041 | RUCBDLL_NOT_LOADED_COD | Indicates sysiocod value when a file open succeeds even though the record update callback DLL was not loaded for data file. | |||||||||
-1042 | FORCE_BLOCKING_LOCK_COD | indicates sysiocod value set internally when a non-blocking lock request is forced to block. | |||||||||
-1043 | FILE_ALREADY_OPEN_COD | Indicates sysiocod value set when a caller requested to know that the file is already open. | |||||||||
1100 | WMEM_ERR | Indicates memory for HTTP server cannot be allocated. | |||||||||
1101 | WCRE_ERR | Indicates HTTP server cannot be created. | |||||||||
1102 | WCFG_ERR | Indicates HTTP config cannot be set. | |||||||||
1103 | COFM_ERR | Indicates the file cannot be opened because this connection already has it open the maximum number of times. | |||||||||
1104 | SSLCONN_ERR | Indicates SSL connection attempt failed. | |||||||||
1105 | REPCNF_ERR | Indicates a conflict was detected when applying a replicated record update. If you get this from the Replication Manager as an exception, it means there was a conflict. When it tried to apply the transaction, the target record didn't match the source record. This error has been seen after altering a replicated table and then adding data to the new field. The alter table didn't replicate so it couldn't apply the next transaction. Conflict Detection was defaulted to ON in V11.5 and later. Before that it would overwrite the record and ignore it. | |||||||||
1106 | HUPD_ERR | Indicates member index cannot be added to a ctTRNLOG host index because the host index has been updated. To correct this, physically close and reopen the host index, and then add the new member index. | |||||||||
1107 | DCPT_ERR | Indicates a Ctree Data file has corrupted data, and you must restore to a backup. A rebuild may be able to restore the file to a functional state with some data loss. | |||||||||
1108 | CTDR_ERR | Indicates a temporary directory cannot be created. Please refer to sysiocod in order to check the File System error code. | |||||||||
1109 | DTDR_ERR | Indicates a temporary directory cannot be deleted. Please refer to sysiocod in order to check the File System error code. | |||||||||
1110 | NTDR_ERR | Indicates no temporary directory. In order to be considered a temporary directory, it must be created by the ctTempDir() interface. | |||||||||
1111 | NORF_ERR | Indicates a restore point rollforward was requested, but the restore point checkpoint was not found in the transaction logs (the required transaction logs are not present). | |||||||||
-1112 | FFTI_COD | Indicates sysiocod value when the FNOP_ERR error is caused by missing FTI file(s). | |||||||||
1113 | FTIP_ERR | Indicates the full text index is not currently accessible due to index definition changes that are pending commit. To correct this, commit the current transaction before accessing the full text index. | |||||||||
1114 | NAUT_ERR | Indicates the FairCom RTG client is not authorized to connect to the server. Check license restrictions on allowed FairCom RTG clients. | |||||||||
1115 | ROSV_ERR | Indicates the operation was denied because the server is set in read-only mode. | |||||||||
1116 | PWDEXP_ERR | Indicates this user account has been disabled because its password has expired. | |||||||||
1117 | PWDLEN_ERR | Indicates the specified password does not meet the minimum length requirement. | |||||||||
1118 | PWDCLS_ERR | Indicates the specified password does not contain the required number of character classes. | |||||||||
1119 | RCVREN_ERR | During automatic recovery, this error code indicates that the specified file is not open, but a renamed version of it is open. This error code is used internally and does not necessarily indicate an error situation. | |||||||||
1120 | RCVTFL_ERR | Indicates automatic recovery failed due to an unexpected error mapping a transaction file number to a FairCom DB file number. | |||||||||
1121 | OPNSID_ERR | Indicates failure to open the specified file because its system file ID could not be read. Check sysiocod for system error code value. | |||||||||
1122 | JSON_KTFM_ERR | Indicates CT_JSON key transformation failed. Check sysicod for details, see CTJSON_* definitions. sysiocod values that may be returned in case of this error:
| |||||||||
1123 | QSVR_ERR | Indicates a FairCom DB client has attempted to use an incompatible system queue API on an older server. Update the FairCom DB server. For example, a V11.2.2 client can't connect to a V11.5 server and use the update queue. | |||||||||
1124 | QSVR_ERR | Indicates a FairCom DB client has attempted to use an incompatible system queue API on an older server. Update the FairCom DB server. | |||||||||
1125 | NICU_ERR | Indicates bad Unicode data detected. If malformed Unicode data is sent to our database engine, it can crash. This error was added to catch the data before it crashes the server. A SQL query can give this error and most likely will have terminated early; users must clean up the Unicode data and perform the query again to get the full result set. | |||||||||
1126 | BICU_ERR | Indicates an ICU error has occurred during a Unicode string conversion. | |||||||||
1127 | DSYN_ERR | Indicates dynamic dump script syntax error. | |||||||||
1128 | DNAM_ERR | Indicates file name too long. | |||||||||
1129 | FCYC_ERR | Indicates a file system loop or cycle has been encountered. | |||||||||
1130 | POPN_ERR | Indicates operation cannot be completed because the file is in a pending open state for the maximum number of pending open retries. These cases typically resolve themsolves with sufficient retries. If a bug occurs due to a pending file open operation never resolving, the symptom will be connections hanging rather than POPN_ERR. | |||||||||
1131 | LCOD_ERR | Indicates the transaction log cannot be read because it is encrypted with advanced encryption and either advanced encryption or log encryption is off. Enable advanced encryption and log encryption to proceed. | |||||||||
1132 | LCAM_ERR | Indicates the transaction log cannot be read because it is camouflaged, and either advanced encryption is on or log camouflage is off. Enable the log camouflage option and turn off advanced encryption to proceed. | |||||||||
1133 | LEOF_WARN | Indicates ctVerifyFile found unexpected data beyond the logical end of file. This is unlikely to cause problems by itself, but might indicate prior data loss or corruption | |||||||||
1134 | PEOF_WARN | Indicates ctVerifyFile found a discrepancy between end of file tracked in the header and the actual file size. This is unlikely to cause problems by itself, but might indicate prior data corruption. | |||||||||
1135 | ISORT_ERR | Indicates the rebuild succeeded but is missing keys. This error is returned in some cases with very large sort memory (greater than 12GB) and large indexes. V11.5.1.55041 introduced a fix that allows a successful rebuild in this case. | |||||||||
1136 | FBTU_ERR | Indicates file block failed because the file has been updated in an active transaction and the caller requested that the file block should fail in this situation instead of aborting the transaction. | |||||||||
1137 | CBPO_ERR | Indicates file open wait for a pending conditional index callback initialization timed out. If callback initialization was waiting on this operation, retry the open later. | |||||||||
1138 | APICOMPAT_ERR | Indicates FairCom DB initialization failed because the FairCom DB library's API definition is not compatible with the application's compile time options. For example, the client library might be using 4-byte file numbers but the application is compiled to use 2-byte file numbers. | |||||||||
1139 | SRVFILNO_ERR | Indicates the connection attempt failed because the FairCom DB client library is using 4-byte file numbers but the server is using 2-byte file numbers. | |||||||||
1140 | TRNU_ERR | Indicates compact to truncate failed because the file has been updated in an active transaction. | |||||||||
1141 | PDESC_ERR | Indicates plug-in callback request does not match plug-in library. | |||||||||
1142 | PLOAD_ERR | Indicates plug-in callback library failed to load. Check CTSTATUS. | |||||||||
1143 | PLINK_ERR | Indicates plug-in callback unable to link function. | |||||||||
1144 | SMIV_ERR | Indicates unexpected shared memory state. This error causes the operation to fail if an unexpected shared memory state is encountered. | |||||||||
1145 | FORCE_DIAG_ERR | Indicates the function call returned an error due to a request by a diagnostic option. | |||||||||
1146 | ATTR_NOTFOUND_ERR | Indicates attribute not found / end of iterator scan. | |||||||||
1147 | ATTR_INVHDL_ERR | Indicates invalid handle type. | |||||||||
1148 | ATTR_NOMEM_ERR | Indicates memory exhausted. | |||||||||
1149 | ATTR_INVALID_ERR | Indicates attribute unknown or not applicable to the handle. | |||||||||
1150 | ATTR_INTERNAL_ERR | Indicates internal resource text parsing/handling error | |||||||||
1151 | ATTR_INVITR_ERR | Indicates invalid iterator. | |||||||||
1152 | ATTR_INVIDX_ERR | Indicates item index out of range. | |||||||||
1153 | ATTR_NOTSUP_ERR | Indicates unsupported resource version / unsupported operation. | |||||||||
1154 | ATTR_ASSOC_ERR | Indicates handle already added to a parent handle. | |||||||||
1155 | REPL_NOBASEDIR_ERR | Indicates the source server's base directory has not been set for replication. | |||||||||
1156 | RCPT_ERR | Indicates a FairCom DB data file has a corrupted resource definition. | |||||||||
1157 | LONG8_NSUP_ERR | Indicates the operation is not supported because it requires native 64-bit integer support. | |||||||||
1158 | SQL_LOGON_BLOCKED_ERR | Indicates SQL connection is blocked from logon due to server startup logon block. SQL connections have a choice when logons are blocked at server startup:
| |||||||||
1159 | SERVER_FAILOVER_ERR | Indicates the client library supports setting a time interval in seconds after which a socket receive call checks the server failover status. If a failover has occurred, the FairCom DB function call returns this error, see ctSetCommProtocolOption(). | |||||||||
1160 | SERVER_LOGON_REQUIRES_MD5 | Indicates the server logon protocol requires MD5 hash support but this library does not support MD5 hash. | |||||||||
1161 | CLIENT_LOGON_REQUIRES_SHA512 | Indicates the client logon protocol requires SHA512 hash support but the server does not support it. Upgrade server or downgrade client. | |||||||||
1162 | DUMP_ABANDONED_ERR | Indicates the dynamic dump gave up due to !DELAY setting and active transactions. | |||||||||
1163 | INVALID_REGULAR_EXPRESSION | Indicates the specified value is not a valid regular expression. | |||||||||
1164 | MAX_WORKER_ERR | Indicates a worker thread could not attach to the database engine because the worker thread limit has been reached. | |||||||||
1165 | MAX_NAME_INCOMPAT_ERR | Indicates the client connection attempt was rejected because the client library's maximum file name size (MAX_NAME) does not match the server's maximum file name size. | |||||||||
1166 | ENCL_ERR | Indicates log encryption is enabled (LOG_ENCRYPT YES), but an existing log was not encrypted. To correct this, either disable log encryption or remove old transaction logs (L0*.FCS), start files (S0*.FCS), and log templates (L0*.FCT). | |||||||||
1167 | INV_CMD_ERR | Indicates invalid plug-in command. | |||||||||
1168 | REPLOP_NO_AGENTS | Indicates ctReplAgentOp() found no replication agents running. | |||||||||
1169 | REPLOP_MULTIPLE_AGENTS | Indicates ctReplAgentOp() found more than one Replication Agent running, so the agent ID must be specified. | |||||||||
1170 | SYNC_COMMIT_BLOCKED_ERR | Indicates a transaction commit failed because synchronous commits have been blocked. | |||||||||
1171 | CANNOT_PROMOTE_SERVER | Indicates a promotion of a server failed. See the error message for details. | |||||||||
1172 | CANNOT_DEMOTE_SERVER | Indicates a demotion of a server failed. See the error message for details. | |||||||||
1173 | CANNOT_EXECUTE_SCRIPT | Indicates a script or external process was unable to be executed. See the error message and system error code for details. | |||||||||
1174 | ATTR_INVATTRVAL_ERR | Indicates the attribute has an invalid value. | |||||||||
1175 | INSERT_ONLY_ERR | Indicates a file has disabled updates and deletes. | |||||||||
1176 | INTERRUPTED_ERR | Indicates an interruption by a request or conflicting action. | |||||||||
1177 | JSON_LIB_ERR | Indicates the JSON library returned an error. | |||||||||
1178 | SYSCLOSE_REOPEN_DIFF_ERR | Indicates that a reopen of a file that was closed, found a different file at the system level. | |||||||||
1179 | CLIENT_LOGON_REQUIRES_AES_GCM | Indicates that the client logon protocol requires AES-GCM support but the server does not support it. To resolve this error, upgrade the server or downgrade the client. | |||||||||
1180 | SERVER_LOGON_REQUIRES_AES_GCM | Indicates that the server logon protocol requires AES-GCM support but the client does not support it. | |||||||||
1181 | CRYPTO_RANDOM_ERROR | Indicates that a cryptographic pseudorandom number generation failure occurred. Contact Faircom. | |||||||||
1182 | FIPS_INIT_ERROR | Indicates that an OpenSSL FIPS module could not be initialized. Check configuration. | |||||||||
1183 | KEYGEN_ERROR | Indicates a Cryptographic Key generation failure. Contact Faircom. | |||||||||
1184 | CRYPTO_CRC_ERROR | Indicates a Cryptographic Checksum error, wrong master key, or corrupted file. | |||||||||
-1185 | TIMEOUT_ON_LAST_LOG_ENTRY | Indicates the sysiocod value when ctReplGetNextChange() returns NTIM_ERR on the last log entry in the transaction log. | |||||||||
1186 | CERT_EVAL_ERROR | Indicates an error occurred while parsing a username from client x509 certificate. | |||||||||
1187 | X509_NSUP_ERROR | Indicates that X509 authentication is not allowed by the server. | |||||||||
1188 | CHANGEID_NOTSUPPLIED_ERR | Indicates a record update failed because changeid was not supplied by the caller. | |||||||||
1189 | CHANGEID_NOTREAD_ERR | Indicates a record update failed because the changeid value was not read at the time the record was read. One possible cause is that the record was read without locking it. | |||||||||
1190 | CHANGEID_ALREADY_EXISTS_ERR | Indicates the specified data file already has a changeid field. | |||||||||
1191 | CHANGEID_DOES_NOT_EXIST_ERR | Indicates the specified data file does not have a changeid field. | |||||||||
1192 | CHANGEID_MISMATCH_ERR | Indicates the changeid value passed to an update operation does not match the record's current changeid value. | |||||||||
1193 | CHANGEID_VALUE_TOO_LOW_ERR | Indicates the generated changeid value is less than the changeid high water mark in the data file header. This can be a result of deleting the transaction logs or copying the file to another server, and then opening the file within an active transaction. | |||||||||
1194 | CLUSTER_NOT_ACTIVE | Indicates the client requested a connection to a server in a c-tree cluster, but the cluster is not active. | |||||||||
1195 | DEFRAG_IN_PROC_ERR | Indicates an online compact or rebuild is already in process for this file. | |||||||||
-1196 | DEFRAG_NO_TRUNCATE_COD | Indicates an online file compaction completed, but was unable to reduce the file size on disk due to exceptional activity. | |||||||||
1197 | DEFRAG_MANAGER_ERROR | Indicates an online file compaction failure due to an error in the defrag manager. Check CTSTATUS for additional error messages. | |||||||||
1198 | BATCH_UNEXPECTED_STATE_ERR | Indicates an unexpected state during batch operation. Check CTSTATUS.FCS for diagnostic information. | |||||||||
1199 | ONLINE_REBUILD_ERROR | Indicates a critical error during an online rebuild. The index must be rebuilt in EXCLUSIVE mode. Check CTSTATUS for additional error messages. | |||||||||
1200 | CRYPTO_DIGEST_ERROR | Indicates a cryptographic Digest failure. | |||||||||
1201 | TMPDIR_VERSION_ERROR | Indicates that TMPDIRDT.FCS has unknown format. | |||||||||
1202 | SYSTEM_CALL_FAILED | Indicates a system call failed. Check the system error code. | |||||||||
1203 | SCHEMA_VERSION_ERROR | Indicates an invalid record schemaid was encountered. | |||||||||
-1204 | REACHED_MAX_LOG_READ_POSITION | Indicates the sysiocod value when | |||||||||
1205 | SCHEMA_TYPE_UNKNOWN | Indicates the schema contains an unknown data type. | |||||||||
1206 | MULTIOPEN_ERROR | Indicates the operation is not allowed for a file opened by this user more than once. | |||||||||
1207 | READ_ACCESS_DENIED_ERR | Indicates this file's permissions do not allow the caller to read the file. |