Running Global Projects
Suggested Housekeeping Guidelines for Projects : Database File Locks : Locating and Closing Locked and/or Open Database Files : Managing Database File Status
Managing Database File Status
To monitor for locked and/or open files the Windows's own Open Files screen on the File Server can be used. However, there is no standard Windows tool to close the locked or open files and additional utilities are needed. The utility used by AVEVA and other customers is pstools that can be obtained from Sysinternals the specific tool being PsFile. Using this, the files can be monitored and closed.
Note:
PsFile only shows files opened remotely, so won't show files open by processes running on the File Server itself - e.g. if scheduled jobs are being run on the File Server itself.
Alternatively, you can use the Microsoft NETFILE API on the server to free locked db files.
Summary of steps before conducting an ADMIN task on a database
1.
Broadcast a message to all users on the project telling them that they should cleanly exit by a required time. If the ADMIN MESSAGE command is used note that it will only be visible to those logged in at the time, and when they change module.
2.
At the advised time Lock the project via ADMIN to prevent any users accessing the databases further.
3.
If a Global project, stop the Daemon to stop updates and/or remote claiming.
4.
Check the project for any users still logged in and try to get in contact with them and ask them to leave the project cleanly.
5.
Any users who cannot be contacted should be severed from the project by Expunge User Process.
6.
Expunge All Users to remove any phantom users and release any claims.
7.
Using pstools PsFile check for any open or locked db files on the db File Server.
8.
Using pstools PsFile close any open or locked db files on the db File Server.
Note:
In truth the only databases that should not be being accessed in the project in Read or Write mode are those on which an ADMIN task such as reconfiguration or session is being undertaken. However to secure this without getting all users out of the project is to isolate the databases (inclusive of the whole extract family) from use by removing them from all MDB’s and then performing steps 1-8 with the exception of 6. Deferring them is not recommended as the user can overwrite the deferral. After the Admin task has been performed on the specific databases they can then be re-added to the MDB’s.
As this adds an extra level of complexity to the Admin task it is therefore suggested that a window of time is sought where the whole project can be shut down.
1974 to current year. AVEVA Solutions Limited and its subsidiaries. All rights reserved.
AVEVA Logo