IO17362: [MDVREGR IO16636] "sh" error running dbback or dbrestore

Tivoli Directory Server, Version 6.0.0.71-ISS-ITDS-IF0071
Tivoli Directory Server, Version 6.0.0.72-ISS-ITDS-IF0072

APAR status

• Closed as program error.

Error description

• The following error was observed running dbback or dbrestore on
  Linux. A similar error may occur on any non-windows platform
  running TDS versions 6.0.0.70.
  
    # ./idsdbback -I idsinst1 -k /tvo/backup
    GLPWRP123I The program '/opt/ibm/ldap/V6.2/sbin/32/dbback'
      is used with the following arguments '-I idsinst1 -k
      /tvo/backup'.
    sh: -c: line 0: unexpected EOF while looking for matching `''
    sh: -c: line 1: syntax error: unexpected end of file
    You have chosen to perform the following actions:
    ...
  
  A trace of the error shows in part:
  
    <timestamp> isProcessStarted: will run command='ps -p 9380|
      grep ' dbback'.
    sh: -c: line 0: unexpected EOF while looking for matching `''
    sh: -c: line 1: syntax error: unexpected end of file
    <timestamp> Error - isProcessStarted: stat(/tmp/ids_tmp_17127
      -1208105280_check_dbback_9380,0xbfe6a0b0) - errno=2
  

Local fix

• The only effect the error has on the operation of dbback or
  dbrestore is that it will fail to detect if another instance of
  dbback is already running. Unless you're in an environment where
  multiple administrators are all trying to back up or restore the
  same TDS instance at the same time, this can safely be ignored.
  

Problem summary

• APAR IO16636 in TDS 6.0.0.70 modified the command used to check
  if a process is running. The changes exposed an unrelated defect
  in a string library. The defect effects the formatting of
  strings to a maximum length when the string is less than that
  maximum. An audit of the code confirmed that (a) this is the
  only place this defect is exposed, and (b) "dbback" is the only
  process name < 8 characters which is checked in this way.
  
  The defect in the string library has been fixed.
  

Problem conclusion

• This problem was introduced by APAR IO16636 which is contained
  in the following maintenance packages:
  | MDVREGR 6.0.0.70-ISS-ITDS-IF0070 |
  The fix for this APAR is contained in the following maintenance
  packages:
  | interim fix | 6.0.0.71-ISS-ITDS-IF0071 |
  

Temporary fix

Comments

APAR Information

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

  IO16913

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

Fix information

• Fixed component name

  IBM TIV DIR SER

• Fixed component ID

  5724J3960

Applicable component levels

• R600 PSY

     UP