PM93875: VOBs are inaccessible and 'Error: Process not running on registry specified hostname' is logged by db_server

Rational ClearCase Fix Pack 8 (8.0.0.8) for 8.0
Rational ClearCase Fix Pack 1 (8.0.1.1) for 8.0.1
Rational ClearCase Fix Pack 11 (8.0.0.11) for 8.0
Rational ClearCase Fix Pack 4 (8.0.1.4) for 8.0.1
Rational ClearCase Fix Pack 5 (8.0.1.5) for 8.0.1
Rational ClearCase Fix Pack 12 (8.0.0.12) for 8.0
Rational ClearCase Fix Pack 6 (8.0.1.6) for 8.0.1
Rational ClearCase Fix Pack 13 (8.0.0.13) for 8.0
Rational ClearCase Fix Pack 14 (8.0.0.14) for 8.0
Rational ClearCase Fix Pack 7 (8.0.1.7) for 8.0.1
Rational ClearCase Fix Pack 15 (8.0.0.15) for 8.0
Rational ClearCase Fix Pack 8 (8.0.1.8) for 8.0.1
Rational ClearCase Fix Pack 16 (8.0.0.16) for 8.0
Rational ClearCase Fix Pack 9 (8.0.1.9) for 8.0.1
Rational ClearCase Fix Pack 17 (8.0.0.17) for 8.0
Rational ClearCase Fix Pack 10 (8.0.1.10) for 8.0.1
Rational ClearCase Fix Pack 18 (8.0.0.18) for 8.0
Rational ClearCase Fix Pack 11 (8.0.1.11) for 8.0.1
Rational ClearCase Fix Pack 19 (8.0.0.19) for 8.0
Rational ClearCase Fix Pack 12 (8.0.1.12) for 8.0.1
Rational ClearCase Fix Pack 20 (8.0.0.20) for 8.0
Rational ClearCase Fix Pack 13 (8.0.1.13) for 8.0.1
Rational ClearCase Fix Pack 21 (8.0.0.21) for 8.0
Rational ClearCase Fix Pack 14 (8.0.1.14) for 8.0.1
Rational ClearCase Fix Pack 15 (8.0.1.15) for 8.0.1
Rational ClearCase Fix Pack 16 (8.0.1.16) for 8.0.1
Rational ClearCase Fix Pack 17 (8.0.1.17) for 8.0.1
Rational ClearCase Fix Pack 18 (8.0.1.18) for 8.0.1
Rational ClearCase Fix Pack 19 (8.0.1.19) for 8.0.1
Rational ClearCase Fix Pack 20 (8.0.1.20) for 8.0.1
Rational ClearCase Fix Pack 21 (8.0.1.21) for 8.0.1
Rational ClearCase Fix Pack 22 (8.0.1.22) for 8.0.1
Rational ClearCase Fix Pack 23 (8.0.1.23) for 8.0.1
Rational ClearCase Fix Pack 24 (8.0.1.24) for 8.0.1
Rational ClearCase Fix Pack 25 (8.0.1.25) for 8.0.1

APAR status

• Closed as program error.

Error description

• It is possible that an IBM Rational ClearCase 8.0.1.x VOB server
  hosting ACL-enabled VOBs will not properly clean up VOB database
  tables in the db_server process if they were accessed by clients
  that had not been upgraded to ClearCase 8.0.1, leading the
  db_server in some cases to run out of file descriptors. If the
  VOB server makes use of the alternate_hostnames file and the
  db_server process is out of file descriptors and unable to open
  this file to check alternate hostnames, VOBs may become
  inaccessible and these errors will appear in the db_server log:
  
  ?date??time? db_server(?pid?): Error: Process not running on
  registry specified hostname (?hostname?)
  
  Steps to reproduce: Exact conditions are unknown. However
  accessing ACL-enabled VOBs with clients prior to ClearCase 8.0.1
  will increase the chances of running into this defect.
  
  Workaround: Do not access ClearCase 8.0.1 ACL-enabled VOBs using
  clients that have not been upgraded to ClearCase 8.0.1. If this
  issue does occur, restart ClearCase to terminate all running
  server processes that have used all available file descriptors.
  

Local fix

Problem summary

• It is possible that an IBM Rational ClearCase 8.0.1.x VOB server
  hosting ACL-enabled VOBs will not properly clean up VOB database
  tables in the db_server process if they were accessed by clients
  that had not been upgraded to ClearCase 8.0.1, leading the
  db_server in some cases to run out of file descriptors.
  

Problem conclusion

• A fix is available in ClearCase versions 8.0.0.8 and 8.0.1.1
  

Temporary fix

Comments

APAR Information

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

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

Fix information

• Fixed component name

  CC&CC MSITE UNI

• Fixed component ID

  5724G3301

Applicable component levels