The Database jobs are scheduled with a transaction DB13 that terminates with R/3 errors:
1. SXPG_COMMAND_EXECUTE failed for <tool>
no_permission
2. SXPG_COMMAND_EXECUTE failed for <tool>
program_start_error
3. SXPG_COMMAND_EXECUTE failed for <tool>
command_not_found
4. SXPG_COMMAND_EXECUTE failed for <tool>
parameters_too_long
5. SXPG_COMMAND_EXECUTE failed for <tool>
program_termination_error
6. SXPG_COMMAND_EXECUTE failed for <tool>
x_error
7. Variant &000000<var_nr> does not exist
Action unknown in SDBAP
Action deleted in SDBAP at <date>
Planning unknown in SDBAP
Action deleted in SDBAP at <date>
Planning unknown in SDBAP
Planning deleted in SDBAP at <date>
The older R/3 releases are giving error message that starts with the JOB SUBMIT than with SXPG_COMMAND_EXECUTE.
1. The user should have a sufficient authorizations for execution of jobs:
S_TCODE Authorization Checking of Transaction Start S_TCD_ALL
S_LOG_COM Authorization for Executing Logical Comm S_LOGCOM_ALL
S_BTCH_ADM Background Processing: Background Adm S_BTCH_ALL
S_BTCH_JOB Background Processing: Operations on S_BTCH_ALL
S_RZL_ADM CCMS: System Administration S_RZL_ALL
S_ADMI_FCD System Authorizations S_ADMI_ALL
2. Entries of sapdba, brbackup and brarchive are maintained by the default in SXPGCOTABE table. When the brconnect is being in use then corresponding Support Package status will implement in accordance otherwise “command_not_found” error may occur.
3. The list of the parameters that transferred should not be too long while changing scheduled operations accordingly.
4. These messages will be having different causes.
a. Import the current R/3 kernel patches including sapxpg, sapdba and BR tools.
b. Check R/3 Syslog and trace the files for additional error messages.
c. Check whether the error can be reproduced or only occurs sporadically.
d Check operating system log for error messages.
5. If error “variant does not exist" then create DB13 schedules again from beginning.