If you create a new database with replicas on other locations servers, and publish the new database by sending a doclink to the users at the same day, the doc/database link will always try to open the replica on the server the doclink was created from. This is because at this time does not yet exist database catalog entries for that new database. For that reason, the notes clients are not able to locate the "best" replica from the database catalog, and will try to open the new database from the "server hint" in the link which in many (most?) cases is not desired.
Solution: In addition to the usual nightly scheduled run, catalog task should also be resident in memory. This way, the catalog task could intercept database creation/deletion events, and (almost) immediately create/remove database catalog entries for the newly created database replica in the local catalog (or perhaps via AdminP).
Because now the catalog entries exist everywhere almost immediately after creation, db/doclinks sent at the same day always would open the "best" replica for a Notes client regardless of its location.