Description of problem: Portal doesn't start with all oracle databases (R1, R1-RAC, R2, R2-RAC). There are links to logs: https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/6.0/view/UI%20Database%20Support/job/epp6_ui_selenium_tests_db_oracle11gR2RAC/25/consoleText https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/6.0/view/UI%20Database%20Support/job/epp6_ui_selenium_tests_db_oracle11gR2/19/consoleText https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/6.0/view/UI%20Database%20Support/job/epp6_ui_selenium_tests_db_oracle11gR1RAC/35/consoleText https://jenkins.mw.lab.eng.bos.redhat.com/hudson/view/EPP/view/6.0/view/UI%20Database%20Support/job/epp6_ui_selenium_tests_db_oracle11gR1/27/consoleText
The problem is caused by Oracle DB constrain - the name of identifier can't be longer then 30 characters. If the isolated JCR mode is set (gatein.jcr.db-structure-type=isolated in configuration.properties), the JCR tries to create objects with identifiers longer then 30 chars, i.e.: JCR_IDX_IPORTALSYSTEM_PARENT_FK, which leads to the "ORA-00972: identifier is too long" error. I can think of 3 different ways to resolve this problem: 1. (Prefered) Turn off the "isolated" mode and use "single" as in the previous EPP/JPP versions. The isolated mode can be a feature of JPP, which is not turned on by default. 2. Rename the JPP workspaces to much shorter names, like "portal-system"-"p-sys", "portal-work"->"p-work". 3. Reconfigure databases in the lab. I'm not sure if this is possible to do.
The problem is in the datasouce configuration. You are disabling the JTA (setting jta=false), but the default value in gatein/jpp is jta=true. Deleting jta=false from the datasouce configuration (true is the default value) resolves this problem.