Question

9
Replies
71
Views
Close popover
Perampalam Rajakulasingam (PerampalamR)
Newyorklife

Newyorklife
US
PerampalamR Member since 2016 3 posts
Newyorklife
Posted: January 25, 2018
Last activity: January 30, 2018
Closed

Popup error when upgrade pega6.2SPS2 single schema to 7.1.8 split scheme

Hi All,

We are in the process of upgrading our system from pega6.2SP2 to 7.18, we are using IUA tool.

We are getting error and terminate upgrade tool. find attached the error log.

[java] 2018-01-24 12:23:26,084 [ L184042] [ ] [ ] ( etier.impl.EngineStartup) ERROR - PegaRULES initialization failed. Server: L184042
[java] com.pega.pegarules.pub.context.InitializationFailedError: PRNodeImpl init failed

Caused by: com.pega.pegarules.pub.context.PRSecurityException: Unable to construct authorization core due to authorization failure

[java] Caused by: com.pega.pegarules.pub.context.InvalidConfigurationException: Data-Admin-Requestor instance "${current.system.name}!BATCH" not found
[java] From: (BAE39DDB229197C0699BEB52E836DC137)

Our configuration in IUA tool

pega.jdbc.driver.jar=C:\NYL\ProcessGateway\Pega 7.1.8 Binaries\db2jcc.jar
pega.jdbc.driver.class=com.ibm.db2.jcc.DB2Driver
pega.database.type=udb
pega.jdbc.url=jdbc:db2://aixqadb1:60052/pegaqap2:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;
pega.jdbc.username=db2qapg2
pega.jdbc.password=******
rules.schema.name=pegadpg (existing single schema)
data.schema.name=pegarpg (New schema)
user.temp.dir=
pega.zos.properties=
run.assembler=
import.assembled.classes=true
system.name=pega
production.level=2
multitenant.system=false
update.existing.applications=false
import.codeset.name=Customer
import.codeset.version=06-01-01

System Administration Upgrades
Moderation Team has archived post,
Close popover This thread is closed to future replies. Content and links will no longer be updated. If you have the same/similar Question, please write a new Question.