Solution : https://service.sap.com/sap/support/notes/446172 (SAP Service marketplace login required)
Summary :
When executing a database job in DB13, users may encounter a termination with an error while running BRCONNECT, BRBACKUP, or BRARCHIVE commands. This error, indicated by SXPG_COMMAND_EXECUTE failure, could stem from a variety of issues in the communication between SAP systems and the database server related to incorrect or invalid setup. Common error messages include CPIC return codes and SAP return codes, which often point to network connectivity issues such as timeouts or failed reads. Several steps, from job scheduling in DB13 to external command execution, involve careful configuration checks including SAPDBHOST setup, RSH commands, and RFC connections. To address these errors, it is crucial to verify all parameters and configurations, ensure correct roles and authorizations, and possibly adjust environment settings and remote shell command setups. Updating or installing necessary remote shell tools and checking for consistent SAPXPG configurations across systems are also fundamental steps.
Key words :
sap return code 456these sap error codes, ni_read_failed 223 network read error c_timeout 456 timeout, alias hostname 'hostname -s' set prompt=, sap return code 223 communication error, rfc destination sapxpg_dbdest_<sapdbhost> exists, valid windows nt application, profile parameter gw/remsh, system exception error_messagein addition, schedule database administration jobs, sap profile parameter sapdbhost
Related Notes :
583759 | R/3 error when you start jobs from DB13 |
556232 | Environment settings for R/3/Oracle on Windows |
387137 | RFC connection test for sapxpg does not work |
202227 | Recommended login shells |
188772 | External program does not work |
114287 | SAPDBA in a Microsoft Cluster Server environment |
112266 | SAP and MS Cluster Server: Frequent questions and tips |
63347 | List: CPIC error codes |
34219 | DB13: CPIC error CM_RESOURCE_FAILURE_RETRY |
10403 | Starting external programs |