Discussion
Accenture Services Pvt Ltd
IN
Last activity: 6 Apr 2018 19:26 EDT
Issue while upgrading from PRPC6.3 to PRPC7.1.8
Hi,
We are upgrading our PRPC6.3 single schema environment to PRPC718 split schema. Steps we followed
1. We created one schema PRPCRULESTEMP71
2. Migrated rules from current 6.3 schema (PRPC63) to the temorary schema PRPCRULESTEMP71. It worked fine. No issue.
3. While running the rules upgrade on PRPCRULESTEMP71 we are getting the below error. Please find below the parameters for setupdatabase.proreties files also.
Setupdatabase.properties:
pega.jdbc.driver.jar=/data01/app/oracle/product/11.2.0/db_1/jdbc/lib/ojdbc6.jar
pega.jdbc.driver.class=oracle.jdbc.OracleDriver
pega.database.type=oracledate
pega.jdbc.url=jdbc:oracle:thin:@10.167.203.18:1521/prpcdb
pega.jdbc.username=prpcadmin
pega.jdbc.password=xxxxx
rules.schema.name=prpcrulestemp71
data.schema.name=
user.temp.dir=/data01/software/PRPC718/UpgradeTempDir/temp
ERROR:
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:367)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)
[java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)
[java] Caused by: com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "${current.system.name}!BATCH" not found
[java] From: (B8FEA8A8EF7412F434A8E08EEF8CBE3CD)
[java] at com.pega.pegarules.session.internal.authorization.SessionAuthorization.reset(SessionAuthorization.java:450)
[java] at com.pega.pegarules.session.internal.authorization.SessionAuthorization.<init>(SessionAuthorization.java:245)
[java] ... 58 more
[java]
[java] Exception in thread "PRPCUpgrade" java.lang.RuntimeException: Problem during method invocation (main)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:278)
[java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)
[java] Caused by: com.pega.pegarules.pub.context.PRSecurityException: Unable to construct authorization core due to authorization failure
Please suggest.
**Moderation Team has archived post**
This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.
Accenture
IN
Can you pleasse check in the exisiting 6.3 system, whether BATCH instance of class Data-Admin-Requestor exisit or not. check from Records -> Requestor Type.
and if it exist then what is the value of System Name against that BTACH requestor record.
if you have single record with system name pega or prpc
then create adittional record.
I mean keep 2 records for BATCH, one with system name prpc and another with pega.
and then start your upgrade again by taking the schema copy of the 6.3 enviornment where you did the above change.
Regards
Shankha
Accenture
IN
this issue also may cause if you missed to change one parameter (move.admin.table) while migrating the rules tables, on first migrate this should have value of true.
Regards
Shankha