Your library database is corrupted and you decide to restore the database from a recent backup.
However, after the library is restored, one of your users informs you that he or she is not able to
check out a particular document from the library. When he or she does, the error message “Invalid
attempt to read when no data present” is displayed.
Identify two tasks that should be completed to resolve this issue.
A.
Run the UpdateRestoreDate.sql script on the library database.
B.
Restart the Developer to resynchronize with the library.
C.
Select “Library Updates…” from the Tools menu.
D.
Click the Refresh button (or press F5) to refresh the user’s library view.
E.
Stop and restart the SQL instance to flush the server database cache.
Explanation:
A: If a database administrator restores the server database from a backup, the
UpdateRestoreDate.sql script must be run to update specific fields.
This is necessary because clients normally synchronize with the server in a way that only uploads
or downloads the latest changes that occurred after the last synchronization. This is a differential
or incremental update. This works because the server and the client assume that the time can only
go in one direction: ahead, but cannot go back. This rule is violated when the server database is
restored to an earlier point in time. Therefore, a special flag must be updated in the database
which indicates that an incremental refresh would not work, but a full refresh is needed, because
the server “went back in time”. The system cannot normally handle this situation correctly, unless
the script is run.
The UpdateRestoreDate.sql script is located in the Utils folder in the location where the Developer
server is installed.
OracleUser Productivity, Content Development,Restore a Database