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.
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.
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.
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.
Reason: invalid file or the `DiskConfiguration' entry does not exist inside the `.sv' file.
Description: a reference to a directory inside the physical layout description file is invalid (i.e., the directory doesn't exist).
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.
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).
Description: Essentia detected an incompatible Journal file. To recover the data you must start the correct version of Essentia.
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.
Description: Essentia is trying to read a run log file that was created with other version of Essentia.
Description: The `.sv' file is missing
Error ocurred while initializing lock table
Description: The maximum number of locks specified in the configuration file (see ``Locks'') is too large.
Description: The directory specified for the journal in the `.sv' file can't be found.
Description: The directory specified for the databases in the `.sv' file can't be found.
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.
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.
Description: A table description table has been specified with a type different as PACKED.
Description: The Essentia binary has incorret uid (user id) or suid (set user id). Both must be root for Essentia to run properly.
Description: An invalid option was passed as argument to Essentia, or the configuration file was missing.