Error in MAIN_NEWBAS/STARTSAP_NBAS Upgrade EHP1

[Former Member]

Hi

We have errors in this downtime phase of our BI upgrade. It looks like the KERNEL hasn't updated correctly ?

When I run R3INLPGM the environment variables do not show.

The SCS 00 instance started o.k. and Instance 01 is partially up with DISPATCHER JCONTROL SDM SERVER0

WATCHDOG only running.

I've followed all recommendations of note 1165462.

The error I see on the SDT tool is below together with the errors I see when I try to STOPSAP for manual intervention on 00 or 01

I forced an end of the subsystem to do a manual APYSAP of kernel 69 but this has the same results.

Please advise thanks

David

SDT error

Checks after phase MAIN_NEWBAS/STARTSAP_NBAS were negative!

Last error code set: RFC call to subst_get_uvers failed with key RFC_ERROR_COMMUNICATION (open): SAP_CMINIT3 : rc=20 > Connect to SAP gateway failed

Connect_PM DEST=BID, GWHOST=SATURN, GWSERV=sapgw03, SYSNR=03

LOCATION CPIC (TCP/IP) on local host with Unicode

ERROR partner 'SATURN.NFOODS.NET:3303' not reached

TIME Wed Jun 23 21:49:08 201

RELEASE 710

COMPONENT NI (network interface)

VERSION 39

RC -10

MODULE nixxi.cpp

LINE 2779

DETAIL NiPConnect: 10.222.40.91:3303

SYSTEM CALL connect

ERRNO 79

ERRNO TEXT Connection refused

COUNTER 78

System start failed

STOPSAP Errors

stopsap bid 01

Ownership of object GETOBJINF in QTEMP type *USRSPC changed.

Ownership of object GETOBJINF in QTEMP type *USRSPC changed.

Checking input parameters...

Ownership of object GETOBJINF in QTEMP type *USRSPC changed.

Ownership of object GETOBJINF in QTEMP type *USRSPC changed.

Ownership of object GETOBJINF in QTEMP type *USRSPC changed.

collectSystemInfo: found central instance DVEBMGS03 on host SATURN but

central instance already exists as DVEBMGS01 on host SATURN.

StopInstance: Stopping instance 01 of system BID on host SATURN is not

possible. System configuration can not be retrieved.

O4STPSAP: Stopping instance 01 of system BID on host SATURN failed.

Errors occurred in command.

Errors occurred in command.

Caused

[Former Member]

We've experienced a very similar issue upgrading a BW to NetWeaver 7.3. Symptoms appeared to be the same.

In our case, there was SNC enabled in the instance parameter, which needed to be temporarily disabled for this step to proceed.

Parameter snc/enable = 0

Regards,

Sebastian

---

[Former Member]

Hallo,

same issues during upgrade of Solution Manager to 7.1.

Solution:

- Apply Note 1689532 - EHPI/Upgrade Phase MAIN_NEWBAS/STARTSAP_NBAS: Error Starting

BTW: Update the profile of the shadow instance in /sapmnt/<SID>/profile

- set snc/enable = 0 in the instance profile of the shadow instance

Regards, Thomas.

[Former Member]

Hi

The process has moved on after I logged a SAP message and development managed to start instance 01 . But this has now stopped again MAIN_NEWBAS/TABIM_POST . It's giving message "Background job RDDIMPDP could not be started or terminated abnormally" The SM21 messages in instance 03 suggest it wants instance 01 started.

I've tried to do the ADDENVVAR parameters per note 1165462 but startup still fails no matter what I try - STARTSAP BID 01 (*DUP) or starting QP2TERM and invoking special command via JCONTROL e.g. call jcmon 'pf=/usr/sap/BID/SYS/profile/BID_DVEBMGS01_SATURN' or with -magic which was in one of the earlier START_J2EE_DEPL logs

Thanks in advance for advise.

Regards

David

[Former Member]

HI David

Did SAP ever tell you what they did to start the instance? We are facing the same exact error messge in the same phase while upgrading to Ehp4.

Any suggestions would be appreciated,,,

Thanks

Sap ques

[Former Member]

solved it on my own...,

Its the stupid as4_examine issue with programs saposcol with startup..wanted to let anyone else know..

Thanks

[Former Member]

Hi. Coudl you give more details on this issue? we are having the same problem during our downtime...

[Former Member]

Hi Miguel,

her wanted to say, that either the shadow during uptime or later the real instance during downtime restarts SAP several times and ALWAYS start saposcol as well. If this fails - which is a really crazy behviour - SAP shuts down again !

=> The easiest - especially during an upgrade - is to just comment the saposcol start in the start profile

Then you have repeat the upgrade after shutting down the instance completey with killing all proceeses and it should work fine ...

Regards

Volker Gueldenpfennig, consolut international ag

http://www.consolut.com http://www.4soi.de http://www.easymarketplace.de