DP9: SAP Archive log backup failure

We have an HP-UX 11.31 system running SAP/Oracle 12c.  It is currently the ONLY system that the backups are failing.   Sample errors are as follows:

 [Major] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 3/30/2017 1:37:11 PM
 Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).)

[Major] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11  Received ABORT request from BSM (ERR: Error starting backup/restore (BMA cannot be started or similar).) 

[Critical] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11  Failed to start backup of object BSN.-1. Error: Details unknown. 

[Critical] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11
 Failed to start backup of object BSN.-1. Error: Details unknown.
Cannot create backup set "Catalog not loaded, message #7583 in set 11"

[Major] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11  Aborting connection to BSM. Abort code -17. 

[Major] From: OB2BAR_SAPBACK@s928-dbsapbs1.ssmhc.com "BSN"  Time: 03/30/17 13:37:11
 Aborting connection to BSM. Abort code -17.

Any suggestions?

Tags:

  • Hello Vincent. 

    I would try:

    1, On CM server, edit userlist file:
    C:\ProgramData\OmniBack\Config\Server\users\userlist
    Add more below parameter if it not exist  save file.

    "*" "*" "*" * "admin"

    2, On server s928-dbsapbs1.ssmhc.com, check the permissions on /var/opt/omni/tmp full permissions should be granted.

    Go to /var/opt/omni/
    Run this command to grant full permission for any:
    cd /var/opt/omni
    chmod 777 -R tmp


    3. reboot the media agent server could also be also something to try.

  • Verified Answer

    Thanks for the reply.

    What I eventually ended up doing was uninstalling on local node, removed DP directories and any reference to DP,  cleaning referecnes out any of file on the CM that had the node it (ie make sure problem node was not listed), rebooting the node, reinstalling from CM.

    Now all is happy. go figure.