EHP5 update stops at downtime

[Former Member]

Dear all,

I am in the process of updating to NW EHP5 on HPUX 11,23.

However at the downtime phase it stops at phase MAIN_NEWBAS/STARTSAP_NBAS.

In the SAPehpi.ECO file the relevant paragraph reads:

ENV: SAPSYSTEMNAME=L06

ENV: auth_shadow_upgrade=0

ENV: dbms_type=ORA

ENV: dbs_ora_schema=SAPL03

ENV: dbs_ora_tnsname=L06

EXECUTING /usr/sap/L06/DVEBMGS00/exe/startsap (/usr/sap/L06/DVEBMGS00/exe/startsap) R3 DVEBMGS00

Checking L06 Database

Database is running

-

---

Starting Startup Agent sapstartsrv

OK

Instance Service on host yoda-upg started

-

---

starting SAP Instance DVEBMGS00

Startup-Log is written to /home/l06adm/startsap_DVEBMGS00.log

-

---

/usr/sap/L06/DVEBMGS00/exe/sapcontrol -prot NI_HTTP -nr 00 -function Start

startup of Instance failed

See /home/l06adm/startsap_DVEBMGS00.log for details

Process with ID 14094 terminated with status 1

startsap_DVEBMGS00.log reads:

Trace of system startup/check of SAP System L06 on Mon Aug 22 10:59:58 METDST 2011

Called command: /usr/sap/L06/DVEBMGS00/exe/startsap start

-

---

11:00:01

Starting Startup Agent sapstartsrv

-

---

11:00:01

Instance Service on host yoda-upg started

-

---

11:00:01

starting SAP Instance DVEBMGS00

-

---

11:00:01

Startup-Log is written to /home/l06adm/startsap_DVEBMGS00.log

-

---

11:00:01

/usr/sap/L06/DVEBMGS00/exe/sapcontrol -prot NI_HTTP -nr 00 -function Start

22.08.2011 11:00:02

Start

FAIL: HTTP error, HTTP/1.1 401 Unauthorized

-

---

11:00:12

startup of Instance failed

Can you please shed some light on this problem.?

Thanks

Bob

[former_member204746]

your system visited the dark side of the force. Ask Yoda to help you out.

(sorry, I just couldn't resist after seeing your host name (yoda-upg)

Seriously, check contents of file dev_w0 and other files in the EHPI directory.

[Former Member]

Yoda has helped me out.

Problem was solved.

And for your info, we also have Yabba and a Solo in our server park.

Edited by: Bob Gulien on Aug 25, 2011 8:10 AM

[former_member204746]

He He !

Care to share what solved your issue for the benefit of the community?

[Former Member]

I rebuild a copy of our production system to a testmachine for testing the update EHP4 to EHP5.

The system are HW identical.

So with HPUX ignite you clone the system.

From our SAN box we cloned the volumes and started to rename everything to a new SID.

Evberything looked OK till downtime, when the installation program shuts down the system and starts transferring the shadow system to the real system.

Then it starts the real SID.

That's where it went wrong..

sapcontrol looks into the file /usr/sap/sapservices and in that file the old SID was still present.

Changed it to the new SID and it went on.