IT42603: SWITCHING ORACLE DATABASES IN THE SAME SLA WITH LOG BACKUP ENABLED WILL CAUSE BACKUPS OF THAT DATABASE TO FAIL.

APAR status

• Closed as program error.

Error description

• IBM Spectrum Protect Plus Oracle backup with log backup enabled
  failed, after the database is disabled, and a new database is
  added to the same SLA with log backup enabled.
  Oracle backup error messages as follows:
  
  ERROR    1.66965E+12    Mon 28 Nov 2022 16:58:11 CET    2
  CTGGA4187    [Oracle_server] Return code 1:
  sudo -n mount /mnt/spp/vsnap/vpool1/fs113/9_152_133_173
  ERROR    1.66965E+12    Mon 28 Nov 2022 16:58:11 CET    2
  CTGGA4188    [Oracle_server] Output
  ["mount:/mnt/spp/vsnap/vpool1/fs113/9_152_133_173: can't find in
  /etc/fstab."]
  ERROR    1.66965E+12    Mon 28 Nov 2022 16:58:11 CET    2
  CTGGA4202    [Oracle_server] Cannot mount the CIFS  (SMB) share
  [None].
  ERROR    1.66965E+12    Mon 28 Nov 2022 16:58:11 CET    2
  CTGGF0065    [Oracle_server] Database ora_res: Log purge failed:
  

Local fix

• Workaround 1: run the SLA backup again, and the backup will be
  successful.
  Workaround 2: Disable the log backup for the affected database,
  run SLA
  backup, then re-enable log backup for the affected database.
  

Problem summary

• ****************************************************************
  * USERS AFFECTED:                                              *
  * IBM Spectrum Protect Plus level 10.1.13                      *
  ****************************************************************
  * PROBLEM DESCRIPTION:                                         *
  * See ERROR DESCRIPTION                                        *
  ****************************************************************
  * RECOMMENDATION:                                              *
  * Apply fixing level when available. This problem is currently *
  * projected to be fixed in IBM Spectrum Protect Plus level     *
  * 10.1.13.1, 10.1.14. Note that this is subject to change at   *
  * the discretion of IBM                                        *
  ****************************************************************
  

Problem conclusion

• This problem has been fixed so that after an Oracle database is
  switched to a new SLA policy, backup can be completed without
  error.
  

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

• Oracle
  

Fix information

• Fixed component name

  SP PLUS

• Fixed component ID

  5737SPLUS

Applicable component levels