fail startsap

Hi, I have issue with startsap

cq1ds001:cq1adm 138> startsap

Checking CQ1 Database

Database is running

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

Starting Startup Agent sapstartsrv

Unknown webmethod: WaitforServiceStarted

Startup of Instance Service failed

See /home/cq1adm/startsap_SCS01.log for details

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

cq1ds001:cq1adm 139>

Please, help,

Best Regards,

EDRS

SAP Managed Tags:
NW AS Java Administrator (NWA)

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

Accepted Solutions (1)

firstly try starting sapstartsrv independently ( i.e not by running startsap ). if it comes up then try running startsap.

Provide the details from log file /home/cq1adm/startsap_SCS01.log

Thanks

Amit

You must be a registered user to add a comment. If you've already registered, sign in. Otherwise, register and sign in.

Comment

attach log

Trace of system startup/check of SAP System CQ1 on Tue Jun 5 16:47:01 EDT 2012

Called command: /usr/sap/CQ1/SYS/exe/run/startsap start

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

16:47:03

Starting Startup Agent sapstartsrv

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

16:47:03

Startup of Instance Service failed

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

16:47:03

See /home/cq1adm/startsap_SCS01.log for details

Please go to your kernel directory and execute sapcpe. Let me know if you get any output or errors.

After this please attempt to start your instance one again.

Also let me know if you recently performed a kernel upgrade.

Regards

Amit Padmawar

Hi Amit/Ramones - Thanks for the helpful advice. I have a similar issue, but I am not familiar with running sapcpe manually. I tried the following format: sapcpe -pf=SID_J99_server

This format did not work.

My situation: we just upgraded a J2EE-only portal from 7.01 to 7.02 (so a kernel update has occurred). The central instance server is ok, but my dialog instance (on a different physical server) will not start up (same error Ramones had).

I tried running sapcpe from both the dialog instance and the central instance (using the dialog instance profile both times). In both cases it appears the script could not derive the SID. I ran sapcpe as sidadm. Notice in the error below (from sapcpe.log) that the directory path does not have SID:

*************************************************

source: /usr/sap//SYS/exe/uc/linuxx86_64

target: /usr/sap//SYS/exe/run

*************************************************

*** ERROR: sapcpe: find <dst> /usr/sap//SYS/exe/run failed, 2, No such file or directory, [sapxxcpe.c:1588]

Any help is appreciated - Thanks Jeff

looks like environment for your sidadm account is missing some variables.

Please compare the environment variables for sidadm in CI and on the app server. Because the log which you pasted does not have a <SID>

Also i believe that you have nfs mounted your kernel directory from CI to your APP server.

Generally there is no need to explicitly execute sapcpe , startsap calls it automatically.

Please make sure that all processes running with sidadm are stopped ( even sapstartsrv ) then attempt to start your system.

in the mean time i will check on the syntax for sapcpe , but my understanding is there is none.

just executing sapcpe should do the magic. make sure you are sidadm.

Regards

Amit Padmawar

Hi Jeff,

Please publish SID_J99_server and Default profiles.v

Regards.

Ruchit.

Ruchit this what i got as a syntax for sapcpe. Any idea on which option will work out for Jeff ?

i would still let startsap handle it . what do you say ?

sapcpe [profile-parameters] [control-parameters]

profile-parameters:

all profile-related parameters: nr=..., name=..., pf=...

control-parameters:

shcp - use shell commands instead of internal

coding to copy files

default: use internal coding

test:n - switch test mode on. Target filename is

always sapcpeTS

default: test mode is off

n: 7 writing/linking target file sapcpeTS

n: 5 creating/linking target file sapcpeTS, no read

n: 3 creating/linking target file sapcpeTS, no write

n: 1 creating/linking target file sapcpeTS, no read/write

n: 0 test mode off

all - process all files

copy - primary operation: copy files (default)

link - primary operation: link files

process files as specified in file table (CT)

nocm - suppress transfer/uncompress of compressed

files

default: transfer and uncompress the compressed file,

if exists and is younger than the uncompressed

file in the source directory. Otherwise, copy

the uncompressed file.

nock - no check on mandatory files

default: check enabled

chown - set original owner to the copied files

(requires superuser privilege)

default: copied files will be created under current

user

