Upgrade from XI 3.0 to PI 7.3 stuck at CHECK_INSTANCES_DETECTED

[Former Member]

Hi

We are trying to upgrade NW04 / XI 3.0 to NW7.3/PI7.3.

We are stuck at CHECK_INSTANCES_DETECTED (Configuration Phase).

[Error]: com.sap.sdt.j2ee.services.servicesimpl.CheckInstancesService.checkDialogInstancesDetected(CheckInstancesService.java:131) [Thread[main,5,main]]: There is a mismatch between the dialog instances detected by the maintenance procedure and <br>the dialog instances read from Configuration Manager. Possible reasons can be: <br> Dialog instances were removed before starting the maintenance procedure and SAP Note 871523 was not applied afterwards. <br> Some of the dialog instances were not up and running when the procedure was started. <br><b>Dialog instances detected by the maintenance procedure</b>:<br> none <b>Dialog instances read from Configuration Manager</b>: ID4058154;ID4154679;

The reported instances ID4058154 and ID4154679 are the Dialog Instances that we have been using for some time now.

We have tried the following till now and nothing has helped us:

• Restart all the instances along with cleanipc
• Check consistency between Instance IDs and Box Numbers for all instances (SAP note 1156185)
• Added SAPSYSTEM = 40 and SAPSYSTEM = 41 in the respective profile files
• Checked SAP note 871523
• Restarted upgrade from the first phase

Can anyone help resolve this problem

regards

AKD

[Former Member · Accepted solution]

The following worked for us:

1. Start sapstartsrv for all the instances in the landscape

sapstartsrv pf=/sapmnt/<SID>/profile/START_<INSTANCE>_<host> -D

The start profile must be used (for NW 2004)

2. Reset upgrade and restart

The instances are read in an earlier step and compared with the instances listed in Config Tool, which is why the restart of upgrade is required.

regards

AKD

[JPReyes]

Hi Anil,

As far as I can see this is a problem of consistency between parameter j2ee/instance_id and instances registered in Configtool. Can you check if they match?

Regards, Juan

[Former Member]

Hello Juan

We do not see this parameter in any profile files. If I understood SAP note 1156185 correctly, j2ee/instance_id is relevant NW 7.0 (we are using NW 2004).

We did compare the entries in /usr/sap/<SAPSID>/<instance-name>/j2ee/cluster/bootstrap/bootstrap.properties with the one shown in Config Tool and they match.

regards

AKD

[JPReyes]

is there any chance that additional instances where uninstalled in the past and not properly removed?

The message says

There is a mismatch between the dialog instances detected by the maintenance procedure and <br>the dialog instances read from Configuration Manager

It doesnt necesarely mean that are the instances currently running.

dialog instances read from Configuration Manager</b>: ID4058154;ID4154679;

Seems like your current instances are been detected without issues. I'll be leaning to think that other instance_ids where created and deleted.

Regards, Juan

[Former Member]

Hi Juan,

Yes, there was an instance 04 that was uninstalled. We have followed SAP note 871523 to ensure that the config tool has no traces left of 04 instance and even repeated the upgrade thrice.

Dialog instances detected by the maintenance procedure</b>:<br> none should mean that the working DIs are not detected. Right?

regards

AKD

[JPReyes]

Yes, it should list the available instances... theres something missing somewhere.

Maybe reinstalling the SUM could help.. read,

http://scn.sap.com/thread/3184566

Regards, Juan

[Former Member]

Hi Juan,

We did check the thread.

We are upgrading using SAPup/SAPJup

.

- SAPup and SAPJup for Upgrades from Source Release SAP NetWeaver 7.0 and Lower

- Software Update Manager for Upgrades from Start-Release SAP NetWeaver 7.1 and Higher

regards

AKD

[JPReyes]

Hi Anil,

Havent used  SAPJUP in a good while, but the concept is the same, reinstall to reset the SAPUp logs... i think its worthy a try,

Regards,

Juan

[Former Member]

Make sure you don't see any enrty regarding deleted dialog instance in /etc/sapservices..

Regards,

Vishal