Skip to Content
avatar image
Former Member

EHP7 Upgrade-error in START_SHDI_PREPUT!

Hello friends,


I'm doing an upgrade to EHP7 in Linux/Oracle. I am currently facing an error in the START_SHDI_PREPUT! phase. Shadow instance fails to start. I have setup SSFS in both original and shadow system.


Severe error(s) occurred in phase MAIN_SHDPREPUT/START_SHDI_PREPUT!

Last error code set: Shadow instance couldn't be started, check 'STARTSSC.LOG' and 'DEVTRACE.LOG': Process /usr/SUM/SUM/abap/exe/sapcontrol exited with 2, see '/usr/SUM/SUM/abap/log/SAPup.ECO' for details

STARTSSC.LOG

----------------------------

1 ETQ201 Entering upgrade-phase "MAIN_SHDPREPUT/START_SHDI_PREPUT" ("20140114101135")

2 ETQ367 Connect variables are set for standard instance access

4 ETQ399 System-nr = '00', GwService = 'sapgw00' Client = '000'

4 ETQ399 Environment variables:

4 ETQ399 dbs_ora_schema=SAPSR3

4 ETQ399 auth_shadow_upgrade=<null>

1 ETQ200 Executing actual phase 'MAIN_SHDPREPUT/START_SHDI_PREPUT'.

1 ETQ399 Phase arguments:

2 ETQ399 Arg[0] = 'START_SERVICE'

2 ETQ399 Arg[1] = 'DEVTRACE.LOG'

4 ETQ380 computing toolpath for request "TP_ALWAYS_NEW"

4 ETQ381 request "TP_ALWAYS_NEW" means "always tp from DIR_PUT/exe, for phase KX_SWITCH"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ399 Requirement for tp maps to 'exe'

4 ETQ383 translates to path "/usr/SUM/SUM/abap/exe"

2 ETQ399 Distribute 15 parallel processes to 2 tp and 8 R3trans.

2 ETQ399 Starting shadow instance

4 ETQ399 Set database connect to shadow.

4 ETQ399 Set environment for shadow connect:

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'

4 ETQ380 computing toolpath for request "TP_SHADOW_CONNECT"

4 ETQ381 request "TP_SHADOW_CONNECT" means "tp needs to connect to shadow system"

4 ETQ382 translates to group "R3UP_TOOL_GROUP_NEW"

4 ETQ399 Requirement for tp maps to 'exe'

4 ETQ383 translates to path "/usr/SUM/SUM/abap/exe"

4 ETQ399 Set tool parameters for shadow connect:

4 ETQ399 default TPPARAM: SHADOW.TPP

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'

1 ETQ359 RFC Login to: System="AE7", AsHost="plx287" Nr="01", GwHost="plx287", GwService="sapgw01"

2EETQ231 RFC Login failed

2 ETQ353 Starting system

1 ETQ399 SAPCONTROL MANAGER: SAPupSAPControlManager entered.

1 ETQ399 SAPCONTROL MANAGER: SAPupSAPControlInstanceUnix entered.

1 ETQ399 SAPCONTROL MANAGER: SAPupSAPControlInstanceUnix exit.

1 ETQ399 SAPCONTROL MANAGER: SAPupSAPControlManager exit.

1 ETQ399 SYSTEM MANAGER: Initializing.

1 ETQ399 SYSTEM MANAGER: featureCheck

1 ETQ399 SAPCONTROL MANAGER: getFeatureList with dumpfile: /usr/SUM/SUM/abap/log/INSTANCELIST.TMP

3 ETQ399 20140114101135: PID 7571 execute '/usr/SUM/SUM/abap/exe/sapcontrol -prot NI_HTTP -host plx287 -nr 01' , output written to '/usr/SUM/SUM/abap/log/INSTANCELIST.TMP'.

3 ETQ399 20140114101136: PID 7571 exited with status 1 (time: 1.000/0.004/0.008 real/usr/sys)

