Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Upgrade script fails for oracledate at generateDDL step

SA-1848

Summary



User is trying to upgrade Pega 7.1.5 to 7.1.6 using the upgrade script bundled in Pega 7.1.6 full package (not the upgrade package). Upon triggering the upgrade script, they observe an error during the DDL generation step.

Error Messages



Error generating ddl for oracledate, RULES
Problem running XPath expression (//* except //pega:routineGroup[@filter='udf']/*) intersect (//pega:table[tokenize(@schematype, ',')[.='data']] | //pega:privilege[tokenize(@schematype, ',')[.='data']] | //pega:viewGroup[tokenize(@schematype, ',')[.='data']]/* | //pega:routineGroup[tokenize(@schematype, ',')[.='data']]/* | //pega:trigger[tokenize(ancestor::pega:table/@schematype, ',')[.='data']] | //pega:index[tokenize(ancestor::pega:table/@schematype, ',')[.='data']]| //pega:dataUpdateGroup[tokenize(@schematype, ',')[.='data']]/* ) on the DOM.Original Message: null
com.pega.pegarules.data.ddl.SchemaManagerTransformerException: Problem running XPath expression (//* except //pega:routineGroup[@filter='udf']/*) intersect (//pega:table[tokenize(@schematype, ',')[.='data']] | //pega:privilege[tokenize(@schematype, ',')[.='data']] | //pega:viewGroup[tokenize(@schematype, ',')[.='data']]/* | //pega:routineGroup[tokenize(@schematype, ',')[.='data']]/* | //pega:trigger[tokenize(ancestor::pega:table/@schematype, ',')[.='data']] | //pega:index[tokenize(ancestor::pega:table/@schematype, ',')[.='data']]| //pega:dataUpdateGroup[tokenize(@schematype, ',')[.='data']]/* ) on the DOM.Original Message: null
at com.pega.pegarules.data.ddl.SchemaManager.getTopLevelDocument(Unknown Source)
at com.pega.pegarules.data.ddl.SchemaManager.getSchemaManagerFromCustomExpression(Unknown Source)
at com.pega.pegarules.data.ddl.SchemaManager.getCustomUpdateDDLTR(Unknown Source)
at com.pega.pegarules.data.ddl.SchemaManager.getUpdateDDLTR(Unknown Source)
at com.pega.pegarules.data.ddl.SchemaManager.getUpdateDDL(Unknown Source)
at com.pega.pegarules.data.ddl.SchemaGenerator.generateUpgradeDDL(SchemaGenerator.java:343)
at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1146)
Caused by: javax.xml.xpath.XPathExpressionException
at org.apache.xpath.jaxp.XPathImpl.evaluate(XPathImpl.java:295)
... 7 more
Caused by: javax.xml.transform.TransformerException: Expected ), but found: except
at org.apache.xpath.compiler.XPathParser.error(XPathParser.java:610)
at org.apache.xpath.compiler.XPathParser.consumeExpected(XPathParser.java:528)
at org.apache.xpath.compiler.XPathParser.PrimaryExpr(XPathParser.java:1426)
at org.apache.xpath.compiler.XPathParser.FilterExpr(XPathParser.java:1345)
at org.apache.xpath.compiler.XPathParser.PathExpr(XPathParser.java:1278)
at org.apache.xpath.compiler.XPathParser.UnionExpr(XPathParser.java:1236)
at org.apache.xpath.compiler.XPathParser.UnaryExpr(XPathParser.java:1142)
at org.apache.xpath.compiler.XPathParser.MultiplicativeExpr(XPathParser.java:1063)
at org.apache.xpath.compiler.XPathParser.AdditiveExpr(XPathParser.java:1005)
at org.apache.xpath.compiler.XPathParser.RelationalExpr(XPathParser.java:930)
at org.apache.xpath.compiler.XPathParser.EqualityExpr(XPathParser.java:870)
at org.apache.xpath.compiler.XPathParser.AndExpr(XPathParser.java:834)
at org.apache.xpath.compiler.XPathParser.OrExpr(XPathParser.java:807)
at org.apache.xpath.compiler.XPathParser.Expr(XPathParser.java:790)
at org.apache.xpath.compiler.XPathParser.initXPath(XPathParser.java:129)
at org.apache.xpath.XPath.<init>(XPath.java:178)
at org.apache.xpath.XPath.<init>(XPath.java:266)
at org.apache.xpath.jaxp.XPathImpl.eval(XPathImpl.java:195)
at org.apache.xpath.jaxp.XPathImpl.evaluate(XPathImpl.java:281)
... 7 more


Steps to Reproduce



N/A


Root Cause



The root cause of this problem is because the upgrade script picked up the incorrect version of XPathImpl. The upgrade script needs XPathImpl that is bundled in Saxon library, but it was picking up Xalan libraries (xalan jar and serializer jar) instead as they have been put to the JVM's endorsed folder.

Resolution



The issue is resolved by making the following change to the PRPC operating system: temporarily remove the xalan jars from endorsed folder when doing the generate ddl step.

 
Suggest Edit

Published January 31, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

100% found this useful

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

We'd prefer it if you saw us at our best.

Pega Community has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice
Contact us