Clarity

We are on CA PPM version 15.3

While doing PMO Accelerator installation we are facing below error and installation is unsuccessful:

12/13/17 6:29 AM (admin) Loading registered objects for data warehouse attributes bootstrap...
12/13/17 6:36 AM (admin) ERROR 13-12 06:36:21,609 - rollback exception
12/13/17 6:36 AM (admin) java.lang.OutOfMemoryError: Java heap space
12/13/17 6:36 AM (admin)  at com.niku.xql2.jdbc.JDBCRecord.<init>(JDBCRecord.java:149)
12/13/17 6:36 AM (admin)  at com.niku.xql2.pmd.PMDRecord.<init>(PMDRecord.java:26)
12/13/17 6:36 AM (admin)  at com.niku.xql2.pmd.PMDRecordSet.singleRecordSet(PMDRecordSet.java:363)
12/13/17 6:36 AM (admin)  at com.niku.xql2.pmd.PMDRecordSet.executePMDStatement(PMDRecordSet.java:279)
12/13/17 6:36 AM (admin)  at com.niku.xql2.pmd.PMDRecordSet.<init>(PMDRecordSet.java:87)
12/13/17 6:36 AM (admin)  at com.niku.xql2.pmd.PMDDataSource.select(PMDDataSource.java:94)
12/13/17 6:36 AM (admin)  at com.niku.xql2.XQLVisitor.getObjectSet(XQLVisitor.java:868)
12/13/17 6:36 AM (admin)  at com.niku.xql2.XQLVisitor.getField(XQLVisitor.java:1480)
12/13/17 6:36 AM (admin)  at com.niku.xql2.eval.XQLPropertyNode.eval(XQLPropertyNode.java:92)
12/13/17 6:36 AM (admin)  at com.niku.xql2.eval.XQLEvaluator.parse(XQLEvaluator.java:40)
12/13/17 6:36 AM (admin)  at com.niku.xql2.XQLVisitor.eval(XQLVisitor.java:1086)
12/13/17 6:36 AM (admin)  at com.niku.xql2.XQLVisitor.eval(XQLVisitor.java:1060)
12/13/17 6:36 AM (admin)  at com.niku.xql2.handlers.LoopHandler.preProcess(LoopHandler.java:115)
12/13/17 6:36 AM (admin)  at com.niku.xql2.XQLVisitor.preProcess(XQLVisitor.java:1385)
12/13/17 6:36 AM (admin)  at com.niku.union.xml.dom.DOMWalker.preProcess(DOMWalker.java:194)
12/13/17 6:36 AM (admin)  at com.niku.union.xml.dom.DOMWalker.traverseIntern(DOMWalker.java:74)
12/13/17 6:36 AM (admin)  at com.niku.union.xml.dom.DOMWalker.traverse(DOMWalker.java:51)
12/13/17 6:36 AM (admin)  at com.niku.xql2.handlers.LoopHandler.processObject(LoopHandler.java:388)
12/13/17 6:36 AM (admin)  at com.niku.xql2.handlers.LoopHandler.processSet(LoopHandler.java:259)
12/13/17 6:36 AM (admin)  at com.niku.xql2.handlers.LoopHandler.preProcess(LoopHandler.java:216)
12/13/17 6:36 AM (admin)  at com.niku.xql2.XQLVisitor.preProcess(XQLVisitor.java:1385)
12/13/17 6:36 AM (admin)  at com.niku.union.xml.dom.DOMWalker.preProcess(DOMWalker.java:194)
12/13/17 6:36 AM (admin)  at com.niku.union.xml.dom.DOMWalker.traverseIntern(DOMWalker.java:74)
12/13/17 6:36 AM (admin)  at com.niku.union.xml.dom.DOMWalker.traverseIntern(DOMWalker.java:92)
12/13/17 6:36 AM (admin)  at com.niku.union.xml.dom.DOMWalker.traverseIntern(DOMWalker.java:92)
12/13/17 6:36 AM (admin)  at com.niku.union.xml.dom.DOMWalker.traverse(DOMWalker.java:36)
12/13/17 6:36 AM (admin)  at com.niku.xql2.XQLProcessor.process(XQLProcessor.java:257)
12/13/17 6:36 AM (admin)  at com.niku.xql2.XQLProcessor.process(XQLProcessor.java:283)
12/13/17 6:36 AM (admin)  at com.niku.xql2.binding.ServiceControlBindingXql.processFile(ServiceControlBindingXql.java:390)
12/13/17 6:36 AM (admin)  at com.niku.xql2.binding.ServiceControlBindingXql.getDocument(ServiceControlBindingXql.java:273)
12/13/17 6:36 AM (admin)  at com.niku.xql2.binding.ServiceControlBindingXql.processRequest(ServiceControlBindingXql.java:157)
12/13/17 6:36 AM (admin)  at com.niku.odf.object.Bootstrap.executeXBL(Bootstrap.java:2916)
12/13/17 6:36 AM (admin) ERROR 2017-12-13 06:36:21,609 [main] union.service rollback exception
12/13/17 6:36 AM (admin) java.lang.OutOfMemoryError: Java heap space
12/13/17 6:36 AM (admin)  at com.niku.xql2.jdbc.JDBCRecord.<init>(JDBCRecord.java:149)

