Kbase 16310: Changes that require building a new schema cache file
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
16/10/2008 |
|
Status: Unverified
SYMPTOM(s):
WARNING: The -cache <filename> parameter was used. An error occurred while attempting to read the schema cache from the named file. The schema cache will be read from the database instead. (6126)
The file <filename> is not a valid local cache file. (823)
The time stamp in the database does not match the time stamp in the -cache file: <filename>. (840)
CAUSE:
The primary reason why a new schema cache file requires rebuilding is because of timestamp differences. The schema cache is valid only if the time stamp of the schema cache file matches the time stamp in the database master block. If the time stamps do not match, or for some reason PROGRESS cannot read the file, PROGRESS issues a warning message and reads the schema from the database.
FIX:
The errors indicates that the cache file is out of date and needs to be rebuilt using the SAVE CACHE statement. This will occur when:
- database schema has changed,
- schema permissions have changed,
- when a dump and load has been done.
PROCOPY does not require a new schema cache file.
In the event the client version changes from that of the original cache file, the following error(s) are seen.
The file <filename> is not a valid local cache file. (823)
Thus, a V7 client can only use a cache file saved in V7. Likewise, the same applies for V8 and V9 clients. Minor versions between the client and the cache file are allowed.