Question
Newyorklife
US
Last activity: 30 Jan 2018 16:44 EST
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
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
Newyorklife
US
Sorry for typo mistake in the title. the version is pega 6.2SP2.
please let us know if you all need any more information on this.
please help to resolve this problem.
Thanks in advance
Pegasystems Inc.
IN
Hi,
Can you check the system name in pega and in database. See if there is a mismatch
Refer the below link for more details
https://collaborate.pega.com/discussion/data-admin-requestor-instance-sdev718batch-not-found-52-718-upgrade
https://community.pega.com/support/support-articles/pegarules-initialization-fails-error-message-log
Thank You
Newyorklife
US
Thanks Shekhar for the reply.
in which table do I need to check in the DB. where in Pega do I need to check to verify the mismatch.
This is working for single schema, so I do not think this is related to system name.
any other idea
Thanks
Regards
Kulam
Techmahindra
IN
Hi Perampalam,
This is one common issue we have seen in the past. Have you tried changing the system name to prpc in the prconfig.xml and give a try.
Regards,
Shanthini Charles
Newyorklife
US
Hi Shanthini,
Thanks for the response,
We are doing only rule base upload to the DB only. JVMs are already stopped, how would read from prconfig.xml .
In prconfig.xml, only DB connection details are available. no other entries.
Also it is working for single schema upgrade without any issues.
Any idea ??
Regards
Perampalam
Pegasystems Inc.
US
rules.schema.name=pegadpg (existing single schema)
data.schema.name=pegarpg (New schema)
This is not correct. The existing single schema will become the data schema in the new environment. You will have a new rules schema, migrate the rules table to it, upgrade the rules schema, and then upgrade the data schema.
Newyorklife
US
Thanks for your comments.
migrate the rules table to it means, in the new rule schema do I need to export all rule table from the existing schema.
I am doing IUA tool for the upgrade. do I need to do any other script prior to upgrade or DBA just export the tables.
please advice
thanks
Pegasystems Inc.
US
https://docs-previous.pega.com/pega-731-platform-upgrade-guide
See the section "Upgrading from a single-schema to split-schema configuration" in the guide on how to do a single to split schema upgrade. It is not a one step process using the IUA. You would use the migrate script to migrate the rules tables to new rules schema, run the upgrade of the rules schema, run migrate script again to create rules schema objects (assuming you are using one database for upgrade), and then run the data schema upgrade. The other option would be to upgrade to a single schema and then use the migrate script afterwards to split it. With the single to split approach your existing 6.x system can be in use up until you get to the data schema step. Since the upgrade of the rules schema is the longest part of the upgrade you would minimize down time. For the single schema upgrade and then split your 6.x system needs to be down as soon as you start the upgrade.