Support Article
Error determining the mode of PRPC install from database
SA-1726
Summary
Admin is running DATA upgrade part of Update documentation on a split schema 7.1.5 environment using a database user with DBA role. Process fails with an error.
Error Messages
[java] 2014-09-22 15:53:43,229 [ main] [ ] [ ] (ta.internal.PRDataProviderImpl) ERROR - Error determining the mode of PRPC install from database.
[java] com.pega.pegarules.pub.database.NonexistentTableException: Database-TableWithNoColumns SAND_RULES716.pr4_base PegaRULES
[java] From: (unknown)
[java] at com.pega.pegarules.data.internal.access.TableInformationMapImpl.lookupColumnInfo(TableInformationMapImpl.java:664)
[java] at com.pega.pegarules.data.internal.access.TableInformationMapImpl.lookupTableInfo(TableInformationMapImpl.java:500)
[java] at com.pega.pegarules.data.internal.access.TableInformationMapImpl.get(TableInformationMapImpl.java:384)
[java] at com.pega.pegarules.data.internal.access.TableInformationMapImpl.getWithConnection(TableInformationMapImpl.java:352)
[java] at com.pega.pegarules.data.internal.PRDataProviderImpl.isMultiTenantEnvironment(PRDataProviderImpl.java:1146)
[java] at com.pega.pegarules.data.internal.dictionary.DictionaryImpl.<clinit>(DictionaryImpl.java:259)
[java] at com.pega.pegarules.data.internal.PRDataProviderImpl.getEngineDictionary(PRDataProviderImpl.java:661)
[java] at com.pega.pegarules.data.external.dictionary.EngineDictionary.<clinit>(EngineDictionary.java:71)
[java] at com.pega.pegarules.data.external.clipboard.ClipboardObjectImpl.getDictionary(ClipboardObjectImpl.java:380)
[java] at com.pega.pegarules.data.internal.clipboard.ClipboardPageBase.getDictionary(ClipboardPageBase.java:337)
[java] at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.getDictionary(ClipboardPageImpl.java:478)
[java] at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.putStringOverride(ClipboardPageImpl.java:2201)
[java] at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.putString(ClipboardPageImpl.java:2091)
[java] at com.pega.pegarules.data.internal.clipboard.ClipboardPageImpl.putString(ClipboardPageImpl.java:2087)
[java] at com.pega.pegarules.deploy.internal.util.MoveLog.<init>(MoveLog.java:93)
[java] at com.pega.pegarules.deploy.internal.archive.ImportableAbstract.<init>(ImportableAbstract.java:83)
[java] at com.pega.pegarules.deploy.internal.archive.ApplicationBundle.<init>(ApplicationBundle.java:406)
[java] at com.pega.pegarules.deploy.internal.PRDeployProviderImpl.getApplicationBundle(PRDeployProviderImpl.java:122)
[java] at com.pega.pegarules.deploy.external.util.Application.<init>(Application.java:152)
[java] at com.pega.pegarules.deploy.external.util.Application.<init>(Application.java:168)
[java] at com.pega.pegarules.deploy.external.util.Application.main(Application.java:402)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:39)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:25)
[java] at java.lang.reflect.Method.invoke(Method.java:597)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:419)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:460)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:509)
Steps to Reproduce
Follow split schema upgrade part of Update documentation for 7.1.6.
Root Cause
The root cause of this problem is a defect in Pegasystems’ code/rules. If you are running RULE or DATA upgrade part of Update documentation on a split schema 7.1.5 environment using deployment user with Admin/DBA role, the process fails if synonyms exist on RULE tables viz. pr4_base in schemas other than the one that is being upgraded. For example, if you are upgrading v71rulesupdate schema and have a PRPC 6.3 SP1 schema on the same Oracle server, create a synonym pr4_base for PRPC 6.3 SP1.pr4_base. Then run update/upgrade. Without the synonym, the same user is able to upgrade to 7.1.6 without issue.
Resolution
This issue is resolved through the following local change: Add private synonyms for all of the DATA and RULES schema objects of PRPC 7.1.6 to the Admin deployment user (viz. DBADMIN) who is running the upgrade and then follow the steps on Update Guide.
Published January 31, 2016 - 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.