URL: http://www.firstbasesoftware.com/man/man5/error.htm
Last modified: 2 May 1996
Copyright © 1996 by FirstBase Software.
[ Index of Contents] [ FirstBase RDBMS Overview]

NAME

SYNOPSIS

DESCRIPTION

101

FB_BAD_TTY - Not connected to an interactive tty device.

102

FB_BAD_TERMCAP - Either the database of terminal capabilities itself or the individual entry for the current terminal was not located. See terminals(5).

121

FB_BAD_DATA - Corrupt data in the database or data object. If the object is a database, use dbcheck(1) to verify database corruption. Use dbclean(1) or dbemit(1)/dbload(1) to repair a database.

122

FB_BAD_DICT - The database data dictionary is not valid. See dbdbas(1).

123

FB_BAD_INDEX - The index is either corrupt or for a different database. Try dbregen(1) or dbigen(1) to regenerate the bad index.

124

FB_EXEC_FAILURE - An execution failure, probably too many processes running on the computer.

125

FB_FATAL_FGETREC - A fatal fixed getrec call. Fgetrec is used to read the fixed length map records and index entries of the database support files. Use dbcheck(1) to see if the problem is with the database. If so, use dbclean(1) or dbemit(1)/dbload(1) to repair the database. Otherwise, rebuild the offending index using dbigen(1).

126

FB_FATAL_GETREC - A fatal getrec call. Getrec is used to read records from the database. Typically, this means the database map file is corrupt, though the data itself could be. Use dbclean(1) or dbemit(1)/dbload(1) to repair the database.

127

FB_FATAL_PUTREC - A fatal putrec call. Putrec is used to write a record to the database. If received while using a C program or macro(5) code, check each field that is being stored or assigned. This error could indicate a more serious hardware problem.

128

FB_IO_ERROR - A serious data error which could indicate a hardware problem. An attempt to read or write from a file marked OK has resulted in an error. One possibility might be the machine architecture, big endian or little endian. See the FirstBase settings CPU_BYTEORDER and DBASE_BYTEORDER in setup(5).

129

FB_OUT_OF_MEMORY - The process has run out of memory.

130

FB_READ_ERROR - The process could not read from a file.

131

FB_SEEK_ERROR - The process could not seek to a certain point of the indicated file.

132

FB_WRITE_ERROR - The process could not write to the indicated file.

133

FB_WRONG_INDEX - The requested index is either from a different database or from a different incarnation of the current database.

134

FB_DIRTY_DBASE - This error means that some process exited during a critical section of updating a database record. If the occurs, all other processes are locked out of the database since the data is most likely corrupt. The fix is to use dbclean(1), and to determine why the initial process exited during the critical database update section.

135

FB_LINK_ERROR - An error has occurred in a database linked to the current database. The offending database must be fixed before the current one will work.

200

FB_ABORT_ERROR - User entered ABORT keystroke to exit. See keyboard(5).

201

FB_CANT_OPEN - The process cannot open the indicated file. The additional error message should state the reason: permission denied, too many files, read only disk partition, etc.

202

FB_CANT_CREATE - The process cannot create the indicated file. An additional error message stating the reason is also printed.

SEE ALSO

FirstBase User's Guide and Reference Manual