This action might not be possible to undo. Are you sure you want to continue?
Note Language: English Version: 26 Validity:
Valid Since 23.07.2010
Executing a database job in DB13 terminates with the following type of error in the job log: Execution of the logical command BRCONNECT on host <target host> Parameter: -u / -check SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error: see SYSLOG for additional information The following line may also be added to the error: Job cancelled after system exception ERROR_MESSAGE In addition to BRCONNECT, you must also consider BRBACKUP or BRARCHIVE as logical commands, for example. The syslog contains errors of the following type: Communication error, CPIC return code 027, SAP return code 223 Communication error, CPIC return code 020, SAP return code 456 These SAP error codes mean the following specifically (Note 63347): NI_READ_FAILED 223 Network read error C_TIMEOUT 456 Timeout when establishing connect.
R49, K, Microsoft Cluster Server, MSCS, cluster, CM_RESOURCE_FAILURE_RETRY
Reason and Prerequisites
In transaction DB13, you can schedule database administration jobs in which external tools such as BRCONNECT or BRBACKUP are called. You must perform several steps in this case. If problems occur during one of these steps, this results in one of the aforementioned error messages with SXPG_COMMAND_EXECUTE. If an error occurs, it is important to have a rough understanding of the processes. The following is an overview of the individual steps between DB13 scheduling and the actual start of the external tool:
An action is scheduled for a specific time in DB13. As a result, a background job is scheduled with the naming convention "DBA_*". When the start point is reached, the job is executed on an SAP background server. In addition, this server is designated as a source host. The system now checks within the job as to whether a SAP instance is running on the database server. To do so, the SAP profile parameter
Page 1 of 5
server-dependent analyses (such as the parameter value for SAPDBHOST or privileges for RSH connections) must therefore be carried out on every possible source host. If SAPDBHOST does not correspond to any host name of SAP instances.SAP Note 446172 SXPG_COMMAND_EXECUTE (program_start_error) in DB13 SAPDBHOST (called the target host from now on) and the HOST_NAME from V$INSTANCE are compared with the host names of the SAP instances. you must install a relevant tool in this case if Page 2 of 5 2. - If an error occurs during one of these steps. The external tool is started with SAPXPG. 6.09. SAPXPG is called from there. the system assumes that a standalone gateway is running on the database server and performs the following steps: An RFC connection is set up from the source host via SAPXPG_DBDEST_<SAPDBHOST> to the standalone gateway on SAPDBHOST. the system now checks whether an RFC destination SAPXPG_DBDEST_<SAPDBHOST> exists for which the gateway options are maintained according to Note 34219 (3). A remote call to the target host is started using the command defined in the profile parameter gw/remsh (usually RSH). If the name of the host of an SAP instance corresponds to the profile parameter SAPDBHOST or the HOST_NAME from V$INSTANCE. b) The external tool BRBACKUP or BRARCHIVE is started with SAPXPG. perform the following steps: a) The SAP tool SPXPG (which is used for calling external programs) is started on this instance. Under certain circumstances. Solution You can check the following points to locate the cause of the error: 1. - b) Otherwise. see Notes 10403 and 118057 also. The following steps are now executed: a) As of Release 4. For more information. Programs scheduled via DB13 can be executed on different background servers (source hosts) depending on the system status and the current load distribution. The external tool is started with SAPXPG.2010 . which controls its process. the system assumes that no SAP instance is running on the database server. If this is the case. In this case. the external command is started directly by this instance. 24.5B. this usually results in an SXPG_COMMAND_EXECUTE error. Since earlier WINDOWS releases do not contain a remote shell client in the standard system. the target host is accessed remotely via the gateway of the source host. 5. SAPXPG is started via this mechanism.
see Note 202227. Usually "rsh" is used. 4.this line must exist! case Reliant*: set prompt="`/usr/ucb/hostname`:`/usr/ucb/whoami` \!% " breaksw case ULT*: set LOGNAME=$USER default: set prompt="`hostname`:$LOGNAME \!> " breaksw endsw 7. Make sure that SAPXPG_DBDEST_<SAPDBHOST> is entered with program "sapxpg " for the RFC destination in transaction SM59.csh script on TRU64: # define prompt string switch (`uname`) case OS\/390: alias hostname 'hostname -s' set prompt="`hostname`:%/ (\!)%#" breaksw case Sun*: case SIN*: case OSF*: <. Also note that this is case-sensitive. although "remash" can also be used on HP-UX. the network settings and 8. You can use ATAMAN here (see Note To minimize problems with the used shell. test the remote shell call to the target host on the operating system of the source host(s) (if necessary. for example.2010 Page 3 of 5 . make sure that the USER environment variable for SAPSERVICE<sid> contains <sid>ADM. 5. b) Ensure that the parameter gw/netstat_once is set to 0 in cluster environments so that you can identify dynamic changes of logical host names. also see Note 112266. If using the remote shell. 24.sapenv_<host>. For MSCS. you should assign the CSH as the default shell to the gateway user. See also Note 556232. This variable controls the user under which the external command is started. 6. 3. Ensure that an OSF entry exists in the prompt section of . 114287).SAP Note 446172 SXPG_COMMAND_EXECUTE (program_start_error) in DB13 you want to use this function. replace RSH with the actual remote shell tool being used): rsh <target host> -l <sid>adm sapxpg If errors occur with this call (such as "Permission denied". For more information.09. c) The profile parameter gw/remsh must contain the correct remote shell tool. Also check the R/3 profile parameters for consistency: a) SAPDBHOST must be set to the correct physical or logical (in the case of a cluster environment) host names of the database host. "Can't establish connection" or a password query). On Windows.
If the standalone gateway is used. this usually means that everything is alright. there may be several physical or logical names for the same system in cluster environments). However. dev_rd). dev_rfcX. enter only the external command SAPXPG in SM69 and then check the successful execution in SM49. This should run without errors when executed in SM49. the tool may not exist on the target host. In transaction SM69. 12. Check and correct these points." indicates that an incorrect file with the name "sapxpg" is retained for the SAPXPG executable.2010 Page 4 of 5 Released for Customer 23. you can also perform a connection test to the destination SAPXPG_DBDEST_<target host> in transaction SM59 and analyze the errors.07. If the system displays a message such as "sapxpg: Command not found" or "sapxpg: Permission denied. The message "Win32 error 193: %1 is not a valid Windows NT application. this file would have to be renamed or deleted on the target host. a message such as 'Not enough space (fork)' informs you that a limit has been reached on the operating system and no new processes can be created. These can provide additional notes on the actual problem. and that an SAPXPG of the same R/3 version as in the source system is being used. create an external command with the operating system command RSH and the parameters <target host> and sapxpg in the case of a remote target host. If the call is not yet possible at operating system level. although no error actually exists. the authorizations may be missing or you may not be able to find the tool in the user search path.". The system often writes useful error data for the time of the SAPXPG call into the syslog (SM21) or trace files (dev_wX. Consider Note 10403 when correcting this problem.2010 09:04:33 German Recommendations/additional info Help for error analysis BC-DB-ORA-CCM CCMS/Database Monitors for Oracle . note that the connection test in transaction SM59 with SAPXPG according to Note 387137 may lead to an error (CM_PRODUCT_SPECIFIC_ERROR). you can determine which source host name is used after you perform a remote logon (rsh. Also check that there are no files with the same name in the search path of the user. If the call does not return any results at all. For example. 9. Header Data Release Status: Released on: Master Language: Priority: Category: Primary Component: Secondary Components: BC-CCM-BTC-EXT External and Logical Commands 24. In the case of a local SAPXPG execution. rlogin and so on) using the "finger" command on UNIX.rhosts file. then it will not be able to work from R/3 either. As a result. 11. 10. for example.SAP Note 446172 SXPG_COMMAND_EXECUTE (program_start_error) in DB13 security settings are probably not set correctly. This may then have to be enhanced in the . If you have doubts about the source host name used by a user to log on to the target host (in particular.09.
SAP Note 446172 SXPG_COMMAND_EXECUTE (program_start_error) in DB13 BC-CCM-BTC Background Processing BC-DB-ORA-DBA Database Administration with Oracle BC-CST-GW Gateway/CPIC The Note is release-independent Related Notes Number 583759 556232 387137 202227 188772 114287 112266 63347 34219 10403 Short Text R/3 error when you start jobs from DB13 Environment settings for R/3/Oracle on Windows RFC connection test for sapxpg does not work Recommended login shells External program does not work SAPDBA in a Microsoft Cluster Server environment SAP and MS Cluster Server: Frequent questions and tips List: CPIC error codes DB13: CPIC error CM_RESOURCE_FAILURE_RETRY Starting external programs 24.09.2010 Page 5 of 5 .