Error Messages

What follows is a list of error messages with a description of their cause and a possible solution where applicable. Some messages are self-explanatory; in those cases, no explanation will appear after them.

  • The file `file' with extension `ext' doesn't have an associated path in the layout `layoutfile'

    Description: This message appears when the physical file related to a table that belongs to a schema used by the server does not have an entry in the physical layout file.

  • The last directory must have null size, logical name ='table', directory list = `dir1:nbytes,...'

    Description: This message appears when, while working with ranged tables, the last directory has a maximum size defined.

    Solution: Delete the size entry of the last directory.

  • In the configuration file `layoutfile' the line `n' has a syntax error or a forbidden null value.

  • Can't open the configuration file `layoutfile'

    Description: This message indicates problems when trying to open the physical layout description file for modification.

    Solution: check that the appropiate permissions are set on the file.

  • Can not read disk configuration file `layoutfile'

    Reason: invalid file or the `DiskConfiguration' entry does not exist inside the `.sv' file.

  • Directory not found in configuration file, pattern `pattr' directory `directry'

    Description: a reference to a directory inside the physical layout description file is invalid (i.e., the directory doesn't exist).

  • In disk configuration file, entry `ntry' has a pattern (`pattrn') that doesn't belong to any schema.

    Description: this message appears when line n inside the physical layout description file refers to a pattern (i.e., table or group of tables) that doesn't belong to one of those attended by the server.

    Solution: check that all the references to tables or group of tables (through regular expression) are valid.

  • In physical layout configuration file, `c' is not an allowed unit, the units allows are: 'K'for Kb, `M' for Mb, and 'G' for `Gb'.

    Description: The unit size specified for table partition is not valid.

    Solution: check that every dimension is one of the allowed (i.e., K, M or G).

  • Invalid Journal file `jrfl', incompatible with current version.

    Description: Essentia detected an incompatible Journal file. To recover the data you must start the correct version of Essentia.

  • Can not read run log file `file'

    Description: Essentia is trying to read a run log file (option -r) but the file can't be found or it doesn't have the appropiate read permissions.

  • Bad magic for run log file `file'.

    Description: Essentia is trying to read a run log file that was created with other version of Essentia.

  • Server is already running.

  • Can't connect to server: `server'

    Description: In the middle of a 2PC (two phase commit) transaction, a server is trying to connect to its master but fails.

  • Can not read configuration file: `file'

    Description: The `.sv' file is missing

  • Cache size is too small, it must be >= 64K

    Error ocurred while initializing lock table

    Description: The maximum number of locks specified in the configuration file (see ``Locks'') is too large.

  • Could not find journal directory: `dir'

    Description: The directory specified for the journal in the `.sv' file can't be found.

  • Could not find database directory: `dir'

    Description: The directory specified for the databases in the `.sv' file can't be found.

  • Run log generated by diff. endian architechture... must compile Essentia w/DEBUG

    Description: The run log file that is trying to be used (option -r) was generated on a machine whose microprocessor has a different endian architechture than the current one.

  • The time reported by the operating system is inconsistent

    Description: The last timestamp on the database has a higher date than the current date returned by the operating system.

    Solution: Check the operating system and system hardware timers.

  • Struct tables only can be packed type, check the entry in the disk configuration file for struct table `tab'

    Description: A table description table has been specified with a type different as PACKED.

  • Installation problem, server must run as root

    Description: The Essentia binary has incorret uid (user id) or suid (set user id). Both must be root for Essentia to run properly.

  • Usage: essentia [options] configFile

    Description: An invalid option was passed as argument to Essentia, or the configuration file was missing.


    Table of Contents