We have tried increasing the memory for apps in jvm parameters, but still getting the same error.

Any thoughts ?

This error is not due to PMO installation , can you attach the app ca log please 

Hi Suman,

I have updated the app-ca logs

I dont see any heap error, which log file you saw the heap. Was it during installation and if so, how much memory you have in you OS layer and during installation how much free memory is showing

I have updated admin.log for errors

1st problem is the upgrade looks to be problematic 

Nov 10, 2017 1:31:58 PM Error executing command: db upgrade -Dfail.on.errors=true -Dxdm.apply=true -Dupgrade.phase=upgrade
E:\CA\Clarity\.setup\scripts\db.xml:1931: The following error occurred while executing this line:
E:\CA\Clarity\.setup\scripts\db.xml:1945: The following error occurred while executing this line:
E:\CA\Clarity\.setup\scripts\db.xml:1975: The following error occurred while executing this line:
E:\CA\Clarity\.setup\scripts\db.xml:1985: The following error occurred while executing this line:
E:\CA\Clarity\.setup\scripts\db.xml:2038: The following error occurred while executing this line:
E:\CA\Clarity\.setup\scripts\db.xml:2200: E:\CA\Clarity\.setup\scripts\db.xml:2201: The following error occurred while executing this line:
E:\CA\Clarity\.setup\scripts\db.xml:2538: The following error occurred while executing this line:
E:\CA\Clarity\.setup\scripts\db.macros.xml:3054: The following error occurred while executing this line:
E:\CA\Clarity\.setup\scripts\db.xml:624: The following error occurred while executing this line:
E:\CA\Clarity\.setup\scripts\db.macros.xml:56: Java returned: 1
at org.apache.tools.ant.ProjectHelper.addLocationToBuildException(ProjectHelper.java:568)
at org.apache.tools.ant.taskdefs.Ant.execute(Ant.java:443)

Although it showed success at the end

11/10/17 1:32 PM (admin) upgrade.phase = upgrade
11/10/17 1:32 PM (admin) install.upgrade.dir = E:\CA\Clarity/upgrade
11/10/17 1:32 PM (admin) maintenance.release = false
11/10/17 1:32 PM (admin) ------------------------------------------------------------
11/10/17 1:32 PM (admin) Upgrade for Release = 14.4.0 was successful
11/10/17 1:32 PM (admin) ------------------------------------------------------------
11/10/17 1:32 PM (admin) ------------------------------------------------------------
11/10/17 1:32 PM (admin) Upgrade for Release = 15.1.0 was successful
11/10/17 1:32 PM (admin) ------------------------------------------------------------
11/10/17 1:32 PM (admin) ------------------------------------------------------------
11/10/17 1:32 PM (admin) Upgrade for Release = 15.2.0 was successful
11/10/17 1:32 PM (admin) ------------------------------------------------------------
11/10/17 1:32 PM (admin) ------------------------------------------------------------
11/10/17 1:32 PM (admin) Upgrade for Release = 15.3.0 was successful
11/10/17 1:32 PM (admin) ------------------------------------------------------------

The upgrade is not proper then multiple times you tried installing PMO, i believe you should roll back to working version prior to 15.3 and re do the upgrade 

This issue was due to a reference to Permsize in the JVM Parameters. Permsize is no longer needed in 15.3. Once the  reference to -XX:PermSize was removed in the JVM Parameters in CSA, the install completed successfully. 

Just to clarify, removal of the reference to -XX:PermSize was needed because PermSize is no longer valid in Java 8, which is the version supported with PPM 15.3. See: Release Notes (SaaS) - CA PPM SaaS - 15.3 - CA Technologies Documentation for more details on capabilities.