Looking to solve an issue where 3 different versions of the same database (dev, beta and production) had different names, I went looking for a way to fix it without shutting the server down (and losing sleep).
Enter IBM Technote #1257799.
Clipped from the technote, available here.
“If the server cannot be shut down, it is possible to rename the OS file name with the server up if there are no external third-party software factors to consider. Keep in mind that a server task acting on the database can create a database handle and not allow you to rename the file. To prevent this from occurring:
1. Let the user know you are going to rename their database and instruct them to exit their Lotus Notes® client. (Also, ensure that the database is not open by anyone else.)
2. Shut down the Domino Router by issuing tell router quit at the server console.
3. Issue the command drop database mailfilename.nsf
4. Make sure replication/cluster replication is not occurring.
5. Issue the command dbcache flush
6. Rename the database on the file system.
7. Update the Person document "Mail File" field to the new file name of the mail file.
8. Restart the Router task by issuing "load router" at the server console.
9. Make sure the end user's Location document is also updated with the new file name. (Location document -> Mail Tab -> "Mail file" field).”
Better - use Domino Administrator to move databse on the same server using teh replica task. Choose move database (on the same server) - rep server - acknowledge to delete source database in the admin4.nsf
ReplyDeletethats it - out of teh box and supported bey domino - no filetransfer actions needed
Volker Müller