IBM Support

IT26295: REMOVING ORACLE DB FROM SLA DOES NOT CLEAN UP CRONTAB

Subscribe

You can track all active APARs for this component.

 

APAR status

  • Closed as program error.

Error description

  • Removing an SLA association from an Oracle database, with log
    backups enabled, does not remove the entry from the
    crontab file.
    This can result in more than one entry in crontab:
    Example:
    0 0,2,4,6,8,10,12,14,16,18,20,22 * * *
    /opt/IBM/SPP/logbackup/DBNAME/3dfb2ee82fa192a3ce80a0118f62ca00/l
    ogbackup.sh #? Added by SPP
    0 0,2,4,6,8,10,12,14,16,18,20,22 * * *
    /opt/IBM/SPP/logbackup/DBNAME/79b6b3f46cfa15d92f1e0887d98696a4/l
    ogbackup.sh #? Added by SPP
    0 0,2,4,6,8,10,12,14,16,18,20,22 * * *
    /opt/IBM/SPP/logbackup/DBNAME/40879cce0a17b7c574ffdc1644bc78df/l
    ogbackup.sh #? Added by SPP
    This can result in incorrect Oracle log back up attempts.
    Initial impact: Medium
    Versions affected: 10.1.1
    Keywords: TS001068036
    

Local fix

  • 1- Remove all entries from the crontab that end with "Added by
    SPP"
    2 - On the Oracle machine, remove all subfolders from
    /opt/IBM/SPP/logbackup
    If there are SLA's defined to any Oracle databases, the next
    time the SLA run the crontab entry will be recreated.
    

Problem summary

  • ****************************************************************
    * USERS AFFECTED:                                              *
    * IBM Spectrum Protect Plus levels 10.1.1.*                    *
    ****************************************************************
    * PROBLEM DESCRIPTION:                                         *
    * See ERROR DESCRIPTION                                        *
    ****************************************************************
    * RECOMMENDATION:                                              *
    * Apply fixing level when available. This problem is currently *
    * fixed in level 10.1.2 and higher.                            *
    * Note that this is subject to change at the discretion of IBM.*
    ****************************************************************
    

Problem conclusion

  • IBM Spectrum Protect Plus has  improved clean up operations
    under various conditions. The Oracle cleanup operation has been
    improved such that cron jobs that were created by the Oracle
     application agent are more reliably removed when no longer
    required. This includes when databases are removed from an SLA.
    

Temporary fix

  • 1- Remove all entries from the crontab that end with
    "Added by SPP"
    2 - On the Oracle machine, remove all subfolders from
    /opt/IBM/SPP/logbackup
    
    If there are SLA's defined to any Oracle databases, the next
    time the SLA run the crontab entry will be recreated.
    

Comments

APAR Information

  • APAR number

    IT26295

  • Reported component name

    SP PLUS

  • Reported component ID

    5737SPLUS

  • Reported release

    A11

  • Status

    CLOSED PER

  • PE

    NoPE

  • HIPER

    NoHIPER

  • Special Attention

    NoSpecatt / Xsystem

  • Submitted date

    2018-09-14

  • Closed date

    2018-09-20

  • Last modified date

    2018-09-20

  • 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

[{"Business Unit":{"code":"BU058","label":"IBM Infrastructure w\/TPS"},"Product":{"code":"SSNQFQ","label":"IBM Spectrum Protect Plus"},"Platform":[{"code":"PF025","label":"Platform Independent"}],"Version":"A11","Line of Business":{"code":"LOB26","label":"Storage"}}]

Document Information

Modified date:
30 January 2024