MUPIP SET JOURNAL switches older format journal files
Final Release Note
MUPIP SET JOURNAL switches journal files when the existing journal file was created by an older YottaDB release. Previously, it issued a FILEEXISTS error. The workaround was to rename or move the existing journal file before (re)issuing the command. [#1021 (closed)]
Description
This is the output when using an old version and then switching to a newer version. Note the commands/outputs are abbreviated to the essential ones.
$ ver R138
$gtm_dist set to /usr/library/R138/dbg
$ yottadb -r GDE exit
$ mupip create
$ mupip set -journal="enable,on" -file mumps.dat
%YDB-I-JNLCREATE, Journal file /home/sam/mumps.mjl created for database file /home/sam/mumps.dat with BEFORE_IMAGES
%YDB-I-JNLSTATE, Journaling state for database file /home/sam/mumps.dat is now ON
$ ver V989_R139
$ mupip set -journal="on" -file mumps.dat
%YDB-E-FILEEXISTS, File /home/sam/mumps.mjl already exists
%YDB-E-JNLNOCREATE, Journal file /home/sam/mumps.mjl not created
%YDB-E-MUNOFINISH, MUPIP unable to finish all requested actions
Normally, the correct output is:
%YDB-I-FILERENAME, File /home/sam/mumps.mjl is renamed to /home/sam/mumps.mjl_2023195124759
%YDB-I-JNLCREATE, Journal file /home/sam/mumps.mjl created for database file /home/sam/mumps.dat with BEFORE_IMAGES
%YDB-I-JNLSTATE, Journaling state for database file /home/sam/mumps.dat is now ON
Draft Release Note
mupip set -journal
successfully switches journal files even in the case the current journal file corresponds to an older YottaDB release. Previously, it would issue a %YDB-E-FILEEXISTS
error requiring the user to move the older format journal file out of the way before reissuing the command.
Edited by K.S. Bhaskar