size:<bytes> - size of the internal copy buffer (bytes)

default: 1MB

list:<filename> - list of files to be processed. If set, the

default list files are not used. This

parameter changes logfile name to

sapcpe_<filename>.log

default lists:

(lists in central directory)

instance.lst - RDBMS independent files

instancedb.lst- RDBMS dependent files

tools.lst - other files

inhouse.lst - all files which should NOT be

delivered to customers

dbclient.lst - database clisnt files

igsexe.lst - IGS files

sapcrypto.lst - special files for sapcryto

If these files don't exist, only the files from a file

table (default: sapcpeft) are processed

source:<dir-name> - source directory

target:<dir-name> - target directory,

ftable:<filename> - name of a file which contains a table of

files and their FileProcesssModes (FPMs)

default: sapcpeft

Search paths for sapcpeft are current

directory and then source directory

Format: filename [copy_attribute [check_attribute]]

Example: disp+work local_copy check_exist

saptemu softlink check_exist

R3trans softlink

...etc

(FPM: unspec/0, loc/1,ct/2, chk/10, cp_loc_if _exists/20

files - print table of the loaded configured files

stdoutput - print the output of the program also to stdout

trace/trace3 - print trace infromation

help - print this text

Regards

Amit

Hi Amit - you are correct, the kernel directory is NFS-mounted from CI to APP server.
I tried stopping all processes for sidadm on the APP server (cleaned memory segments also).
This still did not work. Also - executing sapcpe with no parameters did not work for me. It does however produce a list of options
As to the environment variables, they look the same for sidadm on CI and APP server.

Thanks - Jeff

Hi Ruchit - The profile contents are listed below. Thanks for your help - Jeff

DEFAULT.PFL:

SAPDBHOST = inbtlsap20

j2ee/dbtype = ora

j2ee/dbname = POQ

j2ee/dbhost = inbtlsap20

SAPSYSTEMNAME = POQ

SAPGLOBALHOST = inbtlsap20

DIR_PUT = /usr/sap/$(SAPSYSTEMNAME)/put

#-----------------------------------------------------------------------

# SAP Central Service Instance for J2EE

#-----------------------------------------------------------------------

j2ee/scs/host = inbtlsap20

j2ee/scs/system = 55

j2ee/ms/port = 3955

#-----------------------------------------------------------------------

# SAP Central Service Instance for J2EE

#-----------------------------------------------------------------------

Instance Profile (Central Instance):

SAPSYSTEMNAME = POQ
SAPSYSTEM = 54
INSTANCE_NAME = JC54
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
jstartup/trimming_properties = off
jstartup/protocol = on
jstartup/vm/home = /opt/IBMJava2-amd64-142
jstartup/max_caches = 500
jstartup/release = 700
jstartup/instance_properties = $(jstartup/j2ee_properties):$(jstartup/sdm_properties)
j2ee/dbdriver = /oracle/client/10x_64/instantclient/ojdbc14.jar
igs/listener/rfc/disable = 1
exe/saposcol = $(DIR_CT_RUN)/saposcol

#------------------------------------------------------------
# Jcontrol: Migrated Profile Parameter
# create at Wed Jul 7 21:18:06 2010
#------------------------------------------------------------
j2ee/instance_id = ID5413973
#------------------------------------------------------------

Instance Profile (SCS):

SAPSYSTEMNAME = POQ

SAPSYSTEM = 55

INSTANCE_NAME = SCS55

DIR_CT_RUN = $(DIR_EXE_ROOT)/run

DIR_EXECUTABLE = $(DIR_INSTANCE)/exe

OS_UNICODE = uc

#-----------------------------------------------------------------------

# SAP Message Server for Java

#-----------------------------------------------------------------------

rdisp/msserv = 0

rdisp/msserv_internal = 3955

ms/standalone = 1

ms/server_port_0 = PROT=HTTP,PORT=81$$

#-----------------------------------------------------------------------

# SAP Enqueue Server

#-----------------------------------------------------------------------

enque/serverinst = 55

enque/table_size = 4096

rdisp/enqname = $(rdisp/myname)

enque/snapshot_pck_ids = 100

Instance Profile (Dialog Instance):

SAPSYSTEMNAME = POQ
SAPSYSTEM = 56
INSTANCE_NAME = J56
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
jstartup/trimming_properties = off
jstartup/protocol = on
jstartup/vm/home = /opt/IBMJava2-amd64-142
jstartup/max_caches = 500
jstartup/release = 700
jstartup/instance_properties = $(jstartup/j2ee_properties)
j2ee/dbdriver = /oracle/client/10x_64/instantclient/ojdbc14.jar
igs/listener/rfc/disable = 1
exe/saposcol = $(DIR_CT_RUN)/saposcol

#------------------------------------------------------------
# Jcontrol: Migrated Profile Parameter
# create at Thu Jul 8 11:32:50 2010
#------------------------------------------------------------
j2ee/instance_id = ID5650542
#------------------------------------------------------------

Hi Amit,

sapcpe as you have mentioned above is called when starting SAP. However it is not in startsap code but rather in Start Profile and there you will find it with control parameter list:<filename>. Filename is the name of file present in Central Kernal directory with extension .lst. There can vbe mutiple such files pointing to different instance for example SCS.lst for SCS instacne. What I would suggest in open the START profile for the concerned instance, check for the section of code related to SAPCPE and they execute it with adapatation since the command in start profile would use some variables (Foe ex: $DIR_EXE etc. which would be already defined in start profile.

@Jeff,

One more thing. Please publish you start profile .Hide confidential values like actual hostname withb <hostname> .

Regards.

Ruchit

Jeff,

Why were you using J99 in profile name ?

And exactly which instance startup is failing.. I guess J56?

Regards.

Ruchit,

Hi Ruchit - you are correct, it is the J56 dialog instance that will not start up. CI instance JC54 is ok. The start profiles are listed below. Thanks again - Jeff

Start Profile - CI:

SAPSYSTEMNAME = POQ
SAPSYSTEM = 54
INSTANCE_NAME = JC54
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
DIR_PROFILE = $(DIR_INSTALL)/profile
_PF = $(DIR_PROFILE)/POQ_JC54_<<CI_hostname>>
SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
_CPARG0 = list:$(DIR_CT_RUN)/j2eeinst.lst
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
_CPARG1 = list:$(DIR_CT_RUN)/igsexe.lst
Execute_01 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG1)
#-----------------------------------------------------------------------
# Start Java application server
#-----------------------------------------------------------------------
_JC = jc.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_02 = local rm -f $(_JC)
Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/jcontrol$(FT_EXE) $(_JC)
Start_Program_00 = local $(_JC) pf=$(_PF)
#-----------------------------------------------------------------------
# Start internet graphics server
#-----------------------------------------------------------------------
_IG = ig.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_04 = local rm -f $(_IG)
Execute_05 = local ln -s -f $(DIR_EXECUTABLE)/igswd_mt $(_IG)
Start_Program_01 = local $(_IG) -mode=profile pf=$(_PF)

UpdateKernelOptions=pf=/usr/sap/POQ/SYS/profile/START_JC54_<<CI_hostname>>

Start Profile - Dialog Instance:

SAPSYSTEMNAME = POQ
SAPSYSTEM = 56
INSTANCE_NAME = J56
DIR_CT_RUN = $(DIR_EXE_ROOT)/run
DIR_EXECUTABLE = $(DIR_INSTANCE)/exe
DIR_PROFILE = /sapmnt/POQ/profile
_PF = $(DIR_PROFILE)/POQ_J56_<<DI_hostname>>
SETENV_00 = LD_LIBRARY_PATH=$(DIR_LIBRARY):%(LD_LIBRARY_PATH)
SETENV_01 = SHLIB_PATH=$(DIR_LIBRARY):%(SHLIB_PATH)
SETENV_02 = LIBPATH=$(DIR_LIBRARY):%(LIBPATH)
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
_CPARG0 = list:$(DIR_CT_RUN)/j2eeinst.lst
Execute_00 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG0)
#-----------------------------------------------------------------------
# Copy SAP Executables
#-----------------------------------------------------------------------
_CPARG1 = list:$(DIR_CT_RUN)/igsexe.lst
Execute_01 = immediate $(DIR_CT_RUN)/sapcpe$(FT_EXE) pf=$(_PF) $(_CPARG1)
#-----------------------------------------------------------------------
# Start Java application server
#-----------------------------------------------------------------------
_JC = jc.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_02 = local rm -f $(_JC)
Execute_03 = local ln -s -f $(DIR_EXECUTABLE)/jcontrol$(FT_EXE) $(_JC)
Start_Program_00 = local $(_JC) pf=$(_PF)
#-----------------------------------------------------------------------
# Start internet graphics server
#-----------------------------------------------------------------------
_IG = ig.sap$(SAPSYSTEMNAME)_$(INSTANCE_NAME)
Execute_04 = local rm -f $(_IG)
Execute_05 = local ln -s -f $(DIR_EXECUTABLE)/igswd_mt $(_IG)
Start_Program_01 = local $(_IG) -mode=profile pf=$(_PF)

