Power failed during NW upgrade，error occurs during restart

[Former Member]

Hi,

I am upgrading NW from 7.02 to 7.3 these days.

Phase MAIN_SHDRUN/ACT_UPG had run almost 16 days but was terminated due to power off accidently.

I restart the STARTUP under upgrade folder but error occurs like this:

I searched this problem on the forum and somebody say that it's due to shadow instance not started.

So I tried to start the shadow instance under folder /usr/sap/<SID>/upg/abap/bin use the following command:

SAPup startshd

But there's a fatal error:

FATAL ERROR: Process 'sapcontrol' exited with 1, see '/usr/sap/S01/upg/abap/log/SAPup.ECO' for details

And the last few lines in log SAPup.ECO are:

EXECUTING /usr/sap/S01/upg/abap/exe/sapcontrol (/usr/sap/S01/upg/abap/exe/sapcontrol) -prot NI_HTTP -host linux-q0fx -nr 01 -function StartWait 10000 10

12.12.2013 22:21:15

Start

FAIL: NIECONN_REFUSED (Connection refused), NiRawConnect failed in plugin_fopen()

Process with ID 6669 terminated with status 1

I also searched this problem on the forum and try to run installsapinit.sh as note 823941 - SAP start service on Unix platforms saies but also got error like this：

Now I don't how to fix this problem.

Could anyone pls. help me?

Thank you!

Thank you very much!

Best Regards,

Carina

[Former Member · Accepted solution]

Hi Rishl and Balazs,

When I run command sapstartsrv without -D I got message like this:

linux-q0fx:/tmp # su s01adm

linux-q0fx:s01adm 51> /usr/sap/S01/DVEBMGS00/exe/sapstartsrv pf=/usr/sap/S01/SYS/profile/S01_DVEBMGS00_linux-q0fx -u s01adm

Unable to open trace file sapstartsrv.log. (Error 11 Resource temporarily unavailable) [ntservsserver.cpp 3483]

Best Regards,

Carina Hu

[Former Member · Accepted solution]

Hi,

Please check the below note.

1762827 - Startup of Instance Service failed in UNIX or Linux environment

Thanks

Rishi abrol

[Reagan · Accepted solution]

Hello

Unless and until the logs are provided it is difficult to help you.

You may start with these SAP notes.

525677 - Problems when starting shadow instance

1937296 - SUM fails at start-shadow-instance-dm step

Regards

RB

[Former Member · Accepted solution]

Hi,

I've done excatly what the note saies but still facing the same error.

Plus, I find out that there's no work folder under parth /usr/sap/S01/upg/abap/S01/DVEBMGS00/.

Does this make a sense?

Thank you!

Carina Hu

[Former Member · Accepted solution]

Hi,

I've checked these notes before. And here are some logs updated yesterday.

TP.ECO

BLOCKED SIGNALS: ''
SAPup> Starting subprocess 22188 at 20131218202553
ENV: CLASSPATH=.:/usr/local/java/jdk1.6.0_51/lib/dt.jar:/usr/local/java/jdk1.6.0_51/lib/tools.jar:/db2/db2d01/sqllib/java/db2java.zip:/db2/db2d01/sqllib/java/runtime.zip:.
ENV: DB2DBDFT=D01
ENV: DB2INSTANCE=db2d01
ENV: DIR_LIBRARY=/usr/sap/S01/upg/abap/exe
ENV: JAVA_HOME=/usr/local/java/jdk1.6.0_51
ENV: LD_LIBRARY_PATH=/usr/sap/S01/upg/abap/exe:/usr/sap/S01/upg/jvm/jre/lib/amd64/server:/usr/sap/S01/upg/jvm/jre/lib/amd64:/usr/sap/S01/upg/jvm/jre/../lib/amd64:/usr/sap/S01/SYS/exe/run:/usr/sap/S01/SYS/exe/uc/linuxx86_64
ENV: PATH=/usr/sap/S01/upg/abap/exe:/usr/local/java/jdk1.6.0_51/bin:/usr/local/java/jdk1.6.0_51/bin:/root/bin:/usr/local/bin:/usr/bin:/bin:/usr/bin/X11:/usr/X11R6/bin:/usr/games:/usr/lib/mit/bin:/usr/lib/mit/sbin:/usr/sap/S01/SYS/exe/uc/linuxx86_64:/usr/sap/S01/SYS/exe/run:/home/s01adm:.:/db2/db2d01/sqllib/bin:/db2/db2d01/sqllib/adm:/db2/db2d01/sqllib/misc
ENV: SAPSYSTEMNAME=S01
ENV: auth_shadow_upgrade=1
ENV: dbms_type=db6
ENV: dbs_db6_schema=SAPS01

