Support Article
Error occurs when downgrading using Reversal script
SA-107541
Summary
Error occurs when downgrading Pega Platform 8.3.2 to Pega Platform 8.2.5 using the Reversal script (reverse.sh).
User is utilizing MSSQLDB and the application server is JBoss EAP 7X.
Error Messages
org.xml.sax.SAXParseException; lineNumber: 14542; columnNumber: 21; cvc-complex-type.4: Attribute 'name' must appear on element 'pega:viewGroup'.
[java] at org.apache.xerces.util.ErrorHandlerWrapper.createSAXParseException(Unknown Source)
[java] at org.apache.xerces.util.ErrorHandlerWrapper.error(Unknown Source)
[java] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
[java] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
[java] at org.apache.xerces.impl.XMLErrorReporter.reportError(Unknown Source)
[java] at org.apache.xerces.impl.xs.XMLSchemaValidator$XSIErrorReporter.reportError(Unknown Source)
[java] at org.apache.xerces.impl.xs.XMLSchemaValidator.reportSchemaError(Unknown Source)
[java] at org.apache.xerces.impl.xs.XMLSchemaValidator.addDefaultAttributes(Unknown Source)
[java] at org.apache.xerces.impl.xs.XMLSchemaValidator.handleStartElement(Unknown Source)
[java] at org.apache.xerces.impl.xs.XMLSchemaValidator.startElement(Unknown Source)
[java] at org.apache.xerces.xinclude.XIncludeHandler.startElement(Unknown Source)
[java] at org.apache.xerces.impl.XMLNSDocumentScannerImpl.scanStartElement(Unknown Source)
[java] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl$FragmentContentDispatcher.dispatch(Unknown Source)
[java] at org.apache.xerces.impl.XMLDocumentFragmentScannerImpl.scanDocument(Unknown Source)
[java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
[java] at org.apache.xerces.parsers.XML11Configuration.parse(Unknown Source)
[java] at org.apache.xerces.parsers.XMLParser.parse(Unknown Source)
[java] at org.apache.xerces.parsers.DOMParser.parse(Unknown Source)
[java] at org.apache.xerces.jaxp.DocumentBuilderImpl.parse(Unknown Source)
[java] at javax.xml.parsers.DocumentBuilder.parse(DocumentBuilder.java:121)
[java] at com.pega.pegarules.data.ddl.SchemaManager.createDomDocumentFromXmlInputStream(SchemaManager.java:258)
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:430)
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:250)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.getCustomSchemaManager(SchemaGenerator.java:2057)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.validateSchemaFile(SchemaGenerator.java:1964)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.getReversalSchemaManager(SchemaGenerator.java:1923)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.handleReverseAction(SchemaGenerator.java:1626)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1548)
Steps to Reproduce
Perform a single schema Out-Of-Place upgrade from Pega Platform 8.2.5 to Pega Platform 8.3.2.
Root Cause
The limitation of the Reverse Upgrade is that the single schema upgrade does not support Reverse Upgrade.
Resolution
Here’s the explanation for the reported behavior:
The limitations of the Reverse Upgrade are:
- In-place upgrades
- Single-schema systems
- Multi-tenancy systems
- Multi-hop upgrades:
For example,
The user can,
- Upgrade from Pega Platform 7.2 to Pega Platform 8.1.
- Reverse the upgrade to return Pega Platform 7.2.
The user cannot:
- Upgrade from Pega Platform 7.2 to Pega Platform 7.4 (first hop).
- Upgrade again from Pega Platform 7.4 to Pega Platform 8.1 (second hop).
- Reverse the upgrade to Pega Platform 7.2.
The user must perform the Out-of-Place upgrade.
Published July 8, 2020 - Updated December 2, 2021
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.