Identity Manager 2.x
Admin observed one of the following errors:Message: Code(-9006) The driver returned a "retry" status indicating that the operation should be retried later. Detail from driver: Unable to locate note from UNID. Notes Exception ID = 4063. Message: Database <server name>!!names.nsf has not been opened yet
<status event-id="#20040930154447#1#8" level="retry">Unable to locate note from UNID. Notes Exception ID = 4091. Message: Invalid universal id</status>
While this happened, the server's TAO cache file grew as subscriber transactions backed-up.
Checked the dirxml trace to find which user was in the subscriber transaction with the error and unassociated it. Once this happened, the other transactions went through just fine and the TAO file began to empty.
Sometimes Notes Admin, when he finds a bad note, will copy the contents of the old note into a new one. While the data appears the same, the Notes ID is different, thus causing a bad association. This can cause a 4091 error, and may cause a 4063 (or some other undertermined type of corruption on the user).
If you experience a 4063 error, first verify only the name of the database is specified (ie. "names.nsf") in the dsrepcfg.nsf and driver InputDB parameter, and not the full path.
Formerly known as TID# 10094864