Error during MAIN_NEWBAS/STARTSAP_NBAS

[Former Member]

Hello,

We are upgrading from 4.7 to ECC 6.0 EHP 5 and we are getting an error on phase MAIN_NEWBAS/STARTSAP_NBAS.

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 GWHOST=ocean71, GWSERV=sapgw00, SYSNR=00 LOCATION CPIC (TCP/IP) on local host with Unicode ERROR partner '10.100.100.71:3300' not reached TIME Mon Jan 9 12:00:18 2012 RELEASE 720 COMPONENT NI (network interface) VERSION 40 RC -10 MODULE nixxi.cpp LINE 2898 DETAIL NiPConnect: 10.100.100.71:3300 SYSTEM CALL connect ERRNO 79 ERRNO TEXT Connection refused COUNTER 866 System start failed Earlier, validating the profile failed, see INSTANCE.OUT

In the phases.log I see the following

2WETQ372 test RFC failed, rc="-1"

2 ETQ370 starting test RFC

4 ETQ359 RFC Login to: System="DEV", Nr="00", GwHost="ocean71", GwService="sapgw

00"

4 ETQ359 RFC Login to: System="DEV", Nr="00", GwHost="ocean71", GwService="sapgw

00"

2 ETQ231 RFC Login failed

4 ETQ359 RFC Login to: System="DEV", Nr="00", GwHost="ocean71", GwService="sapgw

00"

2 ETQ231 RFC Login failed

2WETQ372 test RFC failed, rc="-1"

2EETQ354 Starting system failed, rc="0"

4 ETQ010 Date & Time: 20120109120018

Any help is appreciated.

Thanks

Scott

[Former Member]

We had to change our instance profile. SAP had us remark out the following parameters

ipc/shm_psize_02 = -20

ipc/shm_psize_06 = -20

ipc/shm_psize_20 = 0

[Former Member]

hello Scott,

Please execute SAPPFPAR after modifying the parameter to avoid any other parameter related problems.

Thanks,

Siva Kumar

[Former Member]

Hi Scott,

In the phase MAIN_NEWBAS/STARTSAP_NBAS upgrade tool is trying to start SAP system and is unabe to.

Please check the logs and try to bring up the system.

If not perform a clean shutdown and start the system and repeat the phase.

Regards,

Ershad Ahmed.

[Former Member]

Hello Scott,

Please take a look at dispatcher and latest work processes trace files for the reason of this problem. Try to start the instance manually and see.

This problem might occur when your system does not have latest kernel installed. Do you have the latest target kernel?

If not, please update kernel and resume the upgrade. It should be working fine.

Thanks,

Siva Kumar

[Former Member]

Hi,

The below logs are for the phases, which are seeking an RFC login into the system. This would fail as the system itself is not up.

Request you to check the latest updated dev_disp* and dev_w* logs for the system at /usr/sap/<SID>/DVE../work location.

They would have further details as to why the system fails to start.

Regards,

Srikishan