LO90061: NRF CREATED DELETING DATABASE VIA ADMIN PROCESS WHEN CREATE REDIRECT MARKER IS NOT SELECTED

APAR status

• Closed as fixed if next.

Error description

• NRF created deleting database via Admin Process when  Create
  redirect marker is not selected.
  When deleting a non-cluster database and its replicas using the
  Administration Process. Administrator chooses the following
  options:
  Check mark enabled " Also delete replicas of this database on
  all other servers"
  The  check mark beside " Create a marker that allows clients to
  update their references to this database" is NOT selected.
  The expectation is that the database and all its replicas will
  be removed from the different servers without creating a NRF
  (Notes Redirect File in any server)
  After all Administration Process request are completed the
  database and all its replicas are deleted, but NRF file is
  being created in all the secondary servers unexpectedly
  The 1st replica on the server working on is deleted
  immediately, and  as expected without creating a NRF file
  However, the other replicas which will be deleted by the adminp
  process are deleted, but a NRF file is being created.
  This behaviour is inconsistent and not as expected
  See as well SPR # SPRT6XYQ26 which is related (the check mark
  in the 'delete db' dialog indicating the redirect db (= NRF
  file) should be created is made to remember his last state
  (=made 'sticky')
  TEST - REPRODUCIBLE SCENARIO :
  1. Create a database on server#1 (any template, ie. 'doc lib')
  2. From this database, create a replica on server#2
  3. From the Administrator, initiate a db delete for this
  database.
  As the footnote in the dialog mentions, an adminp request will
  be generated to delete any replica(s)
  4. Check on OS level if the database was deleted on the 1st
  server, and no NRF file created
     >> all ok
  5. Check in the Administrations Request Db the adminp request
  made >> it does not contain any field 'ProxyDBRedirect'
  Remark:
  - When in the dialog 'Create a marker that allows...' is set,
  then  field 'ProxyDBRedirect' exists with value 1.
  - when the check mark is not set, there is no such field added
  to the adminp request
  So it appears this field should control the creation of the
  NRF in the adminp deletion process following
  In this occasion when the field 'Create a marker that
  allows...' is NOT SET only appears the
  Field Name: ProxyDBRedirectDisplay = "Unknown"
  6. Approve the adminp request to effectively delete the db on
  the 2nd server
  7. Check the adminp request has been carried out (so adminp
  then effectively has deleted the db)
  8. Check on OS level if the database was deleted, and no NRF
  file  created
   >> this is not ok !! The database was deleted but a NRF file
  was created
  So the deletion of the db was initiated requiring not to create
  a NRF file.
  The result is:
   - Deletion of the 1st replica and no NRF file is created
  (=direct  deletion, without any adminp intervention)
  - Deletion of other repica(s) but with creation of NRF file
  (=deletion done with adminp request(s))
  This behaviour is not as expected and inconsistent. The NRF
  file  creation should be the same for all for all replica's,
  not only for the  1st (which is deleted immediately when doing
  the deletion in the Administrator client)
  

Local fix

• Manually delete the NRF unexpected created files at opeating
  system level
  

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# BBSZAD7DZV.
  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

• R853 PSN

     UP