Product Documentation

V11.5 Release Notes

Previous Topic

Next Topic

RenameIfil() possible file loss on Unix/Linux fixed

During a file rename operation, Unix/Linux systems could have been unable to open a file due to DMAP_ERR (957) with a CTSTATUS message similar to the following:

User# 00055 DMAP_ERR: index file myFile.idx (474) for data file myFile.dat (506) is already associated with data file myFile.dat (148)

On Unix/Linux systems, a RenameIfil() could succeed even if the new name already existed on disk, causing the original file to be deleted. The DMAP_ERR may occur if the original file was open and in use at the time of the rename.

The logic on Unix/Linux systems has been modified so that, if the new file name already exists, the RenameFile() and RenameIFile() functions will now fail with RENF_ERR (67).

Note: This is a behavior change. Server keyword COMPATIBILITY RENAME_OVERWRITE allows reverting to the prior behavior.

TOCIndex