Support Article
Migration of rules tables fail during upgrade to split schema
SA-11460
Summary
While upgrading from PRPC 6.2 SP2 to Pega 7.1.8, single to split on two databases. The upgrade fails during migration.
Error Messages
[java] Jun 17, 2015 10:09:46 PM com.pega.pegarules.install.SQLLoader writeMessage
[java] INFO: CREATE TABLE RULE_TEMP.PR_DATA_PRODUCTS
[java] Jun 17, 2015 10:09:47 PM com.pega.pegarules.install.SQLLoader writeException
[java] WARNING: Failed to execute SQL in file oracledate02960.sql
[java] java.sql.SQLSyntaxErrorException: ORA-00955: name is already used by an existing object
[java]
[java] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:440)
[java] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
[java] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:837)
[java] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:445)
[java] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:191)
[java] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:523)
[java] at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
[java] at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:999)
[java] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1315)
[java] at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1890)
[java] at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1855)
[java] at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:304)
[java] at com.pega.pegarules.install.SQLLoader.main(SQLLoader.java:266)
[java] Jun 17, 2015 10:09:47 PM com.pega.pegarules.install.SQLLoader writeMessage
Steps to Reproduce
Run migration script.
Root Cause
The flags in the migrateSystem.properties file are not setup correctly for the migration of the rules tables to the temporary rules schema. The pega.move.admin.table should be set to true and the pega.rules.objects.generate and pega.rules.objects.apply should be set to true. All of the other flags are correctly set to true.
pega.move.admin.table=false
pega.clone.generate.xml=true
pega.clone.create.ddl=true
pega.clone.apply.ddl=true
pega.bulkmover.unload.db=true
pega.bulkmover.load.db=true
pega.rules.objects.generate=true
pega.rules.objects.apply=true
Resolution
This issue is resolved by making the following change to the operating environment: Clean the temporary rules schema and then run the migration script again with the correct property flag settings:
pega.move.admin.table=true
pega.clone.generate.xml=true
pega.clone.create.ddl=true
pega.clone.apply.ddl=true
pega.bulkmover.unload.db=true
pega.bulkmover.load.db=true
pega.rules.objects.generate=false
pega.rules.objects.apply=false
Published July 27, 2015 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.