Kbase 18218: AS/400: UPDSCHCRC To Correct Error 2468 / PRO9024
| Autor |
Progress Software Corporation - Progress |
| Acesso |
Público |
| Publicação |
12/9/2008 |
|
Status: Verified
FACT(s) (Environment):
Progress/400 DataServer
IBM AS/400 (CISC)
IBM AS/400 (RISC)
SYMPTOM(s):
Unable to open the database file. (2468)
PRO9024 There is a server schema/object mismatch for <file>.
CAUSE:
Some actions on the AS/400 may cause a timestamp or CRC mismatch between the AS/400 object and the Progress/400 schema. For example, an upgrade of the OS400 or moving libraries from one machine to another. The objects affected are normally the logical files.
The objects affected are normally the logical files. The symptom of that problem is that when the program tries to access the file using the index (logical file) which has the problem it gets the error:
Unable to open the database file. (2468)
In the AS/400 job log the following message referred to the logical file is found:
PRO9024 There is a server schema/object mismatch for <file>.
FIX:
To solve this problem either use the -Dsrv LFLVLCHK=CRC parameter (if client version is 8.1A or later) or running the CHGPRODCT utility over all logical files and synchronizing the schema holder.
But sometimes running CHGPRODCT can be risky because if the parameters are not correctly supplied the Progress attributes (labels, field names,...) will be lost, or it can be tedious to use if the logical files are not alone in the same library.
For these situations we can use the UPDSCHCRC utility supplied by Progress. This utility will recalculate the timestamp and CRC of the logical files in the Progress schema according to current objects. It replaces the use of CHGPRODCT and it is much faster. The syntax of the utility is:
CALL PGM(UPDSCHCRC) PARM(<library>)
where <library> is your Progress/400 dictionary library.
When the utility has finished, a complete synchronization of the client schema holder is required.
***** WARNING - VERY IMPORTANT *****
THIS UTILITY DOES NOT PERFORM ANY CHECK WHILE RUNNING. IF YOU RUN IT OVER A LOGICAL FILE THAT HAS CHANGED AND THE CHANGES HAVE NOT BEEN REFLECTED INTO THE PROGRESS SCHEMA WITH CHGPRODCT, IT WILL CORRUPT THE SCHEMA INFO IN SUCH A WAY THAT THE PROGRAMS MAY CORRUPT THE DATA. BEFORE USING IT, MAKE SURE THAT THE SCHEMA IS THE SAME AND ONLY THE TIMESTAMP HAS CHANGED.