IJ29417: ASSERTION 'MYIDFROMFILE < 0 || ITER->ID == MYIDFROMFILE' OR IN GPFS LOG WHILE RESTORING A BACKUP ARCHIVE.

APAR status

• Closed as program error.

Error description

• If a CCR backup archive is used to
  restore the CCR component with the
  command 'mmsdrrestore -F <BACKUP_FILE> -a',
  the CCR component
  might run into an assertion
  'myIdFromFile < 0 || iter->id == myIdFromFile'
  or 'ccrAddr == iter->addr.addr'.
  

Local fix

• To avoid conflicting ccr.nodes files in
  /var/mmfs/tmp make sure that
  files starting with ccr.nodes are deleted
  in this directory before
  attempting 'mmsdrrestore -F <BACKUP_FILE> -a'.
  

Problem summary

• If a CCR backup archive is used to
  restore the CCR component with the
  command 'mmsdrrestore -F <BACKUP_FILE> -a',
  the CCR component
  might run into an assertion
  'myIdFromFile < 0 || iter->id == myIdFromFile'
  or 'ccrAddr == iter->addr.addr'.
  

Problem conclusion

• Benefits of the solution:
  No more assert
  
  Work around:
  To avoid conflicting ccr.nodes files in
  /var/mmfs/tmp make sure that
  files starting with ccr.nodes are deleted
  in this directory before
  attempting 'mmsdrrestore -F <BACKUP_FILE> -a'.
  
  Problem trigger:
  'mmsdrrestore -F <BACKUP_FILE> -a'
  to restore a cluster from
  a CCR backup file.
  
  Symptom:
  Abend/Crash
  
  Platforms affected:
  ALL Operating System environments
  
  Functional Area affected:
  admin command
  CCR
  
  Customer Impact:
  High Importance
  

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

  SPEC SCALE STD

• Fixed component ID

  5737F33AP

Applicable component levels