REPLINSTFMT, Format error encountered while reading replication instance file xxxx. Expected yyyy. Found zzzz.
Run Time/MUPIP Error: This error is issued by GT.M or MUPIP whenever it tries to open the replication instance file and finds that it was created with a format that the current version of GT.M cannot interpret. GT.M also produces this error when it encounters:
an instance file created on a different endian system or
an instance file created by a 32-bit (or 64-bit) version of GT.M that is different from the current 64-bit (or 32-bit) version of GT.M.
Action: Recreate the instance file using the mupip replic -instance_create command with the current version of GT.M.
![[Note]](../common/images/note.jpg) | |
The REPLINSTCORRV message that was displayed in V5.0-000 has now been replaced by REPLINSTFMT |
Action: If the error is issued by GT.M review the accompanying message(s) in the operator log.
If a MUPIP SET -JOUNAL=ON command produces this message for the region in the operator log, it may indicate that one or more of the current generation journal files are damaged/missing and new journal files were created with no back pointers to the previous journal files. FIS recommends taking a database backup at the earliest convenience because a MUPIP RECOVER/ROLLBACK will not be able to go back past xxxx. If this message is for a specified region(s), consider switching the journal files for all regions (with REGION "*") that the process has opened (all journaled/replicated regions in the instance if replication is in use) to ensure that the RECOVER/ROLLBACK for other regions remains unaffected.
No action is required if the MUPIP BACKUP -NEWJNLFILES=NOPREVLINK issues the error.
