Skip to main content

Renaming a Domino Database with the Server Up

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).”

Comments

  1. 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
    thats it - out of teh box and supported bey domino - no filetransfer actions needed

    Volker Müller

    ReplyDelete

Post a Comment

Popular posts from this blog

Policies and Controls are King in the IT Security world

I came across an article by Roger Grimes over at Infoworld on how security policies and controls are the real power when it comes to IT security. Roger mentions the SANS 20 Critical Security Controls for Effective Cyber Defence , which are a great read for anyone looking at updating or auditing your policies for completeness. The SANS top 20 controls are a must for any organization: Inventory of Authorized and Unauthorized Devices Inventory of Authorized and Unauthorized Software Secure Configurations for Hardware and Software on Laptops, Workstations, and Servers Secure Configurations for Network Devices such as Firewalls, Routers, and Switches Boundary Defense Maintenance, Monitoring, and Analysis of Security Audit Logs Application Software Security Controlled Use of Administrative Privileges Controlled Access Based on the Need to Know Continuous Vulnerability Assessment and Remediation Account Monitoring and Control Malware Defenses Limitation and Control

Error 217 - Error creating product object on Domino 64 bit

I'd like to share something with you.   An error that you'll get if you are trying to use ODBC with Domino 8.5.1 64bit. It starts out with an agent error of Error 217.  The text of the error is "Error creating product object" You can read about it here on the Notes/Domino forum . You can find the solution here as well . I guess I'm now waiting for Domino 8.5.2 for a solution for this.   It would have been nice to have had this in the release notes.  It would have help me greatly.

Reminder: Increase the maximum available memory on your Lotus Notes client JVM today!

Yup, that's right.  Public Service Announcement time. If you haven't increased the maximum memory available to your Lotus Notes JVM yet, what are you waiting for? By default, the Notes JVM only has 256mb of memory available to it.  On a system with 4GB+ of memory, you should be easily able to increase it to 1/4 to 1/3 of the system memory and improve the end user performance. Here's how: Shut down Lotus Notes. In order to make sure that all processes are stopped, run this command:  Start -> Run Type: C:\Program Files (x86)\IBM\Lotus\Notes\nsd.exe -kill Open: C:\Program Files (x86)\IBM\Lotus\Notes\framework\rcp\deploy\ Open the "jvm.properties" file in a text editor like notepad.  You will possibly require Administrator permissions. At the beginning of the file, you will see text surrounded by a lot of pound signs ####. The first ‘property’ after the last # sign is: vmarg.Xmx=-Xmx256m Change 256m to 1024m so that the line reads: vmarg.X