UpdateKernelOptions=pf=/usr/sap/POQ/SYS/profile/START_J56_<<DI_hostname>>

Hi Jeff,

Please try executing this:

/sapmnt/POQ/SYS/exe/run/sapcpe /usr/sap/POQ/J56/exe pf=/sapmnt/POQ/SYS/profile/POQ_J56_<<DI_hostname>> list:/sapmnt/POQ/SYS/exe/run/j2eeinst.lst

Please supply <<DI_hostname>>value.

Let us know the output.

Regards.

Ruchit.

Thanks very much Ruchit! This worked perfectly and my dialog instance started up fine.

Thanks to you and also to Amit for your excellent advice.

fyi - I changed the comand as follows (probably because of the version/directory structure on my instance):

/sapmnt/POQ/exe/sapcpe /usr/sap/POQ/J56/exe pf=/sapmnt/POQ/profile/POQ_J56_<<DI_hostname>> list:/sapmnt/POQ/exe/j2eeinst.lst

Cheers! Jeff

Yes Ruchit i am aware that sapce will get parametrized and called from the start profile. That actually will be called when starting the instance. Just wanted to try that before running sapcpe with options.

Thanks , looks like it will work out for Jeff.

Regards

Amit

Thanks very much Ruchit! This worked perfectly and my dialog instance started up fine.