1 ETQ399 SYSTEM MANAGER: featureCheck - line: SAPup> Starting subprocess with PID 7571 in phase 'START_SHDI_PREPUT' at 20140114101135

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: DIR_LIBRARY=/usr/SUM/SUM/abap/exe

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: JAVA_HOME=/opt/java

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: LD_LIBRARY_PATH=/usr/SUM/SUM/abap/exe:/usr/SUM/SUM/jvm/jre/lib/amd64/server:/usr/SUM/SUM/jvm/jre/lib/amd64:/usr/SUM/SUM/jvm/jre/../lib/amd64:/usr/sap/AE7/SYS/exe/run:/usr/sap/AE7/SYS/exe/uc/linuxx86_64:/oracle/client/11x_64/instantclient

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: NLS_LANG=AMERICAN_AMERICA.UTF8

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: ORACLE_BASE=/oracle

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: ORACLE_HOME=/oracle/AE7/112_64

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: ORACLE_SID=AE7

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: PATH=/usr/SUM/SUM/abap/exe:/oracle/AE7/112_64/bin:/home/ae7adm/bin:/usr/local/bin:/bin:/usr/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin:/opt/java/bin:/usr/scripts:/usr/sap/AE7/SYS/exe/uc/linuxx86_64:/usr/sap/AE7/SYS/exe/run:/home/ae7adm:.

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: SAPDATA_HOME=/oracle/AE7

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: SAPSYSTEMNAME=AE7

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: auth_shadow_upgrade=1

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: dbms_type=ORA

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: dbs_ora_schema=SAPSR3

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ENV: dbs_ora_tnsname=AE7

1 ETQ399 SYSTEM MANAGER: featureCheck - line:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: EXECUTING /usr/SUM/SUM/abap/exe/sapcontrol -prot NI_HTTP -host plx287 -nr 01

1 ETQ399 SYSTEM MANAGER: featureCheck - line: NAME

1 ETQ399 SYSTEM MANAGER: featureCheck - line: sapcontrol (Version: 740, patch 37, changelist 1445373)