EXECUTING /usr/sap/S01/upg/abap/exe/tp (/usr/sap/S01/upg/abap/exe/tp) pf=/usr/sap/S01/upg/abap/bin/SHADOW.TPP unlock_eu S01
This is /usr/sap/S01/upg/abap/exe/tp version 376.02.14 (release 720, unicode enabled)
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
Warning: Parameter INTERRUPT is no longer used.
Warning: Parameter DAYLIGHT_SHUTDOWN is no longer used.
Warning: Parameter WITH_TACOB is no longer used.
Warning: Parameter IMPDP_BY_EVENT is no longer used.
tp finished with return code: 0
meaning:
  Everything OK

SLOG730.log

### Phase ACT_UPG:

START put                  S01        20131218022353              s01adm       linux-q0fx 20131218022352002d62

START SET STOPMARK         S01        20131218022353              s01adm       linux-q0fx 20131218022352002d62

STOP  SET STOPMARK         S01        20131218022353              s01adm       linux-q0fx 20131218022352002d62

LIST  put                  S01 (A{|

START tplock_eu            S01 (      20131218022353              s01adm       linux-q0fx 20131218022352002d62

STOP  tplock_eu            S01 (      20131218022354              s01adm       linux-q0fx 20131218022352002d62

START tp_getprots          S01 J      20131218022354              s01adm       linux-q0fx 20131218022352002d62

STOP  put                  S01   7002 20131218024736              s01adm       linux-q0fx 20131218022352002d62

START tpunlock_eu          S01        20131218202554              s01adm       linux-q0fx 201312182025530056ac

STOP  tpunlock_eu          S01        20131218202554              s01adm       linux-q0fx 201312182025530056ac

SAPup.out

Waiting for SAP SL-Controller to connect at port number 4240 (CTRL-C to interrupt)...

SL-controller connected

PHASE.SAV

#---- TIME: 20131218022352  PHASE: ACT_UPG
#--------------------------------------------------------------

1 ETQ201 Entering upgrade-phase "ACT_UPG" ("20131215034202")
4 ETQ399 Set environment for shadow connect:
4 ETQ399 Set RFC variables for shadow connect:
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
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 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399 Set tool parameters for shadow connect:
4 ETQ399   default TPPARAM: SHADOW.TPP
2 ETQ366 Connect variables are set for shadow instance access
4 ETQ399 System-nr = '01', GwService = 'sapgw01'
4 ETQ399 Environment variables:
4 ETQ399   dbs_db6_schema=SAPS01
4 ETQ399   auth_shadow_upgrade=1
1 ETQ200 Executing actual phase 'MAIN_SHDRUN/ACT_UPG'.
1 ETQ399 Phase arguments:
2 ETQ399 Arg[0] = 'ACTUPG.BUF'
2 ETQ399 Arg[1] = 'ACTUPG.TPP'
2 ETQ399 Arg[2] = 'ACTUPG.TP0'
2 ETQ399 Arg[3] = 'ACTUPG.ELG'
2 ETQ399 Arg[4] = 'SHDINCIMP.BUF'
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 ETQ383 translates to path "exe"
4 ETQ383 translates to path "exe"
4 ETQ399 2013/12/15 03:42:02: put_execute: (tp) forkpid:18879
4 ETQ399 2013/12/15 03:42:03: put_execute: (tp) forkpid:18881
4 ETQ399 2013/12/15 03:42:03: put_execute: (tp) forkpid:18882

About work processes trace files of the shadow system, I didn't find a work folder under parth /usr/sap/S01/upg/. Does this mean I lost some files? Please tell me if you need any other logs.Thank you!

Best Regards,

Carina Hu

[Former Member · Accepted solution]

It would be in /usr/sap/S01/upg/SUM/abap/SID/DV*/work

I can tell you that it has to do with the /tmp folder as some file is still holding old connection .

Thanks

Rishi Abrol

[Former Member · Accepted solution]

Hi,

IF you say that no work directory . There should be work directory as the shadow system will write the logs in that directory . Does this means that shadow instance was never started.

Can there be reason that due to this power some files were lost. If that is the case you will have to go for reset.

Thanks

Rishi abrol

[Former Member · Accepted solution]

As Rishi Abrol has mentioned already

check if the <sid>adm user has write permissions to /tmp directory

run command #> chmod -R 777 /tmp

I think there is some permission issue for <sid>adm in tmp subdirectory

R3trans can not write dump files there

[Former Member · Accepted solution]

Hi,

I think you are right. I did lost some files caused by the power fail.

I've decided to restart the whole upgrade process.

Thank you!

Best Regards,

Carina Hu

[Reagan · Accepted solution]

Hello

You are not checking the correct path.

The instance number for the shadow system is 01.

It is clearly visible in the first screen shot.

Can you provide me the PHASES file present at /usr/sap/S01/upg/abap/log directory ?

If the shadow system was not created then the tool will not try to connect.

Regards

RB

[Former Member · Accepted solution]

Hi,

I think that 00 is typo as the if you check the initial starting bit

/usr/sap/S01/upg/abap/S01/DVEBMGS00

upgrade tool will not create the same instance no in this directory.

Thanks

Rishi Abrol