CCMs alerting if MAXDB Backup fails

Hi,
I want to see an red alert in CCMS (rz20, Method SDB_health_verify_rc_smcl_<SID>, ..Last Check Return Code) if the last return code of the backup is unequal 0. Does anyone have an idea how to custmize rz20 to do this ?
If I put the MTE default settings for monitoring the backup result, ( SDB_health_verify_rc_smcl_<SID>) I will get masses of errors during the backup is running, because than the return code is "9999 Running", which is unequal 0, but I'm only intressed in the result of the backup !
Any ideas ?
Greetings
Wolfgang

Hello Wolfgang,
if you are SAP customer, please review the SAP note 908722.
Please check what SAP Basis Support Package do you have on your system?
SAP note 908722 will change the alert for a running database structure check or a running backup < "9999 Running" > from RED (which was incorrect) to YELLOW. Check data and backup are critical actions in the system while they are running e.g. CHECK DATA sets locks on the table. Therefore both actions when they are active will be marked as yellow. When they has been finished correctly the alert will be green.
The SAP Alert Monitoring that we use to Monitor MaxDB operation does not offer a filter for specific return codes. Its is, however, possible to not raise an e-mail for YELLOW alerts while still raising an e-mail for RED alerts. If you would like to do this => add the parameter REACT_ON_ALERTS with the value RED to your auto-reaction methods.
This is documented in SAP note 671780.
If you're an SAP customer & have further questions/problems on this issue, could you please open the OSS message to the component BC-DB-SDB-CCM.
Please review the Rules of Engagement at
Welcome and Rules of Engagement
Thank you and best regards, Natalia Khlopina

