Hi Rajani,
If this checkinstall script: check-seeded-object-name-conflicts.xml failed, this is because there is a conflict in the object names. Basically this script checks for any custom objects with same names as seeded objects, since they can get completely overwritten during upgrades.
Now, the script runs this statement and it shows that there is result returned:
SELECT CODE objectcode FROM ODF_OBJECTS
WHERE IS_CUSTOM = 1
AND CODE IN ( 'portfolio' )
This means that you have an object in Studio - Objects, named portfolio and marked as custom. If customers have truly custom objects with one of the reserved OOTB object code, they would have, as requested, to back it up with XOG, and rename it by deleting and XOGging back since it will get overwritten during the 14.2 upgrade.
However, since you are upgrading from 13.1, portfolio is an OOTB name of the object back then. If this is the case, something might have gone wrong with your upgrade so far: because the OOTB portfolio object gets completely deprecated during the install to 13.2, and replaced with pfm_portfolio instead. This doesn't seem to have happened. Did you encounter any errors during your 13.2 upgrade in install.log and admin.log?
To proceed further, I recommend you to raise a Support ticket, so you can provide all the logs and we ensure the objects are correctly upgraded. Trying to reset the object with a manual query can only be done after we at Support review it and approve as a solution for your exact situation; else it's unsupported.
Also I am concerned this may have been caused by another prior upgrade issue so checking this together is the best way to proceed in my opinion.
Looking forward to your feedback.
Kind Regards
Nika Hadzhikidi
CA Technologies
Principal Support Engineer