Can we change target version in preprocessing phase of Java Upgrade

[Former Member]

Hi All,

We are performing NW 7.0(Dual Stack) to NW 7.31 (Dual Stack) Upgrade.

OS - HP UNIX and DB - Oracle 11.2

In preprocessing phase of Java Stack upgrade under step DEPLOY JAVA COMPONENT, we are getting error -

"par files are no longer supported. please use the migration tools for migrating your file" for Virsa component.

During investigation we found that during stack file generation we got 530_700 version of Virsa which is causing this issue and we should have 530_730 version of Virsa for the upgrade.

Now I am not sure which files we should update to tell SUM to use 530_730 version, We already copied 530_730 version to download directory but still it is picking 530_700 version.

If I go back completely and restart SUM, We will lost our 4-5 days work and ABAP stack also almost completed for preprocessing phase.

We are also fine to drop this component update for this upgrade if there is any file where we can tell SUM to ignore this component as we can do that manually after upgrade and for next upgrade will update stack file.

Please suggest.

Regards,

Shivam

[JPReyes]

Hi Shivam,

Not very orthodox, but have you try to simply modify the stack.xml and replace the conflicting version with the new one?... You might have to restart the phase.

I'm also assuming you have a backup.

Regards, Juan

[Mofizur]

Hi Shivam,

As per the below note , Most likely editing the XML is not going to work.You have to reset and start from scratch..

2143945 - PortalDeploymentException: Par files are no longer supported. Please use the migration too...

Resolution

Steps to be followed to resolve the issue:

1. Identify the SCA which is causing the problem.
2. Most likely this SCA is missing in the stack xml file and wrong version of the SCA was provided in the inbox directory.
3. You need to reset the current upgrade as per the SUM guide and generate a new stack xml file containing the correct target version of this SCA.

To reset the update then below link can be helpful

How to reset an update when you are in Preprocessing roadmap with SUM SP11 - Technology Troubleshoot...

But make sure while regenerating the XML you take care of your VIRSA component carefully 🙂

Thanks,

Mofizur

[Former Member]

I made changes in Jump.JSPM.DataModel.xml file and now I see SUM is picking latest version from download directory but it is giving different error -

Could not update components. Deployment of queue Queue_2015.09.30 at 09:47:53 completed with error Deployment finished with error. See Deploy Controller log /usr/sap/install/SUM/sdt/log/SWITCH/deploy_api.0.log for details. Deployment finished with error. sap.com/VIREPRTA: Deployment of archive VIREPRTA73000_0-20009335.SCA for component sap.com/VIREPRTA aborted Detailed message: 1. Already deployed component has version:1000.530.730.0.0.20120430062559 1. Contains Aborted deployment component: sap.com_grc~aeeprta Deployment of archive VIREPRTA73000_0-20009335.SCA --> grc~aeeprta.sda for component sap.com/grc~aeeprta aborted Detailed message: 1. Webservices common deployment exception. The reason is: Error occurred, trying to parse documentation for web service UserRoleSearchForAEService_5_3. . Additional info: {1} -> while trying to read the field 'name' of a null object loaded from local variable 'entry' See Deploy Controller log /usr/sap/install/SUM/sdt/log/SWITCH/deploy_api.0.log for details.

Not sure if this is due to old version still available in some files or due to some different reason.

Please suggest if you are aware of this issue.

Regards,

Shivam

[Mofizur]

Hi Shivam,

I am not sure about editing Jump.JSPM.DataModel.xml file.

In my opinion you should reset the upgrade,get a valid XML and start a fresh.

Thanks,

Mofizur

[Former Member]

Hello Shivam,

I dont think you can change target version during pre-processing phase. Is the older version of Virsa exist in the XML file itself?

If that is the case maybe you need to recreate the XML with the appropriate version of Virsa.

Regards,

Raja. G

[Mofizur]

Hello,

I can think of two options :-

1) Edit the XML file and put the correct component/file name and see if it works.

     Below Note gives the GRC related information

     1603438 - GRC AC 10.0 EP Plug-In (JAVA), supported NW versions

2) If option 1 does not work then create an OSS message.May be they can give you some other option.

If you have to reset the update then below link can be helpful

How to reset an update when you are in Preprocessing roadmap with SUM SP11 - Technology Troubleshoot...

Thanks,

Mofizur