IT38653: ORACLE LOG BACKUP ON AIX FAILS WITH CTGGF0058 "[ERRNO 9] BAD FILE NUMBER"

APAR status

• Closed as program error.

Error description

• The log backup for Oracle databases running on AIX hosts using
  IBM Spectrum Protect Plus can fail with the messages seen in the
  joblog :
  
  DETAIL,..,CTGGF0044,[<OracleHost>] <DBName>: Log backup
                                     configuration started.
  DETAIL,..,CTGGF0045,[<OracleHost>] <DBName>: Log backup
                                     destination: /mnt/spp/vsnap/
                                     vpool<x>/fs123/<OracleHostIP
                                     withUnderscoresInsteadof
                                     Dots>/<DBName>
  DETAIL,..,CTGGF0052,[<OracleHost>] <DBName>: Configuring log
                                     backup with cron schedule 0
                                     0 4 8 12 16 20 * * *.
  DETAIL,..,CTGGF0053,[<OracleHost>] <DBName>: Adding cron job:
                                     /opt/IBM/SPP/logbackup/
                                     <DBName>/adbcd123.../
                                     logbackup.sh
  DETAIL,..,CTGGF0216,[<OracleHost>] Collecting log backup
                                     diagnostic files for
                                     database [<DBName>] from
                                     [/opt/IBM/SPP/logbackup/
                                     <DBName>/adbcd123...]
  DETAIL,..,CTGGF0056,[<OracleHost>] <DBName>: Running log backup
                                     job to capture latest
                                     archived logs: /opt/IBM/SPP/
                                     logbackup/<DBName>/adbcd123
                                     .../logbackup.sh
    WARN,..,CTGGF0058,[<OracleHost>] <DBName>: Last log backup
                                     run status: Log backup
                                     failed: [Errno 9] Bad file
                                     number
    WARN,..,CTGGF0060,[<OracleHost>] <DBName>: Failed to
                                     determine if log backup has
                                     been running on schedule.
  DETAIL,..,CTGGF0048,[<OracleHost>] <DBName>: Log backup
                                     configuration finished.
  
  In the application command.log found in the job log bundle, the
   following additional information will be displayed :
  
  .. INFO .. FileLock: Waiting for lock [SPP_ORACLE_LOG_LOCK_
                       <DBName>]
  .. INFO .. FileLock: Released lock [SPP_ORACLE_LOG_LOCK_
                       <DBName>]
  .. INFO .. worker_backup: Traceback (most recent call last):
    File "/opt/IBM/SPP/agents_spporc2/oracleagent/backup.py",
         line 384, in worker_backup
    File "/opt/IBM/SPP/agents_spporc2/python_AIX/lib/python3.6/
         contextlib.py", line 81, in __enter__
         return next(self.gen)
    File "/opt/IBM/SPP/agents_spporc2/oracleagent/runner.py",
         line 41, in FileLock
  OSError: [Errno 9] Bad file number
  
  This is due to an incorrect file lock handling by IBM Spectrum
  Protect Plus specific to AIX.
  
  | MDVREGR 10.1.8.0 5737SPLUS |
  
  IBM Spectrum Protect Plus Versions Affected:
  IBM Spectrum Protect Plus 10.1.8.1
  
  Additional Keywords: SPP, SPPLUS, TS007001475, ISPP-17138
  

Local fix

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.8 patch1                *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * see Error description                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed IBM Spectrum Protect Plus level 10.1.8 *
  * ifix2 and 10.1.9. Note that this is subject to change at the *
  * discretion of IBM.                                           *
  ****************************************************************
  

Problem conclusion

• Fixed an issue with the file locking that was causing this issue
  on AIX. After applying the fix the log backup will complete
  successfully without "[Errno 9] Bad file number" message
  

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:

Modules/Macros

• Apps     Oracle
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels