Sometimes by mistake you deploy some SDAs which are part of SCAs belonging to portal usage types(EP & EPC), but your netweaver java does not have usage types EP and EPC. Later on when you download stack.xml to upgrade your netweaver java to higher version, then stack.xml contains list of some SCAs because of unnecessary SDAs deployed on your system by mistake. When you start SUM tool, then upgrade fails with error message:
The following problem has occurred during step execution: com.sap.sdt.util.diag.DiagException: Error while executing Task with input file CopyParsLibsForMigration.xml and task COPY_PORTAL_LIBS.
Could not finish Copy operation with parameters fromFile: ‘/usr/sap/<SID>/SYS/global/pcd/pcdStartup.properties’ toDir: ‘/usr/sap/<SID>/SUM/sdt/tmp/portalContent’. Check whether the current user has sufficient permission to execute this operation.
Cannot copy /usr/sap/<SID>/SYS/global/pcd/pcdStartup.properties to directory /usr/sap/<SID>/SUM/sdt/tmp/portalContent.
Input output exception has occurred: fileName: /usr/sap/<SID>/SYS/global/pcd/pcdStartup.properties.
java.io.FileNotFoundException: fileName: /usr/sap/<SID>/SYS/global/pcd/pcdStartup.properties
It happens due to a deployment of an SCAs which belongs to a usage type which does not exist on netweaver java. Here portal is not usage type of netweaver java system and SUM tool triggers pcd migration, but pcd does not exist in the system and it fails. So, in such scenarios if you are sure that portal(EP, EPC) is not usage type in your netweaver java, then please perform the steps:
Either undeploy the SDAs which were deployed by mistake and generate the stack.xml file again or you can skip portal migration in SUM as:
The value for portal migration could be found at SharedInputCatalog.xml under SUM/data direcotry.
On your system the property most probably looks like:
<Property value="true" setBy="ComponentHandlingService" key="IsPortalMigrationNeeded">
So changing the above property to “false” and restarting the SUM tool will skip pcd migration.