Thanks to you and also to Amit for your excellent advice.

fyi - I changed the comand as follows (probably because of the version/directory structure on my instance):

/sapmnt/POQ/exe/sapcpe /usr/sap/POQ/J56/exe pf=/sapmnt/POQ/profile/POQ_J56_<<DI_hostname>> list:/sapmnt/POQ/exe/j2eeinst.lst

Cheers! Jeff

Hello Ruchit/Amit,

I have similar issue. i get the below message after i upgraded the kernel to 720 standard on dual stack machine neither ABAP nor JAVA startup.

OS = AIX

Oracle = 11g

Database is running

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

Starting Startup Agent sapstartsrv

Unknown webmethod: WaitforServiceStarted

Startup of Instance Service failed

disp+work shows the latest patch level

R3trans -x works fine, however when i start the above message appears.

I have checked the profile parameters

DIR_CT_RUN = /usr/sap/DS0/SYS/exe/ctrun --> This directory does not exists

DIR_EXECUTABLE = /usr/sap/DS0/SYS/exe/run

i copied the newly extracted kernel to the /usr/sap/DS0/SYS/exe/run. could please advise what can be done.

Thank you very much.

Hi Kiran

Please try the following first. Stop all the processes including sapstartsrv , do a clean ipc and try to bring up the instance.

If it does not work then we can try executing sapcpe as recommended above.

Regards

Amit Padmawar

Hi Amit,

Thank you for your reply, i have tried that numerous times. it is not helping me Amit.

kindly advise.

Thanks and regards

Kiran Deverla

hello All,

I know this thread is closed but need small suggestion . I am facing the same error while starting SAP Web Dispatcher after upgrade to 720. Could you please guide which command should i try to restart web dispatcher

Thanks,

Supriya

Answers (0)

Ask a Question

Top Q&A Solution Author

User

Count

fail startsap

Accepted Solutions (1)

Accepted Solutions (1)

Answers (0)

Re: "Failed to update setup engine executables. Pr...

Re: Timer showing while sending the mails from SAP

Re: Best practice to connect to multiple databases...

SAP Hana Calculation view input parameter from JPA...

Re: Adaptation error in sap mdg ui screen customer