mupip ftok -jnlpool correctly reports the FTOK Key and FileId columns for replication instance files
Final Release Note
mupip ftok -jnlpool
correctly reports the FTOK Key
and FileId
columns for replication instance files. Previously, in YottaDB r1.36, these columns used to hold incorrect values for those instance file names which were not in the current directory. Additionally, mupip ftok
works correctly on database file names whose absolute path is longer than 255 characters. Previously, in YottaDB r1.36, it would use a truncated file name resulting in incorrect output. [#979 (closed)]
Description
When MUPIP FTOK is used with one (or more - YDB extension) repl instance files, the path is stripped off of the filename before the FTOK() is done. This means the FTOK/file-id information is missing (generally FTOK is -1 and fileid is random) though the jnlpool or recvpool information is correct if it exists as it was extracted from the replication instance file (full path used).
Bottom line is unless one is currently in the directory that contains the replication instance file(s), then the file is not found and reports a -1 FTOK. The YottaDB extension that allows multiple replication files to be specified then causes all of them to be reported for the same file in the current directory.
While working on this issue, a further issue was identified with usage of a strncpy() call that would allow a 255 byte DB name to overflow a filename buffer and cause damage. This issue was also corrected.
Draft Release Note
mupip ftok -jnlpool
correctly reports the FTOK Key
and FileId
columns for replication instance files. Previously, in YottaDB r1.36, these columns used to hold incorrect values for those instance file names which were not in the current directory. Additionally, mupip ftok
works correctly on database file names whose absolute path is longer than 255 characters. Previously, in YottaDB r1.36, it would use a truncated file name resulting in incorrect output. [#979 (closed)]