Has anything changed in the database that you connect VFE to? That error seems to me to indicate that it can't find a table. That's where I would start troubleshooting.
Also for what it's worth, we are on CPS and the naming convention for tables is dbo.x, so in this case it would be dbo.OBSHEAD. Not sure about how things are in the Oracle version.
Brad
As Brad suggested, VFE cannot open the database connection. Sometimes simply opening EMR/CPS will re-establish the link while other times a fresh reboot is required.
What exactly causes the connection to fail could be attributed to numerous culprits to include, a change in network or local security settings, corruption of drivers and a different program locking the driver/connection for its own use.
It is important to note that VFE utilizes the local Windows ODBC driver connection, meaning most all failures would be external of VFE proper. You might be able to troubleshoot connection issues using Windows ODBC Manager. If the issue persists, you may want to contact VFE Support for assistance.
For the record, DBO is the table prefix for SQL databases while DBA is the prefix for Oracle databases.
Hope this helps.