avatar image
Former Member

Can we change target version in preprocessing phase of Java Upgrade

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

Add comment
10|10000 characters needed characters exceeded

  • Get RSS Feed

2 Answers

  • avatar image
    Former Member
    Oct 06, 2015 at 05:09 AM

    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

    Add comment
    10|10000 characters needed characters exceeded

  • Oct 06, 2015 at 09:47 AM

    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

    Add comment
    10|10000 characters needed characters exceeded

Skip to Content