DBSM (database server) return codes

The return codes in Table 1 are generated by database access routines and recorded in the error_no value in the errorlog entry.

If an error_no value is not described here, check the AIX errno value for a description of the error, and contact Blueworx Support if necessary.

Table 1. Blueworx Voice Response database return codes
error_no	Description	Explanation	User response
2	No such file or directory	An operation failed because the specified file could not be found.	Try to establish which operation received this error, check and correct the data if necessary, and retry.
5	I/O error	An operation failed because a input/output error has occurred. This may indicate a hardware problem.	Check the AIX system log (using the "errpt -a" command) for any evidence of hardware errors. If there is a hardware error, consider shutting down Blueworx Voice Response, as system operation may be affected.
9	Bad file descriptor	An operation failed because an invalid file descriptor was specified.	Check the errorlog, because this error can be preceded by one which more correctly describes the problem. If not and this error persists after you have restarted Blueworx Voice Response, contact Blueworx Support.
13	Permission denied	An operation failed because the file permissions would not allow it.	Check the error details, and the ownership and file permissions. See the "vae.setuser" utility in Blueworx Voice Response for AIX: Installation to reset the permissions if necessary.
17	File exists	An attempt was made to create a database file or table, but it already exists.	Try to establish what operation received this error, check and correct the data if necessary, and retry.
24	Too many open files	A process has reached the per-process limit on the number of files open concurrently.	Restart Blueworx Voice Response. If this problem persists, then contact Blueworx Support.
27	File too large	An attempt was made to increase the size of a database file or table beyond the system limit.	Check the error details of the affected file.
28	No space left on device	An operation failed because there was insufficient space in the file system.	Delete any unnecessary data or increase the size of the relevant file system(s). Restart Blueworx Voice Response, specifying forced recovery.
30	Read only file system	A write operation failed because the file system was mounted as read-only.	Reconfigure the file system and restart Blueworx Voice Response.
-4201	End-of-file encountered	The end of the file was encountered on a read of a database file or table.	None normally required. However, this can happen when an operation expects a record or row to exist, but it doesn’t.
-4202	Beginning-of-file encountered	The beginning of the file was encountered on a read of a database file or table.	None normally required. However, this can happen when an operation expects a record or row to exist, but it doesn’t.
-4203	Intentions denied	The requested database access intentions cannot be granted because another process(es) already hold more restrictive intentions on the file.	Try to establish which operation received this error, and retry. This may be a transient condition. If the problem persists, contact Blueworx Support.
-4204	Duplicate key	An attempt was made to add/insert a record/row into a database file/table, but the request failed because a unique index already contains the same data.	Try to establish which operation received this error, check and correct the data if necessary, and retry. If the problem persists, contact Blueworx Support.
-4206	No record	Either no record was found which matched the specified key, or a delete/update was attempted when the record was not locked.	If the problem persists after restarting Blueworx Voice Response specifying forced recovery, then contact Blueworx Support.
-4207	Not an index	An operation was attempted which required the use of a database index, but the specified index did not exist.	Restart Blueworx Voice Response. If the problem persists, then contact Blueworx Support.
-4208	File needs recovery	A file was found to need recovery when it was opened.	Restart Blueworx Voice Response and specify forced recovery, noting any errors that occur. If the problem persists, contact Blueworx Support.