cancel
Showing results for 
Search instead for 
Did you mean: 

Upgrade stuck in phase STARTSAP_TBUPG

gsantana
Explorer
0 Kudos

Dear Gurus,

Im in the process of upgrade our systems to EPH7, but in the phase of Execution im getting the error STARTSAP_TBUPG, the sapcontrol show GRAY a dispatcher, but the instance start successfully.

I have tried upgrade kernel to the last version possible for me 742 p300.

checked sappfpar for parameters error but nothing help me to start, and the trace files dev_disp and dev_w0 doesnt show any error.

Regards

Accepted Solutions (1)

Accepted Solutions (1)

Former Member
0 Kudos

Hello Geyson,

Just to be sure that I follow you, you say the instance is running. when you run 'dpmon' you see running work processes ? Also, when you run saplogon, you get a logon screen ?

In your attached file we see two PIDs for the dispatcher. When you do a 'ps -ef' do you find PID 8740 ?

What I would try is:

1. stopsap

2. cleanipc

3. sapcontrol -nr NN -function StopService

4. check there are no processes for <sid>adm

5. startsap

6. sapcontrol -nr NN -function GetProcessList

KR,

Amerjit

gsantana
Explorer
0 Kudos

Dear Amerjit CHAHAL,

Thank you for your prompt answer.

i've tried multiple commands, even reboot server and starting again from the phase and i stiil have the error, and yes i get the logon screen.

I have tried the following command:

  1. stopsap all
  2. cleanipc 00 remove
  3. sapcontrol -nr NN -function StopService
  4. ps -ef |grep <sid>adm
  5. kill -9 pid found.
  6. ipcs and ipcrm -s semaphores found.
  7. sapcontrol -nr NN -function StartService
  8. startdb
  9. R3trans -d and -x show 0000.
  10. startsap r3,
  11. sapcontrol -nr NN -function GetProcessList (It Show the previous attatched logs).
  12. But i can get to SAP Logon Screen, im unable to log on because is still in upgrade mode.

Regards

Geyson Rodriguez

Former Member
0 Kudos

Hi Geyson,

Is the PID of the dispatcher that is showing Grey when you run sapcontrol still the same PID from your attached log ?

If that is the case then we may have a file that is acting as a type of semaphore still hanging around.

ps: What is your o/s ?

KR,

Amerjit

gsantana
Explorer
0 Kudos

Hi Amerjit,

Right now is not the same PID, i have tried again and the pid is different but is not showing using the command ps -ef.

cat /etc/redhat-release

Red Hat Enterprise Linux Server release 7.1 (Maipo).

Former Member
0 Kudos

Hi Geyson,

This is a curious one.

So we can see that the dispatcher seems to be getting started twice. First with PID 14009 and finally with 14012. That in itself is odd due to the sequence.

0 = Dispatcher

1 = Message Server

2 = Enqueue Server

3 = Dispatcher

4 = Gateway

You can see that the 0 (zero) starting first makes absolutely no sense and would fail (as is the case) as neither the msg or enq are running.

Things I'd check if I was in this situation.

1. Check entries in /usr/sap/sapservices.

2. Check your Instance profile to make sure there isn't a duplicate or incorrectly numbered entry (Execute_nn) and also entries for disp+work startup.

KR,

Amerjit

gsantana
Explorer
0 Kudos

Thank you Amerjit,

For some reason i haved duplicated entries in instance profile for startup of dispatcher.

Thats fix my problem.

Thank you again!!.    

Answers (1)

Answers (1)

former_member182657
Active Contributor
0 Kudos

Hi Geyson,

As per my assumptions,you're using SUM 1.0 SP14,if yes then for the issue i would suggest you to follow SAP Central note  2084104 - Central Note - Software Update Manager 1.0 SP14 [lmt_005]


---------------------< I065580 11/SEP/12 >---------------------------

MAIN_NEWBAS/STARTSAP_TBUPG:System start failed on NT IA64

During the MAIN_NEWBAS/STARTSAP_TBUPG phase the upgrade stops with the error message:

Checks after phase MAIN_NEWBAS/STARTSAP_TBUPG were negative! (...) System start failed

A possible solution can be note 1696517. To prevent the error, select a target kernel version that includes the related correction.

along with SAP Note  1696517 - Memory alignment problem in sapstartsrv.exe process

Hope this will help you in resolution.

Regards,

gsantana
Explorer
0 Kudos

Dear Gaurav Rana,

I've updated the kernel and sapcontrol too, but this note seems to fit more to NT systems and IA64,

I have RedHat EL7.

Regards.