on 12-08-2015 10:55 AM
Hello, dear experts.
Jobs, scheduling with DB13 not working.
Help me please understand how to configure job scheduling for the Oracle database in DB13 with SSH.
I have distributed installation SAP NW 7.40 SPS11:
sapdbscs - DB + ASCS
sapapp1 - PAS
sapapp2 - DI
Log of job in DB13:
Job started
Step 001 started (program RSDBAJOB, variant & 0000000000002, user ID ADMIN)
No application server found on database host - rsh / gateway will be used
Execution of the logical command BRCONNECT on host sapdbscs
SXPG_STEP_XPG_START: is_local_host: rc = 403
SXPG_STEP_XPG_START: host = sapdbscs
SXPG_STEP_XPG_START: is_local_r3_host: rc = 802
SXPG_STEP_XPG_START: RFC_TCPIP_CONNECTION_OPEN: rc = 1003
SXPG_STEP_COMMAND_START: SXPG_STEP_XPG_START returned: 1.003
SXPG_COMMAND_EXECUTE (LONG)
<timestamp> = 20151207170311
COMMANDNAME = BRCONNECT
ADDITIONAL_PARAMETERS = -jid CHECK20151207170230 -u / -c -f check
LONG_PARAMS
OPERATINGSYSTEM = ANYOS
TARGETSYSTEM = sapdbscs
DESTINATION
SY-SUBRC = 1003
SXPG_COMMAND_EXECUTE failed for BRCONNECT - Reason: program_start_error: see SYSLOG for additional information
Job cancelled after system exception ERROR_MESSAGE
I read the note:
446172 - SXPG_COMMAND_EXECUTE (program_start_error) in DB13
980266 - RFC destination SAPXPG_DBDEST_ <DB-HOST> does not work
1974030 - How to configure DB13 to work with a standalone Oracle database in Unix Linux
I configured SSH with authorization keys for user <sid>adm:
from sapapp1 to sapdbscs
from sapapp2 to sapdbscs
command ssh sapdbscs -l <sid>adm sapxpg is executed without error
I added in instances profiles the following parameters:
gw/acl_mode 0
gw/remsh /usr/bin/ssh
gw/netstat_once 0
gw/rem_start SSH_SHELL
Settings in RFC SAPXPG_DBDEST_SAPDBSCS:
Program: sapxpg
Target Host: sapdbscs
Start Type of External Program: Secure Shell
Gateway Options is clear
Test connection for RFC SAPXPG_DBDEST_SAPDBSCS error occurs:
LOCATION SAP-Gateway on host sapapp2 / sapgw02
ERROR timeout during allocate
TIME Tue Dec 8 11:44:59 2015
RELEASE 742
COMPONENT SAP-Gateway
VERSION 2
RC 242
MODULE /bas/742_REL/src/krn/si/gw/gwr3cpic.c
LINE 2181
DETAIL no connect of TP sapxpg from host sapdbscs after 20 sec
COUNTER 140
RFC 1710 CONVID 73,460,107
* CMRC = 27 DATA = 0 STATUS = 0 SAPRC = 242 ThSAPOCMINIT
RFC> ABAP Programm: RSRFCPIN (Transaction: SM59)
RFC> User: ADMIN (Client: 001)
RFC> Destination: SAPXPG_DBDEST_SAPDBSCS (handle: 2, DtConId: 5665D80EAE9320E5E10000000ACB81C5, DtConCnt: 0, ConvId:,)
TH VERBOSE LEVEL FULL
** RABAX: end RX_GET_MESSAGE
I don't understand why it used Gateway, because the note 1974030 said:
Make sure there are no gateway options set for that destination.
... If no settings for that, remote shell will be used
Help me please to configure planning in DB13 through SSH and without using Gateway.
Hi,
Could you check these notes..
1914589 - SXPG_COMMAND_EXECUTE failed when start job from DB13/DBACOCKPIT
2145145 - User is not authorized to start an external program [VIDEO]
Hope this helps.
Regards,
Prithviraj
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.
Hi Dmitriy,
If you configured the SAPXPG_DBDEST_SAPDBSCS for ssh, then ssh should be used and no standalone gateway is needed for sure (standalone gateway would be an alternative method).
Could you restart the gateway (sapapp2 / sapgw02) or the whole instance to make sure gateway knows of the of the correct parameter values and then retest the RFC ?
Regards, Péter Mihálffy
Hello Dmitry,
I have realized that the gateway configuration is wrong.
gw/ssh defines the call path of the secure shell and
gw/remsh defines the call path of the remote shell.
You told that ssh is working, then I think you should set
gw/ssh = /usr/bin/ssh for the gateway.
According to the documentation this parameter is not dynamically switchable, so I am afraid you
really have to do a restart after that.
Best Regards, Péter Mihálffy
User | Count |
---|---|
78 | |
9 | |
8 | |
6 | |
6 | |
6 | |
6 | |
6 | |
5 | |
4 |
You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.