Under certain circumstances a system crash, or a power failure can leave a DP4 database in a state where records appear to be locked next time it is opened. This could obviously cause operation problems for systems which depend on record locking.
The specific circumstance where this arises is where a record is locked after another program has updated the database, and then the other program terminates. If the system crashes before another record is updated this record will still appear to be locked when the system is restarted, because DBRECOV is not forced (and indeed cannot be run).A work-around for the problem is to update any other record on the database, and close the database down. This will increment the timestamp, so that the record no longer appears to be locked.
Where the version affected is given as 4.5xx or 4.6xx, all versions of DP4 issued prior to the date of the fix are potentially affected. Where a specific version number is given the problem was introduced by that release and prior releases are unaffected. If a patch release number is also specified (in parentheses) , the fault was introduced at that specific patch level.
4.519+ dp4srvr.w32
(for use with all post 4.519/4.614 Win32 versions of DP4)
The Intel Unix and Unixware 7.1 srv3 will be updated shortly