DuroDBMS errors are scalar types. They are shown below in Tutorial D notation.

TYPE no_running_transaction_error POSSREP { };

TYPE invalid_argument_error POSSREP { msg string };

TYPE type_mismatch_error POSSREP { msg string };

TYPE not_found_error POSSREP { msg string };

TYPE operator_not_found_error POSSREP { msg string };

TYPE type_not_found_error POSSREP { msg string };

TYPE name_error POSSREP { msg string };

TYPE element_exists_error POSSREP { msg string };

TYPE type_constraint_violation_error POSSREP { msg string };

TYPE key_violation_error POSSREP { msg string };

TYPE predicate_violation_error POSSREP { msg string };

TYPE aggregate_undefined_error POSSREP { };

TYPE version_mismatch_error POSSREP { };

TYPE not_supported_error POSSREP { msg string };

TYPE syntax_error possrep { msg string };

TYPE in_use_error possrep { msg string };

System errors

TYPE no_memory_error POSSREP {  };

Insufficient memory.

TYPE system_error POSSREP { msg string };

Unspecified system error.

TYPE concurrency_error POSSREP { };

A concurrency error occurred. For example, a lock was requested but could not be granted or the current transaction was rolled back because a concurrent modification was detected.

TYPE deadlock_error POSSREP { };

A deadlock condition was detected.

TYPE resource_not_found_error POSSREP { msg string };

A system resource, usually a file, could not be found.

TYPE internal_error POSSREP { msg string };

Internal error.

TYPE data_corrupted_error POSSREP { msg string };

Indicates data corruption.

TYPE run_recovery_error POSSREP { msg string };

Indicates temporary data corruption that requires running Berkeley DB recovery.