Database errors
- 100 EDUPL
- A duplicate value exists.
- 101 ENOTOPEN
- The table is not open.
- 102 EBADARG
- An illegal argument has been specified.
- 103 EBADKEY
- An illegal key description has been specified. Use the bdbpre and bdbpost tools.
- 106 ENOTEXCL
- This error alerts you that the table is not exclusively locked for your action. You can either wait until the lock on the table is released, or you can remove the lock yourself.
- 107 ELOCKED
- The record you are trying to retrieve is locked. You can either wait until the lock is released or remove the lock yourself.
- 108 EKEXISTS
- The key already exists.
- 109 EPRIMKEY
- You are trying to perform an illegal action on a primary key. See the log file.
- 110 EENDFILE
- You have reached the end of the file.
- 111 ENOREC
- No record was found that matches the query criteria.
- 112 ENOCURR
- No current record exists.
- 113 EFLOCKED
- The table is locked. You can either wait until the lock is released or you can remove the lock.
- 114 EFNAME File name too long
- You are using a file name that is too long. To check the maximum length for a file name, see your system requirements.
- 116 EBADMEM
- Memory cannot be allocated because the system is out of memory. One possible solution is to try to restart the bshell.
- 117 EBADCOLL
- An issue has occurred with the collating or sorting order.
- 123 ENOSHMEM
- No shared memory is initialized. To initialize shared memory, you can, for example, use the rc.start script.
- 129 EUSER
- Too many sessions are started.
- 136 ENOSPACE
- No space is available in shared memory. You can either initialize the shared memory or change the shared memory parameters.
- 140 ETRANSON
- This operation is invalid when the transaction is on.
- 141 ETRANSOFF
- This operation is invalid when the transaction is off.
- 142 EADMON
- An administration process is running.
- 146 ENOSNAPSHOT
- The system cannot take a snapshot of the database, probably because another user locks the database. You can either wait until the lock is released, or you can remove the lock.
- 148 EOFRANGE
- An error occurred in the data-type range check.
- 201 EROWCHANGED
- The record was changed after a delayed lock.
- 202 EDBLOCKED
- The database is locked. You can either wait until the lock is released or you can remove the lock yourself.
- 203 ETRANSACTIONON
- This action is not permitted within a transaction.
- 204 EISREADONLY
- This transaction is read-only.
- 205 ENOTINRANGE
- The field value is out of range and does not agree with the domain definition.
- 206 ENOTLOCKED
- The record is not locked.
- 207 EAUDIT
- An error occurred in the audit trailer.
- 208 EPERMISSION
- The action you just attempted is not permitted at this time.
- 209 EMIRROR
- An error occurred in the mirroring of the database. The tables are inconsistent. You can use bdbpre and bdbpost to copy the tables correctly.
- 210 EMLOCKED
- Either the record is locked in the mirrored database, that the tables are inconsistent, or that the mirroring definition in tabledef6.2 is not compatible.
- 213 ETRANSACTIONOPEN
- The transaction is started, but not updated. This error is an internal bshell error.
- 214 EUNALLOWEDCOMPNR
- An operation for mapping company numbers is not permitted. If the logical company is not equal to the physical company, you cannot perform a drop/clear table operation.
- 215 EILLEGAL
- An illegal state that must never occur.
- 220 EDBCMMODELCORRUPT
- The current DBCM model is corrupt. For more information, see the log messages.
- 221 EDBCMACTIONNOTALLOWED
- An action is not allowed in DBCM context. For example, if a table is under DBCM, an update on the primary key is not allowed. Other actions that are not allowed are updates that would make a record migrate from one to another object.
- 222 EDBCMOBJECTCORRUPT
- A corrupt object is detected. This typically occurs if no root record of the object can be determined.
- 251 EAUDSETUP
- The audit server is set up incorrectly. See the
Log.audit
file. - 252 EAUDCORRUPT
- An audit file is corrupt. See the
Log.audit
file. - 253 EAUDLOCKED
- Another user has locked the audit file. See the
Log.audit
file. - 254 EAUDABORT
- A commit transaction has failed in the audit-server action. See the
Log.audit
file. - 301 ESQLQUERY
- This error is a general SQL error code. This error occurs if a problem with the SQL syntax arises.
- 302 ESQLSYNTAX
- The SQL syntax is incorrect.
- 303 ESQLREFER
- A reference in the query cannot be found.
- 304 ESQLUNDEFINED
- An error occurre305 ESQLWRONGROWd but no error code can be set.
- 305 ESQLWRONGROW
- An incorrect record was returned. This implies that either the table index is corrupt or that the RDBMS has sorting order that differs from the Enterprise Server software.
- 501 EMEMORY
- An internal memory error.
- 502 EBDBON
- The user is already logged on.
- 503 EBADADRS
- An illegal address has been used.
- 504 EBADFLD
- A column is undefined.
- 505 ENOSERVER
- Either no server is specified in
tabledef6.2
, or the server cannot be started. See the log file. - 506 ENOTABLE
- The table does not exist.
- 507 ETABLEEXIST
- The table that you are trying to create already exists.
- 508 EBDBNOTON
- You are not logged on to a database.
- 509 EBADCURSOR
- You have a bad memory cursor or you have specified a bad table pointer.
- 510 EDBNOTON
- The database is not on. To correct the problem, simply start the database.
- 511 EWRONGVERSION
- The version of the client differs from the version of the server.
- 512 EDDCORRUPT
- The data dictionary is corrupt. To repair this error, use bdbpre and bdbpost tools.
- 513 ENODD
- The data dictionary was not found.
- 514 ESECURITY (Oracle)
- This error is a security error and often indicates that you do not have the proper user or group permission.
- 515 ELICENSEERROR
- This error is a license error that usually indicates an unpatched binary.
- 516 EUPDSEGM
- This error occurs during the making or filling of rollback segments and usually indicates that the disk is full.
- 517 EDELAYED
- This error is a general error that indicates delayed locking.
- 518 ENOSESSION
- An invalid session code has been specified.
- 519 ENOCOMPNR
- Either no company number or an illegal company number has been specified. A valid company number is a number between 0 and 999.
- 520 EBUFUPD
- This error occurs when flushing of buffered updates fails. The flushing can fail due to a lock or referential integrity constraint.
- 521 ENOSHM
- This error indicates that shared memory has not been loaded. See Shared memory management.
- 522 EBDBDBCONNECTIONLOST
- The connection between the driver and database has been lost.
- 523 E_BDB_FULL
- The user’s request cannot be carried out because the required space is not available in the database. The database administrator must either extend or reorganize allocated space manually.
- 600 EREFERENCE
- This error is a general reference error. See the log file.
- 601 EREFLOCKED
- The reference table is locked. You can either wait until the lock is released or remove the lock yourself.
- 602 EUNDEFREF
- The reference is not defined. The problem is probably located in the run time data dictionary. See the log file.
- 604 EREFUPDATE
- A reference could not be updated.
- 605 EREFEXISTS
- The record cannot be deleted while the reference exists. See the log file.
- 606 EREFNOTEXISTS
- The reference does not exist.
- 607 ENOREFTBL
- The reference table was not found. The data dictionary might be incorrect. For more information, see the log file.
- 608 ENOREFCNT
- No reference counter fields are present.
- 609 EUPDREFCNT
- This error can occur when you update the reference counter.
- 700 ESETLOCALE
- This error can occur when you set the locale. See the log file.
If an error code greater than 1000 appears, depending on the database driver you use, the error can be retrieved as:
Error - 1000 gives DB error.
Example UNIX:
Error no: 11400
Error: 11400 – 1000 = 10400
Example Oracle:
Error no: 1979
Error: 1979 – 1000 = 979 Not a GROUP BY
Note: If a fatal error occurs, more information is stored in the log
files in the
$BSE/log directory. For example, if
bdbpost causes an error, the error is reported in
the
Log.bdbpost
file.