Oninit Error Codes
Contents |
Invalid year in date. -1205 Invalid month in date. -1206 Invalid day in date. -1207 Converted value does not fit into the allotted space. -1208 There is no conversion from non-character informix isam error codes values to character values. -1209 Without any delimiters, this date must contain exactly 6 or sql statement error number 8 digits. -1210 Date could not be converted to month/day/year format. -1211 Out of memory. -1212 Date conversion format must contain a month, forms statement error number -8063 day, and year component. -1213 A character to numeric conversion process failed. -1214 Value too large to fit in a SMALLINT. -1215 Value too large to fit in an INTEGER. -1216 Illegal exponent. -1217 The format string is sql error too large. -1218 String to date conversion error. -1219 Numeric value from database is too large for COBOL data item. -1220 Numeric value from database is too small for COBOL data item. -1221 Cannot convert null data types. -1222 Value will not fit in a SMALLFLOAT. -1223 Value will not fit in a FLOAT. -1224 Invalid decimal number. -1225 Column does not admit a NULL value. -1226 Decimal or money value exceeds maximum precision. -1227 Message
Finder
file not found. -1228 Message number not found in message file. -1229 Incompatible message file. -1230 Bad message file name formulation. -1231 Cannot seek within message file. -1232 Message buffer too small. -1233 Invalid hour, minute, or second. -1234 Function may be applied only to datetime data types. -1235 Character host variable is too short for the data. -1236 Bad era date. -1237 Bad era name. -1238 Bad era initialization. -1239 Era year overflow. -1250 Unable to create pipes. -1251 Unable to create shared memory. semget failed. -1252 Unable to create shared memory. shmget failed. -1254 Unable to connect to remote host. -1257 Operating system cannot fork process for back end. -1258 Cannot attach to shared memory used to communicate with back end. -1260 It is not possible to convert between the specified types. -1261 Too many digits in the first field of datetime or interval. -1262 Non-numeric character in datetime or interval. -1263 A field in a datetime or interval is out of range or incorrect. -1264 Extra characters at the end of a datetime or interval. -1265 Overflow occurred on a datetime or interval operation. -1266 Intervals or Datetimes are incompatible for the operation. -1267 The result of a datetime computation is out of range. -1268 Invalid datetime or interval qualifier. -1269 Locator conversion error. -1270 Interval literal may not have embedded minus
-104 ISAM error: too many files open. -105 ISAM error: bad ISAM file format. -106 ISAM error: non-exclusive access. -107 ISAM error: record is locked. -108 ISAM error: key already exists.
Sqlcode
-109 ISAM error: the key is the file's primary key. -110 ISAM error: end fiverr or beginning of the file. -111 ISAM error: no record found. -112 ISAM error: there is no current record. -113 ISAM error: the file is locked. -114 ISAM error: the file name is too long. -115 ISAM error: cannot create lock file. -116 ISAM error: cannot allocate memory. -117 ISAM error: bad custom collating sequence. -118 ISAM http://www.oninit.com/errorcode/index.php?idx=6 error: cannot read log record. -119 ISAM error: bad log record. -120 ISAM error: cannot open log file. -121 ISAM error: cannot write log record. -122 ISAM error: transaction not available. -123 ISAM error: no shared memory. -124 ISAM error: no begin work yet. -125 ISAM error: can't use nfs. -126 ISAM error: bad row id. -127 ISAM error: no primary key. -128 ISAM error: no logging. -129 ISAM error: too many http://www.oninit.com/errorcode/index.php?idx=3 users. -130 ISAM error: no such dbspace. -131 ISAM error: no free disk space. -132 ISAM error: rowsize too big. -133 ISAM error: audit trail exists. -134 ISAM error: no more locks. -135 ISAM error: tblspace does not exist. -136 ISAM error: no more extents. -137 ISAM error: chunk table overflow. -138 ISAM error: dbspace table overflow. -139 ISAM error: logfile table overflow. -140 ISAM error: operation illegal on a DR secondary. -141 ISAM error: tblspace table overflow. -142 ISAM error: overflow of tblspace page. -143 ISAM error: deadlock detected. -144 ISAM error: key value locked. -145 ISAM error: system does not have disk mirroring. -146 ISAM error: the other copy of this disk is currently disabled or non-existent. -147 ISAM error: archive in progress. -148 ISAM error: dbspace is not empty. -149 ISAM error: INFORMIX-OnLine daemon is no longer running. -150 The limits of the INFORMIX Demo Version have been exceeded. -151 ISAM error: Illegal value in varchar length field. -152 ISAM error: Illegal message type received from remote process. -153 ISAM error: not in ISMANULOCK mode. -154 ISAM error: Lock Timeout Expired. -155 ISAM error: Primary and Mirror chunks are bad. -157 ISAM error: Interrupted ISAM call. -158 ISAM error: Operation disallowed on SMI pseudo table. -159 ISAM error: Collation sequence inva
locking, a tablename.lok file exists. Possibly such a file was left behind when another program http://www.oninit.com/errorcode/index.php?pageid=-113 terminated abnormally. If you are sure that is the case, you can release the lock by emptying that file. Lock files are not used in many systems, and they are http://www.informixfaq.com/errorcode/index.php?idx=30 never used with IBM Informix Dynamic Server or IBM Informix OnLine Dynamic Server. This error occurs with IBM Informix Dynamic Server or IBM Informix OnLine Dynamic Server when a error codes user attempts to access a table that has been locked.
For C-ISAM programs, rerun the program after the file is unlocked. For SQL products, tables are locked explicitly using the LOCK TABLE statement and implicitly during the execution of the CREATE INDEX or ALTER TABLE statement. Rerun the program or query when the table is unlocked. If you statement error number get this error (-113) when using a transaction isolation mode of REPEATABLE READ or SERIALIZABLE, and if your query did not use an index (and therefore had to use a sequential scan of the entire table), the cause of the error might be that another user had either an exclusive lock or a promotable lock on at least one row in the table. If you are in REPEATABLE READ or SERIALIZABLE mode and your query requires a scan (search) of every single record in the table to find all the records that meet the conditions in the WHERE clause, then the engine will need to lock every record in the table to maintain the repeatability of the read. In practice, rather than locking every single record, the engine will try to lock the entire table. But if there are any exclusive locks, or even promotable locks, on any row in the table, then the engine will not be able to get a shared lock on the entire table, and the query will fail. Copyright Privacy