When the database is unavailable (either because the database appliance is not running or otherwise inaccessible, or because the Postgres system service is stopped), Filr users can expect to experience some problems.
Users will not be able to login. Those attempting access from the web client may get a message such as: "Could not open Hibernate Session for transaction; nested exception is org.hibernate.TransactionException: JDBC begin failed:". Windows desktop application users will also fail to login, possibly with an error such as "The server is not a Micro Focus file server."
Already logged-on users will also see errors when performing operations such as opening a file in their home folder. On the web client, the error may be something like: "Could not open Hibernate Session for transaction; nested exception is org.hibernate.exception.JDBCConnectionException: Cannot open connection" or "Could not open Hibernate Session for transaction; nested exception is org.hibernate.TransactionException: JDBC begin failed:". Or, operations may simply fail with no error message at all.
On the other hand, it is not expected that data corruption or data loss will occur if the database is down while the Filr and Search engines are up. If files are added in the back-end while the database is down for 20 minutes or more, all data will become available after the database is again brought up. In the worst-case scenario, if data is not available, it will be necessary to re-index.
Ensure that the Filr database appliance (or external database) remains available, to ensure user access and current data for Filr.
Filr relies on the availability of the database for normal operations.