Similar Messages

  • MAXDB backup failed with error: end of file reached -917

    Hi I am performing a complete data backup for a database which is about 230 GB.
    Previously it had run successfully for many days, but since yesterday, I began to receive such error:
    Error: end of file reached(-917)
    The backup stopped itself after running for 1 hour, and from backup history I just saw above error message.
    I also had a look at the logs, and found below, could someone help me look into this issue?
    Appreciate your kind help in advance!
    2008-11-25 22:08:09      0xBE4 ERR 52012 SAVE     error occured, basis_err 5750
    2008-11-25 22:08:09      0xBE4 ERR     3 Backup   Data backup failed
    2008-11-25 22:08:09      0xBE4 ERR     1 Backup    +   Backupmedium #1 (F:\Dbbackup\QAS_data_01) end of file reached
    2008-11-25 22:08:09      0xBE4 ERR     6 KernelCo  +   Backup error occured, Error code 5750 "write_task_crash"
    2008-11-25 04:00:27     0x16A0     52024 SAVE     30462712 pages -> "F:\DBbackup\QAS_DATA"
    2008-11-25 04:00:28     0x1BE4     19626 IO       Async I/O thread stopped, 'F:\DBbackup\QAS_DATA'
    2008-11-25 04:00:28     0x1FC4     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0001'
    2008-11-25 04:00:28     0x1688     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0002'
    2008-11-25 04:00:28     0x15D4     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0003'
    2008-11-25 04:00:28      0xAEC     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0004'
    2008-11-25 04:00:28     0x179C     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0005'
    2008-11-25 04:00:28      0xDD4     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0006'
    2008-11-25 04:00:28     0x1AE8     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0007'
    2008-11-25 04:00:28     0x176C     19626 IO       Async I/O thread stopped, 'E:\sapdb\QAS\DAT_0008'
    2008-11-25 04:00:28     0x11B8     19626 IO       Async I/O thread stopped, 'G:\sapdb\QAS\DAT_0009'
    2008-11-25 04:00:28     0x1B4C     19626 IO       Async I/O thread stopped, 'G:\sapdb\QAS\DAT_0010'
    2008-11-25 04:00:28     0x1F60     19626 IO       Async I/O thread stopped, 'G:\sapdb\QAS\DAT_0011'
    2008-11-25 04:00:35      0xB8C     52012 SAVE     ready
    2008-11-25 04:00:35      0xB8C     19651 CONNECT  Connection released, T113
    Thanks,
    vivian

    Hello Shaun,
    Thank you so much for your reply. But I've checked that my F drive still have more than 480GB free space, so the space should not be the problem.
    And I've just run the backup once again, this time it keeps running for 2 hours, and then failed again with the same error.
    Is there other possible reasons of this error?
    Thanks a lot,
    Vivian

  • CCMS Alert for Backup DB2 on OS390

    Experts
    We would like to configure CCMS Alert for backup failures on the Db2 database which resides on z/OS. I have an option in RZ20 to configure , but it tell me which tablespaces needed fort the backup. it dosent tell you whether the backup is success or failed. I can see the status from the backup history in db2 t code. So how do we configure?do we really have an option to use the same.
    Regards,
    Mahesh Shetty

    Hi,
    did you check this SDN Document regarding your monitoring problem?
    [SAP DB Admin Guide for DB2|http://www.sdn.sap.com/irj/scn/go/portal/prtroot/docs/library/uuid/5a6c489b-0501-0010-7ab2-80450fc6ce60?quicklink=index&overridelayout=true]
    Kind regards,

  • CCMS alert emails for failed jobs

    Hello All
    What are the steps to set a ccms alert for failed jobs? Also is it possible to set ccms to warn us of long running jobs. I would like to set the sysem so that we get a email notification on any failed jobs or long running jobs.
    I appreciate any input or leads.
    Thanks

    Hi,
    You can get the alerts for failed jobs, Just maintain the realted setting in the ccms_onalert_email
    maintain the address and then assign this as auto reaction method in your ccms template for background jobs.
    Also i request to search SDN there are many threads related to auto reaction mails.
    Regards,
    Vamshi.

  • MaxDB backup through Backint on Oracle for TSM

    Hello Gurus:
    We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
    I checked some forums and configured but backint is not recognizing MaxDB parameter file. Please see below parameter file and error logs.
    *BSI File:*
    BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    INPUT D:\sapdb\data\wrk\backint\sapdb.in
    OUTPUT D:\sapdb\data\wrk\backint\sapdb.out
    ERROROUTPUT D:\sapdb\data\wrk\backint\sapdb.err
    PARAMETERFILE D:\sapdb\data\wrk\LCD\maxdb_config.par
    ORIGINAL_RUNDIRECTORY L:\sapdb\LCD\sapdata
    *Parameter File - MaxDB_config*
    STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
    FILES PER BACKINT CALL:     2
    BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    PARAMETERFILE OF BACKINT:     D:\oracle\SCD\102\database\initSCD.utl
    HISTORY FILE:     D:\sapdb\data\wrk\BackintHistory
    INPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.in
    OUTPUTFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.out
    ERRORFILE OF BACKINT:     D:\sapdb\data\wrk\backint\backint.err
    MAXIMAL DELAY OF BACKINT CALL:     30
    Error Logs:
    2010-03-30 17:38:35
    Using environment variable 'TEMP' with value 'C:\Windows\TEMP' as directory for temporary files and pipes.
    Using connection to Backint for MaxDB Interface.
    2010-03-30 17:38:35
    Checking existence and configuration of Backint for MaxDB.
        Using environment variable 'BSI_ENV' with value 'D:\sapdb\data\wrk\LCD\bsi.env' as path of the configuration file of Backint for MaxDB.
        Reading the Backint for MaxDB configuration file 'D:\sapdb\data\wrk\LCD\bsi.env'.
            Found keyword 'BACKINT' with value 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe'.
            Found keyword 'INPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.in'.
            Found keyword 'OUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.out'.
            Found keyword 'ERROROUTPUT' with value 'D:\sapdb\data\wrk\backint\sapdb.err'.
            Found keyword 'PARAMETERFILE' with value 'D:\sapdb\data\wrk\LCD\maxdb_config.par'.
            Found keyword 'ORIGINAL_RUNDIRECTORY' with value 'L:\sapdb\LCD\sapdata'.
        Finished reading of the Backint for MaxDB configuration file.
        Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
        Using 'D:\sapdb\data\wrk\backint\sapdb.in' as input file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\backint\sapdb.out' as output file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\backint\sapdb.err' as error output file for Backint for MaxDB.
        Using 'D:\sapdb\data\wrk\LCD\maxdb_config.par' as parameter file for Backint for MaxDB.
        Using '300' seconds as timeout for Backint for MaxDB in the case of success.
        Using '300' seconds as timeout for Backint for MaxDB in the case of failure.
        Using 'L:\sapdb\LCD\sapdata\dbm.knl' as backup history of a database to migrate.
        Using 'L:\sapdb\LCD\sapdata\dbm.ebf' as external backup history of a database to migrate.
        Checking availability of backups using backint's inquire function.
    Check passed successful.
    2010-03-30 17:38:35
    Checking medium.
    Check passed successfully.
    2010-03-30 17:38:35
    Preparing backup.
        Setting environment variable 'BI_CALLER' to value 'DBMSRV'.
        Setting environment variable 'BI_REQUEST' to value 'NEW'.
        Setting environment variable 'BI_BACKUP' to value 'FULL'.
        Constructed Backint for MaxDB call 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c'.
        Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.out' as output for Backint for MaxDB.
        Created temporary file 'D:\sapdb\data\wrk\backint\sapdb.err' as error output for Backint for MaxDB.
        Writing '
    .\pipe\BACKscd #PIPE' to the input file.
    Prepare passed successfully.
    2010-03-30 17:38:35
    Starting database action for the backup.
        Requesting 'SAVE DATA QUICK TO '
    .\pipe\BACKscd' PIPE BLOCKSIZE 8 NO CHECKPOINT MEDIANAME 'Back123'' from db-kernel.
    The database is working on the request.
    2010-03-30 17:38:35
    Waiting until database has prepared the backup.
        Asking for state of database.
        2010-03-30 17:38:35 Database is still preparing the backup.
        Waiting 1 second ... Done.
        Asking for state of database.
        2010-03-30 17:38:36 Database has finished preparation of the backup.
    The database has prepared the backup successfully.
    2010-03-30 17:38:36
    Starting Backint for MaxDB.
        Starting Backint for MaxDB process 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe -u LCD -f backup -t file -p D:\sapdb\data\wrk\LCD\maxdb_config.par -i D:\sapdb\data\wrk\backint\sapdb.in -c >>D:\sapdb\data\wrk\backint\sapdb.out 2>>D:\sapdb\data\wrk\backint\sapdb.err'.
        Process was started successfully.
    Backint for MaxDB has been started successfully.
    2010-03-30 17:38:36
    Waiting for end of the backup operation.
        2010-03-30 17:38:36 The backup tool process has finished work with return code 2.
        2010-03-30 17:38:36 The backup tool is not running.
        2010-03-30 17:38:36 The database is working on the request.
        2010-03-30 17:38:36 The database is working on the request.
        2010-03-30 17:38:41 The database is working on the request.
        2010-03-30 17:38:51 The database is working on the request.
        2010-03-30 17:39:06 The database is working on the request.
        2010-03-30 17:39:26 The database is working on the request.
        2010-03-30 17:39:37 Canceling Utility-task after a timeout of 60 seconds elapsed ... OK.
        2010-03-30 17:39:38 The database has finished work on the request.
        Receiving a reply from the database kernel.
        Got the following reply from db-kernel:
            SQL-Code              :-903
    The backup operation has ended.
    2010-03-30 17:39:38
    Filling reply buffer.
        Have encountered error -24920:
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
        Constructed the following reply:
            ERR
            -24920,ERR_BACKUPOP: backup operation was unsuccessful
            The backup tool failed with 2 as sum of exit codes. The database request was canceled and ended with error -903.
    Reply buffer filled.
    2010-03-30 17:39:38
    Cleaning up.
        Copying output of Backint for MaxDB to this file.
        **-- Begin of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)--**
                                     **Data Protection for SAP(R)**
                         **Interface between BRTools and Tivoli Storage Manager***
                         **- Version 6, Release 1, Modification 0.0  for Win x64 -**
                               **Build: 358  compiled on Nov  4 2008**
                    **(c) Copyright IBM Corporation, 1996, 2008, All Rights Reserved.**
            **BKI8310E: The keyword MAXIMAL is not allowed.**
            **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
            **BKI0020I: End of program at: 03/30/10 17:38:36 .**
            **BKI0021I: Elapsed time: 00 sec .**
            **BKI0024I: Return code is: 2.**       
    End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
        Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
        Copying error output of Backint for MaxDB to this file.
    Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
    End of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
        Removed Backint for MaxDB's temporary error output file 'D:\sapdb\data\wrk\backint\sapdb.err'.
        Removed the Backint for MaxDB input file 'D:\sapdb\data\wrk\backint\sapdb.in'.
    Have finished clean up successfully.
    Any help will be appreciated.
    Thanks,
    Miral.

    > We are using TSM backint interface for Oracle database. We are in the process of implementing SCM. We would like to schedule MaxDB backup through backint interface for Oracle.
    > *BSI File:*
    >
    > BACKINT D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    > *Parameter File - MaxDB_config*
    > STAGING AREA:     D:\TEMP\STAGE1 1024000 KB
    > FILES PER BACKINT CALL:     2
    > BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    >
    >     Using 'D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe' as Backint for MaxDB program.
    > 2010-03-30 17:39:38
    > Cleaning up.
    >     Copying output of Backint for MaxDB to this file.
    >                                  **Data Protection for SAP(R)**
    >                      **Interface between BRTools and Tivoli Storage Manager***
    >                      **- Version 6, Release 1, Modification 0.0  for Win x64 -**
    >         **BKI8310E: The keyword MAXIMAL is not allowed.**
    >         **BKI1001E: syntax error in file 'D:\sapdb\data\wrk\LCD\maxdb_config.par'. Exiting program.**
    >         **BKI0020I: End of program at: 03/30/10 17:38:36 .**
    >         **BKI0021I: Elapsed time: 00 sec .**
    >         **BKI0024I: Return code is: 2.**       
    >
    >     -
    End of output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.out)----
    >     Removed Backint for MaxDB's temporary output file 'D:\sapdb\data\wrk\backint\sapdb.out'.
    >     Copying error output of Backint for MaxDB to this file.
    >     -
    Begin of error output of Backint for MaxDB (D:\sapdb\data\wrk\backint\sapdb.err)----
    @Markus: thanks for the hint with the quote-formatting option!
    Concerning the issue:
    Sorry, but you misunderstood the way how the general BACKINT for Oracle interface is used with MaxDB.
    See, MaxDB comes with a own BACKINT executable.
    This is a enhanced BACKINT tools that allows pipes as data input channels - which is not supported by the Backint for Oracle.
    The MaxDB Backint serves as a adapter program between the MaxDB Kernel and the backint for Oracle program.
    So instead of
    BACKINT:     D:\usr\sap\SCD\SYS\exe\uc\NTAMD64\backint.exe
    you should point it to the MaxDB provided adapater program.
    I propose to revisit the documentation on that topic [Connecting to a Backint for Oracle Interface |http://maxdb.sap.com/doc/7_7/45/746a5712e14022e10000000a1553f6/content.htm].
    best regards,
    Lars

  • MaxDB backup problem through Data protector

    When I start the Online MaxDB database backup through Data Protector GUI the backup fails with error as below,
    Normal] From: BSM@ttcsap10 "MAXDB_Online" Time: 6/17/10 4:30:49 AM
    OB2BAR application on "ttcmaxdr" successfully started.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
    Executing the dbmcli command: `user_logon'.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
    Executing the dbmcli command: `dbm_configset -raw set_variable_1 OB2OPTS=""'.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
    Executing the dbmcli command: `dbm_configset -raw set_variable_2 OB2APPNAME=MAX'.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
    Executing the dbmcli command: `dbm_configset -raw set_variable_3 OB2BARHOSTNAME=ttcmaxdr'.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:50
    Executing the dbmcli command: `dbm_configset -raw set_variable_4 TimeoutWaitFiles=30'.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
    Executing the dbmcli command: `dbm_configset -raw BSI_ENV /var/opt/omni/tmp/MAX.bsi_env'.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
    Executing the dbmcli command: `medium_put BACKDP-Data[2]/1 /var/opt/omni/tmp/MAX.BACKDP-Data[2].1 PIPE DATA 0 8'.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
    Executing the dbmcli command: `medium_put BACKDP-Data[2]/2 /var/opt/omni/tmp/MAX.BACKDP-Data[2].2 PIPE DATA 0 8'.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
    Executing the dbmcli command: `util_connect'.
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:30:51
    Executing the dbmcli command: `backup_start BACKDP-Data[2] DATA'.
    [Critical] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:31:45
    Error: SAPDB responded with:
    -24988,ERR_SQL: SQL error
    -903,Host file I/O error
    3,Data backup failed
    17,Servertask Info: because Error in backup task occured
    10,Job 2 (Backup / Restore Medium Task) [executing] WaitingT170 Result=3700
    6,Error in backup task occured, Error code 3700 "hostfile_error"
    1,Backupmedium #1 (/var/opt/omni/tmp/MAX.BACKDP-Data[2].1) Wrong file type
    6,Backup error occured, Error code 3700 "hostfile_error"
    17,Servertask Info: because Error in backup task occured
    10,Job 1 (Backup / Restore Medium Task) [executing] WaitingT170 Result=3700
    6,Error in backup task occured, Error code 3700 "hostfile_error"
    [Normal] From: OB2BAR_SAPDBBAR@ttcmaxdr "MAX" Time: 06/17/10 04:31:45
    Executing the dbmcli command: `exit'.
    [Normal] From: BSM@ttcsap10 "MAXDB_Online" Time: 6/17/10 4:31:46 AM
    OB2BAR application on "ttcmaxdr" disconnected.
    [Critical] From: BSM@ttcsap10 "MAXDB_Online" Time: 6/17/10 4:31:46 AM
    None of the Disk Agents completed successfully.
    Session has failed.
    [Normal] From: BSM@ttcsap10 "MAXDB_Online" Time: 6/17/10 4:31:46 AM
    Backup Statistics:
    Session Queuing Time (hours) 0.00
    Completed Disk Agents ........ 0
    Failed Disk Agents ........... 0
    Aborted Disk Agents .......... 0
    Disk Agents Total ........... 0
    ========================================
    Completed Media Agents ....... 0
    Failed Media Agents .......... 0
    Aborted Media Agents ......... 0
    Media Agents Total .......... 0
    ========================================
    Mbytes Total ................. 0 MB
    Used Media Total ............. 0
    Disk Agent Errors Total ...... 0
    But I have noticed the error is because of this line as below,
    Executing the dbmcli command: `medium_put BACKDP-Data[2]/1 /var/opt/omni/tmp/MAX.BACKDP-Data[2].1 PIPE DATA 0 8'.
    Actually it should execute the dbmcli command as
    medium_put BACKDP-Data[2]/1 /var/opt/omni/tmp/MAX.BACKDP-Data[2].1 PIPE DATA 0 8 NO NO \" \" "BACK"
    But I donu2019t know where to make changes so that when I start the backup through DP GUI it should use backup tool as u201CBACKu201D
    But same DP backup specification is working through MaxDB Database Manager GUI.
    Any solution appreciatedu2026
    Thanks,
    Subba

    Hi Natalia,
    Thanks for the reply...Please find the answer as below,
    -> What is the version of Data Protector?
    Data Protector 5.5
    -> What is the version of the database?
    SAP MaxDB 7.6
    -> According your information you could use the DBMGUI to create the medium of u201CBACKu201D type and create the databackup using this medium. Correct?
    Yes
    The problems are with Data Protector GUI, not with MAXDB or DBMGUI. Correct?
    Yes
    Please let me know where to make any changes or any enviornment settings to be done in Data Protector GUI so that it will use the medium "BACK" as backup tool while i start the backup through Data Protector GUI.
    Thanks,
    Subba

  • ACS 5.3.0.40 On-demand Full Backup failed.

    Hi,
    I have ACS 5.3.0.40 Primary Secondary Authenticators , of which the Scheduled backup has stopped.
    When checked the :
    Monitoring Configuration >
    System Operations >
    Data Management >
    Removal and Backup
    > Incremental Backup , it had changed to OFF mode. without any reason.
    The same was observed earlier too.
    I have made the
    Incremental Backup to ON and intiated the
    View Full Database Backup Now. But it wasn't successful and reported an Error:
    FullBackupOnDemand-Job Incremental Backup Utility System Fri Dec 28 11:56:57 IST 2012 Incremental Backup Failed: CARS_APP_BACKUP_FAILED : -404 : Application backup error Failed
    Later i did the acs stop/start  "view-jobmanager" and  initiated the On-demand Full Backup , but no luck, same error reported this time too.
    Has any one faced similar type of error /problem reported , please let me know the solution.
    Thanks & Regards.

    One other thing; if this does end up being an issue with disk space it is worth considering patch 5.3.0.40.6 or later since improves database management processes
    This cumulative patch includes fixes/enhancements related to disk management to avoid following issue
    CSCtz24314: ACS 5.x *still* runs out of disk space
    and also fix for
    CSCua51804: View backup fails   even when there is space in disk
    Following is taken from the readme for this patch
       The Monitoring and Reporting database can increase when as records are collected. There are two mechanisms to reduce this size and prevent it from exceeding the maximum limit.
    1. Purge: In this mechanism the data will be purged based on the configured data retention period or upon reaching the upper limit of the database.
    2. Compress: This mechanism frees up unused space in the database without deleting any records.
    Previously the compress option could only be run manually. In ACS 5.3 Patch 6 there are enhancements so it will run daily at a predefined time, automatically when specific criteria are met. Similarly by default purge job runs every day at 4 AM. In Patch 6 new option provided to do on demand purge as well.
    The new solution is to perform the Monitoring and Reporting database compress automatically.
    2.       New GUI option is provided to enable the Monitoring and Reporting database compress to run on every day at 5 AM. This can be configured under GUI Monitoring And Configuration -> System Operations -> Data Management -> Removal and Backup
    3.       Changed the upper and lower limit of purging of Monitoring and Reporting data. This is to make sure at lower limit itself ACS has enough space to take the backup. The maximum size allocated for monitoring and reporting database is 42% of /opt( 139 GB). The lower Limit at which ACS purges the data by taking the backup is 60% of maximum size Monitoring and Reporting database (83.42 GB). The upper limit at which ACS purges the data without taking backup is 80% of maximum size Monitoring and Reporting database (111.22 GB).
    4. The acsview-database compress operation stops all services till 5.3 patch 5 , now only Monitoring and Reporting related services are stopped during this operation.
    5. Provided “On demand purge” option in Monitoring and Reporting GUI. This option will not try to take any backup, it will purge the data based on window size configured.
    6. Even if the “Enable ACS View Database compress” option is not enabled in GUI then also automatic view database compress will be triggered if the physical size of Monitoring and Reporting database reached to the upper limit of its size.
    7. This automatic database compress takes place only when the “LogRecovery” feature is enabled, this is to make sure that the logging which happens during this operation will be recovered once this operation is completed. ACS generates alert when there is a need to do automatic database compress and also to enable this feature.
    8. Before enabling “LogRecovery” feature configure the Logging Categories in such way that only mandatory data to log into Local Log Target and Remote Log Target as Log collector under System Administration > ... > Configuration > Log Configuration
    This “LogRecovery” feature can recover the logs only if the logs are present under local log target.
    9       This automatic database compress operation also performed only when the difference between actual and physical size of Monitoring and Reporting database size is > 50GB.
    10 The new CLI “acsview” with option “show-dbsize” is provided to show the actual and physical size of the Monitoring and Reporting database. This is available in “acs-config” mode.
               acsview     show-dbsize     Show the actual and physical size of View DB and transaction log file

  • CCMS alert for Bckground Job

    Dear Experts,
                        I need to configure mail alert through solman for failed backgrougnd job in R/3 system. Please can anyone share configuration guide.
    Regards,
    Sampath

    Hi Sampath,
    please visit http://service.sap.com/solutionmanagerbp. There you'll find a link to the Best Practice document "Background Job Monitoring with SAP Solution Manager" (number 064). The document is mainly about job monitoring as part of Business Process Monitoring (which I would actually recommend). Nevertheless at the beginning of the document also the CCMS job monitoring is briefly explained.
    Best Regards
    Volker

  • CCMS Alert for Stuck Queue

    Hi
    I want to setup alert for any ABAP Dump or any Failed XML Message.
    Requirement is that it should come to me as an email like:
    System:SID
    Client:xxx
    Text:a brief description of the Dump or XML message
    I have setup CCMS and GRMG but I am receiving mails regarding GRMG Heartbeats only and not related to other CCMS alerts.
    I have seen the weblogs available in the SDN.
    Thanks in advance

    Hello Sundara
    You can setup CCMS for J2EE in the following ways
    1. Setup system monitoring in DSWP as you do for ABAP systems
    2. Installing and Registering sapccmsr agents
    3. Availability Monitoing by GRMG Lite and GRMG
    4. Setting up Central Autoreaction
    5. E2E analysis (Solution Manager Diagonostic)
    Four options are excellently elaborated in the following link
    Setting Up your Central Monitoring [original link is broken]
    and E2E
    http://service.sap.com/diagnostics
    If you face any problem in any of these, revert back
    thanks
    Bhudev

  • Incorrect time of CCMS alerts, alerts getting delayed by more than a day

    Hi All,
    We have SOLMAN 4.0 and configured the autoreaction method for alert on e-mail centrally on SOLMAN for a client in DEV(100). The configuration is correct and we are able to receive the CCMS alerts, however, the alerts are getting delayed by more than a day. Alerts are getting generated every 3-5 minutes and in the central autoreaction method zCCMS_OnAlert_Email_Central i have added a parameter TIME_ZONE and gave the value as PST as our servers are all on PST.
    The following is an example of the alert that I received:
    ALERT for DEV \ Workload Collector \ Workload Collector Frame \ Collectorframe Messages at 20070910 215114 ( Time in UTC )
    System: DEV at 20070910 145114 ( Time in PST ) RED CCMS alert for monitored object Collectorframe Messages Alert Text:Determination of component from SCR failed System:DEV Segment:SAP_CCMS_e47dev_DEV_00 MTE:DEV\Workload Collector\Workload Collector Frame\Collectorframe Messages Client:000 User:DDIC
    Severity:        0
    I received the above alert at 15:45 after changing the "set wait time" to 15:30. However, in Tx. SOST, this alert was supposed to reach at 23:52 on 2007 09 10 which is like almost a day to receive the alert?
    Is this any configuration issue? The job which was scheduled to run every 3 minutes in SCOT to send e-mails is running fine without any delay.
    Please help me!!!

    > Hi All,
    > We have SOLMAN 4.0 and configured the autoreaction
    > method for alert on e-mail centrally on SOLMAN for a
    > client in DEV(100). The configuration is correct and
    > we are able to receive the CCMS alerts, however, the
    > alerts are getting delayed by more than a day. Alerts
    > are getting generated every 3-5 minutes and in the
    > central autoreaction method
    > zCCMS_OnAlert_Email_Central i have added a parameter
    > TIME_ZONE and gave the value as PST as our servers
    > are all on PST.
    >
    > The following is an example of the alert that I
    > received:
    >
    > ALERT for DEV \ Workload Collector \ Workload
    > Collector Frame \ Collectorframe Messages at 20070910
    > 215114 ( Time in UTC )
    > System: DEV at 20070910 145114 ( Time in PST ) RED
    > CCMS alert for monitored object Collectorframe
    > Messages Alert Text:Determination of component from
    > SCR failed System:DEV Segment:SAP_CCMS_e47dev_DEV_00
    > MTE:DEV\Workload Collector\Workload Collector
    > Frame\Collectorframe Messages Client:000 User:DDIC
    > Severity:        0
    >
    > I received the above alert at 15:45 after changing
    > the "set wait time" to 15:30. However, in Tx. SOST,
    > this alert was supposed to reach at 23:52 on 2007 09
    > 10 which is like almost a day to receive the alert?
    >
    > Is this any configuration issue? The job which was
    > scheduled to run every 3 minutes in SCOT to send
    > e-mails is running fine without any delay.
    >
    > Please help me!!!
    Any ideas on the above issue?

  • Backup Failed (error -24988 and -903)

    Hello All,
    MaxDb 7.6.03.03 on Windows 2003 Server (32 bit).
    I've an instance that run fine since several years now, which is backed up using a simple script:
    @echo off
    echo ============================= >> d:maxdbscripts ackup.log
    echo. | date | find "current" >> d:maxdbscripts ackup.log
    echo. | time | find "current" >> d:maxdbscripts ackup.log
    del f:     orpedo_com
    "c:program filessdbprogramspgmdbmcli" -d torpedo -n srv-sgbd2 -u ***,*** -i D:maxdbscripts ackup_torpedo.script
    xcopy f:     orpedo_com t: /y >> d:maxdbscripts ackup.log
    echo. | time | find "current" >> d:maxdbscripts ackup.log
    Here the backup_torpedo.script:
    util_connect ****,******
    backup_start complet data
    util_release
    Every thing work fine, until monday: the backup script failed with error code -903 and -24998:
    D:maxdbscripts>backup_torpedo.bat
    >util_connect ***,*****
    OK
    >backup_start complet data
    ERR
    -24988,ERR_SQL: SQL error
    -903,Host file I/O error
    3,Data backup failed
    The database error file say that:
    2009-07-29 08:53:55     0x13EC ERR 18008 TASKING  Could not create thread: 'ASYNCi', rc = 8
    2009-07-29 08:53:55     0x14D4 ERR 52011 SAVE     devspace: surprising blk cnt:
    2009-07-29 08:53:56     0x14D4 ERR 52012 SAVE     error occured, basis_err 3700
    2009-07-29 08:53:56     0x14D4 ERR     3 Backup   Data backup failed
    I've tried to remove and recreate the backup medium, lauch the backup from dbmgui, but i still have the same error.
    There is far enougth place on f: disk (83Gb, database size is 40Gb).
    I've tried to move the backup medium from f: disk to d: disk, but i still have te same errors.
    There is nothing related on event viewer on the server.
    The online documentation don't say anything usefull about this 2 errors messages.
    No changes have been made on the server nor the database, no update, nothing.
    Any idea ?
    TIA
    Frédéric.

    Yeah, problem solved !
    I've moved batch scripts from this server to another one, and the backup run fine !
    Look's like i ran out of shared memory, file descriptor or something like that.
    Maybe this could help someone later...
    Frédéric.

  • I want all ccms alerts come into my solution manager

    Hello,
    I want to monitor all the ccms alerts in all the systems from my solution manager.
    We are using solmon (4.0) SP 14.
    We are using ECC6, all systems in the landscape should configure to solmon
    Like if any backgroind job fails it should come to somon alert inbox,if it coming near to any threshold i should get a alert in solmon alert in box,what ever it shows yellow or red ccms it should come to solmon
    please help me in doing this
    Regards
    Mahesh

    Mahesh,
    That is possible with solution manager. You need to define system landscape and setup the system monitoring, central system administration.
    Please check transactions codes SMSY, DSWP and SDCCN.
    http://help.sap.com/saphelp_nw04/helpdata/en/02/5ec13690581b20e10000009b38f839/frameset.htm
    http://service.sap.com/rkt-solman
    Hope this helps.
    Manoj Chintawar
    Edited by: Manoj Chintawar on Mar 17, 2009 8:29 AM

  • Email Alerts for Scheduled Backup Failures on Cisco UCM?

    Hi,
    I never set this up before or know if this is possible.  Can I setup email alerts on Cisco UCM 8.X when a scheduled backup fails?
    I specified the SMTP host under the OS administration page, but that is it.
    Please let me know if this is possible and if so how I can set this up?
    Thank you in advanced!
    -rya

    Rya
    You'll be looking for the CiscoDRFFailure in Alert Central of RTMT. The alert can be configured to send a free text alert to an email address on backup failure.

  • ACS 5.3 Backup fails

    ACS 5.3 on VM- backup fails all the time. I opened several tickets with Cisco, but still no luck.
    Here is one of the log message I got during the backup. Maybe someone can point out what the issue is.
    debugd[2933]: [31965]: config:kron: cs_api.c[1142] [daemon]: occurrence occurrence_backup1 could not be deleted.

    I just did it on my ACS 5.4 patch 6 (running on VMWare) backup to a Windows 2003 FTP server and it works without any issues:
    repository ftp_192.168.1.129
      url ftp://192.168.1.129/
      user Administrator password hash e50ffb9aabc8ccebe066f6239efeaa1ab728a16f2b2
    labacs2/admin# backup labacs2 repository ftp_192.168.1.129
    % Creating backup with timestamped filename: labacs2-140628-2059.tar.gpg
    Calculating disk size for /opt/backup/backup-labacs2-1403989173
    Total size of backup files are 27 M.
    Max Size defined for backup files are 13339 M.
    labacs2/admin#

  • Windows Server 2008 R2 Backup failing with error - 0x8004231F

    Hi,
    I have Windows Server 2008 R2 Web Edition. Everything was working fine until recently. I tried checking for the log files, but I see that there are no log files that are created now in the location C:\Windows\Logs\WindowsServerBackup. The only files that
    are being created recently are of the type mentioned below.
    Wbadmin.1.etl
    WbadminUI.0.etl
    etc.
    I tried removing the old backup and starting a new backup. But, even now it is failing with the same error.
    When running the backup from the PowerShell, the output is as below.
    PS C:\Users\administrator> Wbadmin start backup -backupTarget:\\localhost\E$\WindowsImageBackup\Server01 -systemState -vss
    Copy
    wbadmin 1.0 - Backup command-line tool
    (C) Copyright 2004 Microsoft Corp.
    Note: The backed up data cannot be securely protected at this destination.
    Backups stored on a remote shared folder might be accessible by other
    people on the network. You should only save your backups to a location
    where you trust the other users who have access to the location or on a
    network that has additional security precautions in place.
    Retrieving volume information...
    This will back up volume System Reserved (100.00 MB) (Selected Files),SAN(I:) (Selected Files),Local Disk(C:) (Selected
    Files) to \\localhost\E$\WindowsImageBackup\Server01.
    Do you want to start the backup operation?
    [Y] Yes [N] No y
    The backup operation to \\localhost\E$\WindowsImageBackup\Server01 is starting.
    Starting to back up the system state [12/8/2013 9:29 AM]...
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Creating a shadow copy of the volumes specified for backup...
    Summary of the backup operation:
    The backup of the system state failed [12/8/2013 9:30 AM].
    Log of files successfully backed up:
    C:\Windows\Logs\WindowsServerBackup\Backup-08-12-2013_09-29-49.log
    Log of files for which backup failed:
    C:\Windows\Logs\WindowsServerBackup\Backup_Error-08-12-2013_09-29-49.log
    There is not enough disk space to create the volume shadow copy on the storage location. Make sure that, for all volumes
     to be backup up, the minimum required disk space for shadow copy creation is available. This applies to both the backup
     storage destination and volumes included in the backup.
    Minimum requirement: For volumes less than 500 megabytes, the minimum is 50 megabytes of free space. For volumes more th
    an 500 megabytes, the minimum is 320 megabytes of free space.
    Recommended: At least 1 gigabyte of free disk space on each volume if volume size is more than 1 gigabyte.
    ERROR - A Volume Shadow Copy Service operation error has
    occurred: (0x8004231f)
    Insufficient storage available to create either the shadow copy storage file or other shadow copy data.
    If you see the free space available in each of the drives, they are in plenty.
    C:\ 7.5 GB free of 70 GB
    E:\ 250 GB free of 499 GB
    I:\ 86.7 GB free of 350 GB
    I am out of any hints on how I can proceed now. Has any one had similar issues? Can any one give any hint on this? Thanks.
    Thanks.

    Some Additional info.
    Shadow Copy Storage association
       For volume: (\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}\)\\?\Volume{a9f
    b0474-f1bd-11e0-b235-806e6f6e6963}\
       Shadow Copy Storage volume: (\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}
    \)\\?\Volume{a9fb0474-f1bd-11e0-b235-806e6f6e6963}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 32 MB (32%)
    Shadow Copy Storage association
       For volume: (I:)\\?\Volume{ddf6a51c-1282-11e3-b291-000c293b01d1}\
       Shadow Copy Storage volume: (I:)\\?\Volume{ddf6a51c-1282-11e3-b291-000c293b01
    d1}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 35 GB (10%)
    Shadow Copy Storage association
       For volume: (E:)\\?\Volume{0e3bf713-125d-11e3-b2dd-000c293b01bd}\
       Shadow Copy Storage volume: (E:)\\?\Volume{0e3bf713-125d-11e3-b2dd-000c293b01
    bd}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 149.999 GB (30%)
    Shadow Copy Storage association
       For volume: (C:)\\?\Volume{a9fb0475-f1bd-11e0-b235-806e6f6e6963}\
       Shadow Copy Storage volume: (C:)\\?\Volume{a9fb0475-f1bd-11e0-b235-806e6f6e69
    63}\
       Used Shadow Copy Storage space: 0 B (0%)
       Allocated Shadow Copy Storage space: 0 B (0%)
       Maximum Shadow Copy Storage space: 4.99 GB (7%)
    Hope this might also help you experts to get a little more information.

Maybe you are looking for