Hello Experts,
How to configure db13 so that the backup can be scheduled for running? An error occurs while scheduling database from DB13.
Kindly share your views here.
Thanks in advance.
How to Configure DB13 so that the Backup can be Scheduled for Running?
Updated May 18, 2018
Comments
Recommended Posts:
- SAP BASIS Full Form & Meaning
- How to Check SAP Version
- SAP Shortcut Parameter
- Lock/Unlock SAP T-Codes via SM01
- Reset SAP* Password
- What is SAP Router
- SAP STMP Mail Configuration
- SAP Compatible Printers
- Check SAP Services in Linux and Unix
- SAP Schedule Background Job
- SAP Background Jobs List
- Stop Scheduled Background Job
- SAP Spool Overflow
- SAP Basis DB Refresh Steps
- Difference between DDIC and SAP
- Find Locked Users in SAP
- SAP Basis Tcodes
- SAP BASIS Scope and Opportunity
- SAP BASIS Certification Cost in India
- SAP Security Interview Questions
×
The reason for the error is that programs scheduled via DB13 can be executed on different background servers depending on the system status and the current load distribution. Under certain circumstances server-dependent analyses must be carried out on every possible source host. Since earlier WINDOWS did not have a remote shell client in the standard system we therefore had to install a relevant tool. We should also check R/3 profile parameters for consistency. We must also ensure that an OSF entry exists in the prompt section of .sapenv_<host>.csh script on TRU64.
If the backup job might has been scheduled using CRONTAB in Unix and if it doesn’t work then we can just check the previous backup logs where we can find a command line: “BROCONNECT –u-f” or similar to this. We can just copy the command and run it in OS platform using ORA user.
If the database used is Oracle then we need to logon to the server using sidadm and goto command prompt and then we can connect to oracle. After that we can enter the shutdown immediate command-> enter command startup mount.