Why is a short dump written during an offline backup when the R/3 system is running?
The current R/3 system cannot know that BRBACKUP stops the database during an offline backup. Therefore, the first work process that loses the connection to the database writes a short dump. All work processes then go into reconnect mode until the database is available again. Consequently, it is normal that one (or more) short dumps are written during an offline backup, because the database cannot be accessed. For more information about the reconnect mechanism, see Note 98051.
Related Questions
- Will the finance system allow us to complete the electronic paperwork offline and then dump it into the system, or will all work be live like eJVE, eTime, SEAS and Temp/On Call Labor systems?
- What Happens If the Agents System Is Not Running When Its Time to Distill a Remote Backup Server?
- What are the system requirements for running Exchange-SQL Backup?
