Skip to Content
avatar image
Former Member

DB backup still running, but in DB13 already status "Finished with errors"


firstly, I am not regular DB administrator, so please be patient with me.

On 5.4.2010, 20:00 started on our server regullary planned online complete DB backup. Now (runing for more than 39 hours - DB size is only 300GB and last time, when it successfully finished, it takes less than 12 hours) I see in DB13 this backup with status "Finished with errors", but in SM37 this job is still with status "Active" so it seems to be running. On HDD where backup should be stored is created file with size 0 B. In job protocol and program protocol are only standard messages, nothing indicates that there is any error. OS is Windows Server 2008.

Program log:

  • DBA Action starts:

Timestamp: 20100405200040 Function: sda Object: DATA

  • SAVE/RESTORE request:


  • SAVE/RESTORE request accepted:


Job log:

05.04.2010 20:00:38 Job wurde gestartet

05.04.2010 20:00:38 Step 001 gestartet (Programm RSDBAJOB, Variante &0000000000001, Benutzername *****)

05.04.2010 20:00:38 Execute logical command DBMCLI On host *****

05.04.2010 20:00:38 Parameters:-d D01 -n ***** -uUTL -tpi D01 -tpp no_longer_used -tpc D01 backup_start COMPLETE_DB_BACKUP REC

05.04.2010 20:00:38 OVERY DATA AUTOIGNORE

Anybody have idea what is doing there?

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

1 Answer

  • avatar image
    Former Member
    Apr 07, 2010 at 09:42 AM

    Hi Peter,

    From the info you have provided it looks like it has aborted.

    In SM37 "tick" the active job and then go to the context menu above select "job" => Check status.

    This will check and will tidy up if need be. My guess it will go RED....


    Add comment
    10|10000 characters needed characters exceeded

    • in DB50, DBAHIST has following record for this backup:

      04-05 20:00:40 20100405200040 sda D01 DATA 9999 20100405200040

      so it is still active.


      ... unless you have a very old database version where there was a bug that caused wrong 9999 entries in DBAHIST under certain constellations. To check this we need to know the Release of your database.

      Also in table SDBADSDB is following record:

      1 20:00:00 20100216134109 D01 20100405200000 20100405200038 ALLNC sda 20100405200040 20100405200040 9999 Update task ADA_INSERT_SDBADSDB 01

      => EXT2 contains "Update task ADA_INSERT_SDBADSDB 01"

      Everything OK here. This message is just telling us that the job is running and that everything looks OK so far.

      So I think only opening CSN message is only applicable here...

      Yes, opening a CSN message would be the best option indeed as we need to logon into your system for further analysis.

      but how to do it and what exactly is CSN message (like I said, I am not regular administrator...)?

      You do it by reporting the problem to the SAP helpdesk. In case you have never done this before I would suggest that you ask your system admisitrator to give you a helping hand.

      CSN is the name of the SAP helpdesk R/3-system.