LO68712: MANUALLY CREATED DATABASE REDIRECT FILES DO NOT WORK AS EXPECTED

APAR status

• Closed as fixed if next.

Error description

• Error Description￘
  When a database is deleted or moved, if you are running a 8x or
  higher client and server, a redirect marker can be created that
  will automatically redirect users to the new location of the
  database. When the redirect file is automatically created via
  the client, it appears to work fine in most cases. There may be
  cases however when the redirect file is not properly created or
  when you need to manually create a redirect file. In such
  cases, the manually created redirect file will not work. Below
  is an example of redirect files that were created manually:
  
  [NotesRedirectFile]
  Type=Delete
  RepID=862579DC:007DB396
  Title=Database1
  
  or
  
  [NotesRedirectFile]
  Type=Redirect
  Server=newserver/org
  RepID=862579DC:007DB396
  Title=Database1
  
  The Notes Client creates identifcal redirect files as shown
  above however only the Client-generated redirect files appear
  to work.
  
  Steps to Reproduce:
  
  1.) Create a database on Server1
  2.) Create a replica of the same database on Server2
  3.) Delete the database on Server1 and choose the option to
  create a redirect marker.
  
  After refreshing the workspace, you will notice that the
  workspace icon will be updated and when you click on the
  database icon, the client will automatically redirect you to
  the database replica on Server2
  
  If you follow the same steps as above but choose not create a
  redirect marker but instead manually create a redirect file as
  shown in the above examples, the Notes Client will not update
  the workspace icon and instead, you will receive an error
  indicating that the database cannot be found on Server1.
  

Local fix

• Local Fix￘
  Always use Notes Client to create database redirect files.
  

Problem summary

• This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

Problem conclusion

Temporary fix

Comments

• This APAR is associated with SPR# MKHS8T9UPJ.
  This APAR is closed as FIN. We have deferred the fix to a
   future release.
  

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

Applicable component levels

• R802 PSN

     UP