Error in UPDATE_DEPLOY_LISTS phase - PI 7.3 upgrade

[Former Member]

Hi Gurus,

We have a PI 7.0 system which has certain EP components deployed which were put in unfortunately although SAP doesnt recommend it.

We are trying to have the system now upgraded to PI 7.3 system. We are pulling all our components from 700 version to 730 version including the EP components.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:751) [Thread[main,5,main]]: Phase PREPARE/CONFIG/UP

DATE_DEPLOY_LISTS has been started.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.initialize(AbstractPhaseType.java:752) [Thread[main,5,main]]: Phase type is com.sap.s

dt.j2ee.phases.PhaseTypeHandleComponents.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:403) [Thread[main,5,main]]: Parameter inputFile=M

igratedParFiles.properties

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:403) [Thread[main,5,main]]: Parameter inputXIFile

=JPLMigratedArchives.properties

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:403) [Thread[main,5,main]]: Parameter componentTy

pe=par_and_xi

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.logParameters(AbstractPhaseType.java:403) [Thread[main,5,main]]: Parameter action=upda

te

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeHandleComponents.checkParameters(PhaseTypeHandleComponents.java:482) [Thread[main,5,main]]: Checking phase paramet

ers componentType.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeHandleComponents.checkParameters(PhaseTypeHandleComponents.java:486) [Thread[main,5,main]]: Phase parameters have

been checked. All required 2 phase parameters have been set.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.j2ee.phases.PhaseTypeHandleComponents.execute(PhaseTypeHandleComponents.java:166) [Thread[main,5,main]]: Looking for portal comp

onents in the target release vector.

Jan 15, 2012 11:01:35 PM [Error]: com.sap.sdt.ucp.phases.AbstractPhaseType.doExecute(AbstractPhaseType.java:883) [Thread[main,5,main]]: Exception has occurred

during the execution of the phase.

Jan 15, 2012 11:01:35 PM [Error]: com.sap.sdt.j2ee.phases.PhaseTypeHandleComponents.handleParsAndXI(PhaseTypeHandleComponents.java:195) [Thread[main,5,main]]: There are par components for migration on the source system, but the migration controller did not migrate any par archives.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:925) [Thread[main,5,main]]: Phase PREPARE/CONFIG/UP

DATE_DEPLOY_LISTS has been completed.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:926) [Thread[main,5,main]]: Start time: 2012/01/15

23:01:35.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:928) [Thread[main,5,main]]: End time: 2012/01/15 23

:01:35.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:930) [Thread[main,5,main]]: Duration: 0:00:00.086.

Jan 15, 2012 11:01:35 PM [Info]: com.sap.sdt.ucp.phases.AbstractPhaseType.cleanup(AbstractPhaseType.java:931) [Thread[main,5,main]]: Phase status is error.

Please suggest what this error might be related to.

We are taking all components to 730 version.

THanks and Regards,

Karan Shah

[sunny_pahuja2 · Accepted solution]

Hi,

As per log of your upgrade, it shows that you have applied some par files on your PI 7.00 system. But upgrade cannot migrate it to 730 version. Because from NW 730 PAR files are no more supported and EPA files are supported. So, you need to migrate these files manually.

Thanks

Sunny

[Former Member · Accepted solution]

Hi,

Thanks for the reply. We just observed that EAR files and PAR files are not supported in NW73.

Any idea where can be the log be for the PAR files that might be an issue?

We are not able to get any log where we get this information. We are checking with SAP. They have seen such issue with windows systems and hence can't provide for our upgrade which is on HP-UX (Oracle)

Thanks and Regards,

Karan Shah

[sunny_pahuja2 · Accepted solution]

Hi,

As per my understanding, you can resolve this problem either by undeploying par files and then do the upgrade or you can convert these par files into EPA format which is supported by NW 7.3. You can also check SAP note 1539463.

As far as logs are concerned then there are no par file specific logs. You have to check either upgrade logs or JSPM logs to find more information.

Thanks

Sunny

[Former Member · Accepted solution]

Hi Sunny,

We have tried finding the exact PAR files but we are not able to still get the exact problematic components.

SAP has been checking the issue since 3 days but have not reverted anything concrete except the suggestion that we remove the erroneous par_war_migration_controller.sda from the file MIGRATIONAUSF.LST and retry.

They have responded mentioning that there are many Portal archives which are giving an error. as mentioned below:

Error during migration of archive

/usr/sap/DXI/upg/java/data/mig/DEPLOYARCHIVES/pcd_upgrade.sda which has

been extracted to directory /usr/sap/DXI/upg/java/migtool/pcd_upgrade.

Could not execute MTI process. See log files

/usr/sap/DXI/upg/java/log/JMT_FRAMEWORK_MFS_01.OUT and

/usr/sap/DXI/upg/java/log/JMT_FRAMEWORK_MFS_01.ERR.

Return code condition success evaluated to false for process java for

action RUN_MTI.

Error during migration of archive

/usr/sap/DXI/upg/java/data/mig/DEPLOYARCHIVES/sap.com_cafeu_gp

model~migr.sda which has been extracted to directory

/usr/sap/DXI/upg/java/migtool/sap.com_cafeu_gpmodel~migr.

Could not execute MTI process. See log files

/usr/sap/DXI/upg/java/log/JMT_FRAMEWORK_MFS_01.OUT and

/usr/sap/DXI/upg/java/log/JMT_FRAMEWORK_MFS_01.ERR.

Return code condition success evaluated to false for process java for

action RUN_MTI.

Error during migration of archive /usr/sap/DXI/upg/java/data/mig/DEPLOYARCHIVES/sap.com_tcje_webservicesmigration.sda which has been extractedto directory

/usr/sap/DXI/upg/java/migtool/sap.com_tcje_webservicesmigration.

Could not execute MTI process. See log files

/usr/sap/DXI/upg/java/log/JMT_FRAMEWORK_MFS_01.OUT and

/usr/sap/DXI/upg/java/log/JMT_FRAMEWORK_MFS_01.ERR.

Return code condition success evaluated to false for process java for action RUN_MTI.

We have been able to upgrade a system which was built from an export of our QA system which went ahead fine.

The only difference is EP components which are deployed in our development system.

Any attempt to undeploy those components leaves behind a config_db entry and hence system during the upgrade detects it as a component which is not present in stack.

We have seen a similar error in the forum Link:[http://forums.sdn.sap.com/thread.jspa?threadID=2087277]

Would the same note as suggested there be applicable here? Just a wild guess

Thanks and Regards,

Karan Shah

Edited by: Karan Shah on Jan 18, 2012 3:46 AM

[sunny_pahuja2 · Accepted solution]

Hi,

Could you please let us know what all sda files you have deployed on the portal ? Also, if you have uninstalled them from the system, what are the entries in config_db ?

Thanks

Sunny

[Former Member · Accepted solution]

Hi,

The solution tothis problem was the upgrade tool was not detected the EP usage type and hence not migrating the EP components / services.

It was resolved by depolying all the EP components which are supposed to be there.

Please note this was actually a non supported scenario as EP + PI in one system is not supported.

Thanks and Regards,

Karan Shah

[Former Member]

Just follow the upgrade guide and if you do not hav all the components needed for a full Portal usage type then deploy the same.

[Former Member]

Just follow the upgrade guide and if you do not hav all the components needed for a full Portal usage type then deploy the same.