1 ETQ399 SYSTEM MANAGER: feature: sapcontrol (Version: found

1 ETQ399 SYSTEM MANAGER: featureCheck - line:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: SYNOPSIS

1 ETQ399 SYSTEM MANAGER: featureCheck - line: sapcontrol [-prot <protocol>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [-trace <filename>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [-debug]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [-user <user> <password>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [-queryuser]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [-repeat <N> <D>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [-format <format>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [-host <hostname>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -nr <instance number>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -function <webmethod> [parameter list]

1 ETQ399 SYSTEM MANAGER: featureCheck - line:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: DESCRIPTION

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Control and monitor SAP instances via WebService interface of SAP Start Service.

1 ETQ399 SYSTEM MANAGER: featureCheck - line:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: OPTIONS

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -prot <protocol>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Specify the protocol for the communication with the SAP instance.

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Available protocols are:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: NI_HTTP HTTP using SAP NI sockets (default, prefer Unix domain sockets)

1 ETQ399 SYSTEM MANAGER: featureCheck - line: NI_HTTPS HTTPS using SAP NI sockets (prefer Unix domain sockets)

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GSOAP_HTTP HTTP using gsoap build in sockets

1 ETQ399 SYSTEM MANAGER: featureCheck - line: WINHTTP HTTP using Windows winhttp

1 ETQ399 SYSTEM MANAGER: featureCheck - line: WINHTTPS HTTPS using Windows winhttp

1 ETQ399 SYSTEM MANAGER: featureCheck - line: PIPE Windows named pipes (on Unix same as NI_HTTP)

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -trace <filename>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Trace SOAP request/response

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -debug

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Write local trace to stderr

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -user <user> <password>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: OS user and password for Webservice authentication

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -queryuser

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Query interactively for user and password

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -repeat <N> <D>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Repeat webmethod call <N> times (-1=forever) with <D> sec delay

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -format <format>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Specify the format for the output of the webmethod.

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Available formats are:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: list List output format (default)

1 ETQ399 SYSTEM MANAGER: featureCheck - line: script Script output format

1 ETQ399 SYSTEM MANAGER: featureCheck - line: -host <hostname>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Host to connect to (default: localhost)

1 ETQ399 SYSTEM MANAGER: featureCheck - line:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: WEBMETHODS

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Start [runlevel]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: InstanceStart <hostname> <instance number> [runlevel]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Bootstrap [<hostname> <instance number>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Stop [softtimeout sec]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: InstanceStop <hostname> <instance number> [softtimeout sec]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Shutdown

1 ETQ399 SYSTEM MANAGER: featureCheck - line: RestartInstance [<softtimeout sec> [runlevel]]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: StopService

1 ETQ399 SYSTEM MANAGER: featureCheck - line: StartService <SID>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: RestartService

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ParameterValue [<parameter>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetStartProfile

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetTraceFile

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetAlertTree

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetAlerts

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetEnvironment

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetVersionInfo

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetQueueStatistic

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetProcessList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetInstanceProperties

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ListDeveloperTraces

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ReadDeveloperTrace <filename> <filesize>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ListLogFiles

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ReadLogFile <filename> [<filter> [<language> [<maxentries> [<cookie>]]]]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: AnalyseLogFiles [<severity 0..2> [<maxentries>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [<starttime YYYY MM DD HH:MM:SS> <endtime YYYY MM DD HH:MM:SS>]]]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ConfigureLogFileList set|add|remove [<filename1> <filename2>... <filenameN>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetLogFileList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: CreateSnapshot [<description> [<datcol_param> [<analyse_severity -1..2>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [<analyse_maxentries> [<analyse_starttime YYYY MM DD HH:MM:SS>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: <analyse_endtime YYYY MM DD HH:MM:SS> [maxentries

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [<filename1> ... <filenameN>]]]]]]]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ReadSnapshot <filename> [<local filename>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ListSnapshots

1 ETQ399 SYSTEM MANAGER: featureCheck - line: DeleteSnapshots <filename1> [<filename2>... <filenameN>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetAccessPointList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetProcessParameter <processtype> [pid]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: SetProcessParameter <processtype> <pid> <parameter> <value1>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [<value2> ... <valueN>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: SetProcessParameter2 <processtype> <pid> [DYNAMIC|PERSIST|DYNAMIC_PERSIST] <parameter> <value1>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [<value2> ... <valueN>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: OSExecute <command> <async> <timeout> <protocolfile>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: SendSignal <pid> <signal>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetSystemInstanceList [<timeout sec>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: StartSystem [ALL|SCS|DIALOG|ABAP|J2EE|TREX|ENQREP|HDB|ALLNOHDB|LEVEL <level>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [<waittimeout sec> [runlevel]]]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: StopSystem [ALL|SCS|DIALOG|ABAP|J2EE|TREX|ENQREP|HDB|ALLNOHDB|LEVEL <level>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [<waittimeout sec> [<softtimeout sec>]]]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: RestartSystem [ALL|SCS|DIALOG|ABAP|J2EE|TREX|ENQREP|HDB|ALLNOHDB|LEVEL <level>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: [<waittimeout sec> [<softtimeout sec> [runlevel]]]]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: AccessCheck <function>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetSecNetworkId <service_ip> <service_port> [<version> [<challenge>]]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: GetNetworkId <service_ip> <service_port> [<version>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: RequestLogonFile <user>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: UpdateSystemPKI [<force>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: UpdateInstancePSE [<force>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: HACheckConfig

1 ETQ399 SYSTEM MANAGER: featureCheck - line: HACheckFailoverConfig

1 ETQ399 SYSTEM MANAGER: featureCheck - line: HAGetFailoverConfig

1 ETQ399 SYSTEM MANAGER: featureCheck - line: HAFailoverToNode <node>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ABAPReadSyslog

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ABAPReadRawSyslog

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ABAPGetWPTable

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEControlProcess <processname> <function>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEControlCluster <processname> <function> [<hostname> <instance number>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEEnableDbgSession <client> [<processname> <debugflags>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEDisableDbgSession <debugkey>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetProcessList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetProcessList2

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetThreadList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetThreadList2

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetThreadCallStack [<threadindex>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetThreadTaskStack [<threadindex>]

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetSessionList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetCacheStatistic

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetCacheStatistic2

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetApplicationAliasList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetComponentList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEControlComponents <process name> <operation> <componenttype>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: <componentname1>,...,<componentnameN>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetWebSessionList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetWebSessionList2

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetEJBSessionList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetRemoteObjectList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetVMGCHistory

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetVMGCHistory2

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetVMHeapInfo

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetClusterMsgList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: J2EEGetSharedTableInfo

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ICMGetThreadList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ICMGetConnectionList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ICMGetProxyConnectionList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: ICMGetCacheEntries

1 ETQ399 SYSTEM MANAGER: featureCheck - line: WebDispGetServerList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: EnqGetStatistic

1 ETQ399 SYSTEM MANAGER: featureCheck - line: EnqGetLockTable

1 ETQ399 SYSTEM MANAGER: featureCheck - line: StartWait <timeout sec> <delay sec>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: StopWait <timeout sec> <delay sec>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: WaitforStarted <timeout sec> <delay sec>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: WaitforStopped <timeout sec> <delay sec>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: RestartServiceWait <timeout sec> <delay sec>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: WaitforServiceStarted <timeout sec> <delay sec>

1 ETQ399 SYSTEM MANAGER: featureCheck - line: CheckHostAgent

1 ETQ399 SYSTEM MANAGER: featureCheck - line:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: EXITCODES

1 ETQ399 SYSTEM MANAGER: featureCheck - line: 0 Last webmethod call successful

1 ETQ399 SYSTEM MANAGER: featureCheck - line: 1 Last webmethod call failed, invalid parameter

1 ETQ399 SYSTEM MANAGER: featureCheck - line: 2 StartWait, StopWait, WaitforStarted, WaitforStopped, RestartServiceWait

1 ETQ399 SYSTEM MANAGER: featureCheck - line: timed out

1 ETQ399 SYSTEM MANAGER: featureCheck - line: 3 GetProcessList succeeded, all processes running correctly

1 ETQ399 SYSTEM MANAGER: featureCheck - line: 4 GetProcessList succeeded, all processes stopped

1 ETQ399 SYSTEM MANAGER: featureCheck - line:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: SECURITY

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Trusted connects without user and password check are possible through

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Unix domain socket or Windows named pipes. Protected webmethods like

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Start or Stop require a trusted connection or OS user and password

1 ETQ399 SYSTEM MANAGER: featureCheck - line: authentication.

1 ETQ399 SYSTEM MANAGER: featureCheck - line:

1 ETQ399 SYSTEM MANAGER: featureCheck - line: EXAMPLES

1 ETQ399 SYSTEM MANAGER: featureCheck - line: sapcontrol -nr 0 -function GetProcessList

1 ETQ399 SYSTEM MANAGER: featureCheck - line: Gets the list of processes on instance 00 on localhost

1 ETQ399 SYSTEM MANAGER: featureCheck - line: SAPup> Process with PID 7571 terminated with status 1 at 20140114101136!

1 ETQ399 SYSTEM MANAGER: sapcontrol feature sapcontrol (Version: is available.

1 ETQ399 Found INSTANCELIST.DMP. Instance list read from the file.

2 ETQ399 Checking consistency of profiles '/usr/SUM/SUM/abap/AE7/SYS/profile/AE7_DVEBMGS01_plx287' and '/usr/SUM/SUM/abap/AE7/SYS/profile/START_DVEBMGS01_plx287'.

1 ETQ399 SYSTEM MANAGER: Instantiated with SC.

1 ETQ399 SYSTEM MANAGER: STOPSAP on UNIX.

1 ETQ399 SYSTEM MANAGER: STOPSAP with SAPCONTROL.

1 ETQ399 SYSTEM MANAGER: SAPControl tries to control all instances.

1 ETQ399 SYSTEM MANAGER: Calling getInstances.

1 ETQ399 SYSTEM MANAGER: found instance for action STOP : Instance Number: 01

1 ETQ399 SYSTEM MANAGER: ControlInstance with SAPCONTOL action STOP for instance 01.

1 ETQ399 SYSTEM HEALTH MANAGER: running preCheck for instance 01 on host plx287

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'

1 ETQ359 RFC Login to: System="AE7", AsHost="plx287" Nr="01", GwHost="plx287", GwService="sapgw01"

2EETQ231 RFC Login failed

2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 1 for used ports on host 'plx287'.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 3201 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 3301 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 3601 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 3901 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 8101 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 30101 appears to be unused.

1 ETQ399 SYSTEM HEALTH MANAGER: System is down, no stop needed

1 ETQ399 SYSTEM MANAGER: Poststop on Unix.

1 ETQ399 SYSTEM MANAGER: STARTSAP on UNIX.

1 ETQ399 SYSTEM MANAGER: STARTSAP with SAPCONTROL.

1 ETQ399 SYSTEM MANAGER: PRESTARTACTION on UNIX.

1 ETQ399 SYSTEM MANAGER: Starting the service.

1 ETQ399 SYSTEM MANAGER: StartService on Unix.

1 ETQ399 SYSTEM MANAGER: Starting service.

1 ETQ399 SAPCONTROL MANAGER: startService

1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction on UNIX

1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction using start path: /usr/SUM/SUM/abap/exe and start profile : /usr/SUM/SUM/abap/AE7/SYS/profile/START_DVEBMGS01_plx287

1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction using ouput file: /usr/SUM/SUM/abap/log/SAPup.ECO

3 ETQ399 20140114101136: PID 7572 execute '/usr/SUM/SUM/abap/exe/sapstartsrv pf=/usr/SUM/SUM/abap/AE7/SYS/profile/START_DVEBMGS01_plx287 -D' , output written to '/usr/SUM/SUM/abap/log/SAPup.ECO'.

3 ETQ399 20140114101136: PID 7572 exited with status 0 (time: 0.000/0.004/0.008 real/usr/sys)

1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction using kernel exe release: 740 and kernel state: 0

1 ETQ399 SAPCONTROL MANAGER: preStartServiceAction using timeout: 300 and delay: 10

3 ETQ399 20140114101136: PID 7574 execute '/usr/SUM/SUM/abap/exe/sapcontrol -prot NI_HTTP -host plx287 -nr 01 -function WaitforServiceStarted 300 10' , output written to '/usr/SUM/SUM/abap/log/SAPup.ECO'.

3 ETQ399 20140114101146: PID 7574 exited with status 0 (time: 10.000/0.004/0.004 real/usr/sys)

1 ETQ399 SYSTEM MANAGER: SAPControl tries to control all instances.

1 ETQ399 SYSTEM MANAGER: Calling getInstances.

1 ETQ399 SYSTEM MANAGER: found instance for action START : Instance Number: 01

1 ETQ399 SYSTEM MANAGER: ControlInstance with SAPCONTOL action START for instance 01.

1 ETQ399 SYSTEM HEALTH MANAGER: running preCheck for instance 01 on host plx287

4 ETQ399 Set RFC variables for shadow connect:

4 ETQ399 System-nr = '01', GwService = 'sapgw01' Client = '000'

1 ETQ359 RFC Login to: System="AE7", AsHost="plx287" Nr="01", GwHost="plx287", GwService="sapgw01"

2EETQ231 RFC Login failed

2 ETQ399 SYSTEM HEALTH MANAGER: Checking instance number 1 for used ports on host 'plx287'.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 3201 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 3301 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 3601 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 3901 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 8101 appears to be unused.

3 ETQ399 SYSTEM HEALTH MANAGER: Port 30101 appears to be unused.

1 ETQ399 SYSTEM HEALTH MANAGER: System is down, go on with start action

1 ETQ399 SAPCONTROL MANAGER: startWait with host: plx287 and instance: 01

3 ETQ399 20140114101206: PID 8045 execute '/usr/SUM/SUM/abap/exe/sapcontrol -prot NI_HTTP -host plx287 -nr 01 -function StartWait 300 10' , output written to '/usr/SUM/SUM/abap/log/SAPup.ECO'.

3 ETQ399 20140114101237: PID 8045 exited with status 2 (time: 31.000/0.000/0.008 real/usr/sys)

1 ETQ399 SYSTEM MANAGER: SAPControl action START failed for instance 01.

1 ETQ399 SYSTEM MANAGER: CheckSystemStatus.

1 ETQ399 SAPCONTROL MANAGER: getProcessList with host: plx287 and instance: 01

3 ETQ399 20140114101237: PID 8999 execute '/usr/SUM/SUM/abap/exe/sapcontrol -format script -prot NI_HTTP -host plx287 -nr 01 -function GetProcessList' , output written to '/usr/SUM/SUM/abap/log/SAPup.ECO'.

3 ETQ399 20140114101237: PID 8999 exited with status 0 (time: 0.000/0.004/0.004 real/usr/sys)

1EETQ399 SYSTEM MANAGER: START of mandatory instance 01 on server plx287 has failed

2EETQ399 Starting shadow instance failed

4 ETQ399 Starting dialog 'StartSHDFailed' at 20140114101237.

4 ETQ399 Dialog finished at 20140114102932.

1EETQ399 Last error code set is: Shadow instance couldn't be started, check 'STARTSSC.LOG' and 'DEVTRACE.LOG': Process /usr/SUM/SUM/abap/exe/sapcontrol exited with 2, see '/usr/SUM/SUM/abap/log/SAPup.ECO' for details

1EETQ204 Upgrade phase "START_SHDI_PREPUT" aborted with severe errors ("20140114102932")

____________________________________________________________________________________________________________________________

DEVTRACE.LOG

-----------------------------

M Tue Jan 14 10:12:09 2014

M ThInit: running on host plx287

I MtxInit: 0 0 0

M calling db_connect ...

B Loading DB library '/usr/SUM/SUM/abap/exe/dboraslib.so' ...

B Library '/usr/SUM/SUM/abap/exe/dboraslib.so' loaded

B Version of '/usr/SUM/SUM/abap/exe/dboraslib.so' is "740.10", patchlevel (0.49)

C Register application info.

C Oracle client version: 11.2.0.2.0, V1, default build, (dbsl 740 271213, UNICODE[2])

C Installed Oracle client patches:

C # Patch 9930315 : Created on 15 Oct 2010, 03:55:06 hrs PST8PDT

C # Patch 10302309 : Created on 23 Nov 2010, 12:10:03 hrs CET

C *** ERROR => Connect via SAPUSER not supported for kernel >= 740.

[dbsloci.c 2386]

C Only Secure Connect method possible.

M ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 75]

M in_ThErrHandle: 1

M *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c 2243]

M

M Info for wp 0

M

M pid = 8489

M severity = 0

M status = 0

M stat = WP_NEW

M waiting_for = NO_WAITING

M workerType = DP_WORKER_DIAWP

M currentSession = T-1/U65535/M255

M lastSession = T-1/U65535/M255

M act_cs_count = 0

M csTrack = 0

M csTrackRwExcl = 0

M csTrackRwShrd = 0

M mode_cleaned_counter = 0

M control_flag = 0

M report = > <

M action = 0

M tab_name = > <

M

M ThIErrHandle: no current incoming request

M

M PfRejectStatistic: clear statistic record

M PfClearAllRec: clear statistic area

M PfClearAllRec: statRecordAction = STAT_RECORD_ACTION_REJECT

M Entering TH_CALLHOOKS

M ThIErrHandle: entering ThSetStatError

M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

M call ThrShutDown (1)...

M ***LOG Q02=> wp_halt, WPStop (Workp. 0 8489) [dpuxtool.c 318]

______________________________________________________________

I have updated the SSFS profile and env variables as per note 1622837. When I try to start the shadow system manually using SAPup, the sapcontrol process is failing to start. Could you please advice what could be wrong here ?

Thanks,

Sudarsan.

Add comment
10|10000 characters needed characters exceeded

  • Follow
  • Get RSS Feed

6 Answers

  • Best Answer
    avatar image
    Former Member
    Jan 14, 2014 at 12:43 PM

    Hello all,

    Thank you for your replies.

    @Reagan, Nirmal: I have set SSFS on the main system. I'll check SSFS settings again. Please find the dev_w0 of shadow instance below

    ---------------------------------------------------

    trc file: "dev_w0", trc level: 1, release: "740"

    ---------------------------------------------------

    *

    * ACTIVE TRACE LEVEL 1

    * ACTIVE TRACE COMPONENTS all, MJ

    *

    M sysno 01

    M sid AE7

    M systemid 390 (AMD/Intel x86_64 with Linux)

    M relno 7400

    M patchlevel 0

    M patchno 50

    M intno 20020600

    M make multithreaded, Unicode, 64 bit, optimized

    M profile /usr/SUM/SUM/abap/AE7/SYS/profile/AE7_DVEBMGS01_plx287

    M pid 8489

    M

    M

    M Tue Jan 14 10:12:08 2014

    M kernel runs with dp version 188000(ext=116000) (@(#) DPLIB-INT-VERSION-188000-UC)

    M length of sys_adm_ext is 500 bytes

    M *** WARNING => NiIHdlSetParamNoSslSessionDone: call on non SSL connection [nixxi.cpp 11068]

    M ThStart: taskhandler started

    M ThInit: initializing DIA work process W0

    M ***LOG Q01=> ThInit, WPStart (Workp. 0 1 8489) [thxxhead.c 960]

    M

    M Tue Jan 14 10:12:09 2014

    M ThInit: running on host plx287

    I MtxInit: 0 0 0

    M calling db_connect ...

    B Loading DB library '/usr/SUM/SUM/abap/exe/dboraslib.so' ...

    B Library '/usr/SUM/SUM/abap/exe/dboraslib.so' loaded

    B Version of '/usr/SUM/SUM/abap/exe/dboraslib.so' is "740.10", patchlevel (0.49)

    C Register application info.

    C Oracle client version: 11.2.0.2.0, V1, default build, (dbsl 740 271213, UNICODE[2])

    C Installed Oracle client patches:

    C # Patch 9930315 : Created on 15 Oct 2010, 03:55:06 hrs PST8PDT

    C # Patch 10302309 : Created on 23 Nov 2010, 12:10:03 hrs CET

    C *** ERROR => Connect via SAPUSER not supported for kernel >= 740.

    [dbsloci.c 2386]

    C Only Secure Connect method possible.

    M ***LOG R19=> ThDbConnect, db_connect ( DB-Connect 000256) [thDatabase.c 75]

    M in_ThErrHandle: 1

    M *** ERROR => ThInit: db_connect (step TH_INIT, thRc ERROR-DB-CONNECT_ERROR, action STOP_WP, level 1) [thxxhead.c 2243]

    M

    M Info for wp 0

    M

    M pid = 8489

    M severity = 0

    M status = 0

    M stat = WP_NEW

    M waiting_for = NO_WAITING

    M workerType = DP_WORKER_DIAWP

    M currentSession = T-1/U65535/M255

    M lastSession = T-1/U65535/M255

    M act_cs_count = 0

    M csTrack = 0

    M csTrackRwExcl = 0

    M csTrackRwShrd = 0

    M mode_cleaned_counter = 0

    M control_flag = 0

    M report = > <

    M action = 0

    M tab_name = > <

    M

    M ThIErrHandle: no current incoming request

    M

    M PfRejectStatistic: clear statistic record

    M PfClearAllRec: clear statistic area

    M PfClearAllRec: statRecordAction = STAT_RECORD_ACTION_REJECT

    M Entering TH_CALLHOOKS

    M ThIErrHandle: entering ThSetStatError

    M ThIErrHandle: do not call ThrCoreInfo (no_core_info=0, in_dynp_env=0)

    M call ThrShutDown (1)...

    M ***LOG Q02=> wp_halt, WPStop (Workp. 0 8489) [dpuxtool.c 318]

    _____________________________________________________________________________

    @Rishi: I have referred to the above notes and as mentioned earlier nor R3trans od original system is also not connecting. I'll check again.

    I am setting the rsdb_ssfs_connect env variable using the setenv command. Do I need to set it in the user profile of <sid>adm ?

    Thanks,

    Sudarsan.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hello Sudarshan,

      Its quite evident from the logs that the SSFS is not properly configured.

      Please follow the description in the notes:
      1622837 - New connect method of AS ABAP to Oracle via SSFS
      1611877 Support for ABAP SSFS during database connect

      Regards,

      Nirmal

  • avatar image
    Former Member
    Jan 14, 2014 at 10:02 AM

    Hello,

    have you changed the rsdb_ssfs_connect environment variable to 1 as well (or the rsdb/ssfs_connect profile parameter in the shadow instance profile)?

    Regards

    Tamás

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Jan 14, 2014 at 04:17 PM

    Hello all,

    Thank you again for your replies. I re-checked all the SSFS parameters, dropped the standard connection table from database and restarted the original system. Now the R3trans of original system is working fine.

    Tue Jan 14 17:09:12 CET 2014

    plx287:ae7adm 51> R3trans -d

    This is R3trans version 6.24 (release 721 - 26.09.13 - 20:13:07 ).

    unicode enabled version

    R3trans finished (0000).

    plx287:ae7adm 52>

    I can see the below lines in the developer trace of the original system .

    B Tue Jan 14 16:51:24 2014

    B Loading DB library '/usr/sap/AE7/DVEBMGS00/exe/dboraslib.so' ...

    B Library '/usr/sap/AE7/DVEBMGS00/exe/dboraslib.so' loaded

    B Version of '/usr/sap/AE7/DVEBMGS00/exe/dboraslib.so' is "721.02", patchlevel (0.138)

    B con_info_ext_support(): DBSL supports extended connect protocol

    B ==> connect info for default DB will be read from ssfs

    C Register application info.

    C Oracle client version: 11.2.0.2.0, V1, default build, (dbsl 721 041013, UNICODE[2])

    C Installed Oracle client patches:

    C # Patch 9930315 : Created on 15 Oct 2010, 03:55:06 hrs PST8PDT

    is this fine ?

    But still start of shadow instance fails. If i try to do a R3trans -d of the shadow kernel, it is not succeeding.

    plx287:ae7adm 55> ./R3trans -d

    This is ./R3trans version 6.24 (release 740 - 26.09.13 - 20:13:07 ).

    unicode enabled version

    2EETW169 no connect possible: "maybe someone set invalid values for DIR_LIBRARY ('/usr/sap/AE7/SYS/exe/run') or dbms_type ('ORA')"

    ./R3trans finished (0012).

    plx287:ae7adm 56> pwd

    /usr/SUM/SUM/abap/exe

    plx287:ae7adm 57>

    Also, I am not able to run the disp+work of the shadow kernel.

    plx287:ae7adm 59> ./disp+work

    ./disp+work: error while loading shared libraries: dw_parse3.so: cannot open shared object file: No such file or directory

    What value should I set in the DIR_LIBRARY ?

    The source kernel is 720_EXT PL 201 and shadow kernel is 740

    thanks,

    Sudarsan.

    Add comment
    10|10000 characters needed characters exceeded

    • Former Member

      Hey Sudarsan,

      You've probably figured it out by now, but we just ran into the same issue while doing both the EHP7 for ECC and the EHP3 for CRM.

      In the end, it was all a problem with the kernel mismatch. When we went into the shadow "work" dir, we looked at all the files in there. And one of them pointed to a mismatch library issue. Where it was expecting KERNEL #27 but it saw KERNEL #37 and didn't like it.

      So anyway, we blew away all the files in the SUM "exe" dir and un-extracted the SAR files for the JUMBO exe/exeDB and BRtools files.

      Then we stopped the shadow (not that it had ever really started), Kill -9 all the PIDs associated with the shadow instance, stopped the main SAP instance, did a cleanIPC on any shared mem.

      Then restarted SAP.

      Then, we re-ran the phase, and got past it.

      Hope that helps somebody out there.

      NICK

  • avatar image
    Former Member
    Jan 14, 2014 at 10:06 AM


    Hi,

    Can you please paste the contents of sapstartsrv.log from the work directory of shadow instance?

    Regards,

    Nirmal.

    Add comment
    10|10000 characters needed characters exceeded

  • Jan 14, 2014 at 10:40 AM

    Hello

    Did you set the SSFS on the main system?

    Could you provide the dev_w0 trace file for the shadow system?

    Regards

    RB

    Add comment
    10|10000 characters needed characters exceeded

  • avatar image
    Former Member
    Feb 07, 2014 at 04:25 PM

    Hi Nick,

    Thank you for your reply to the post.

    In my system, SSFS was also not properly setup (My Db was oracle) . So I setup the SSFS in shadow as well, (as per note 1622837) and then did the steps which you performed. ie, "Then we stopped the shadow (not that it had ever really started), Kill -9 all the PIDs associated with the shadow instance, stopped the main SAP instance, did a cleanIPC on any shared mem".

    Thanks and regards,

    Sudarsan.

    Add comment
    10|10000 characters needed characters exceeded

    • Ran into this problem a week ago during an SCM upgrade.

      The parameter ES/SHM_MAX_SHARED_SEGS was not set in the profile.

      To fix the issue the parameter ES/SHM_MAX_SHARED_SEGS=1 was set in the profile and restarted SAP.

      Regards

      RB