PRBootstrap: Error initializing PRAppLoader

Hi All,

We have performed an out of place upgrade from version 8.1.2 to 8.3.1. After the upgrade and when we try to bring up the server we get the following error:

[8-11-19 12:46:21:752 CET] 00000057 PRBootstrap W com.pega.pegarules.internal.bootstrap.PRBootstrap PRBootstrap.calculateEngineCodeVersionFromDB() - unable to calculate codeset version from database: ORA-00942: Tabel of view bestaat niet.

[8-11-19 12:46:21:754 CET] 00000057 PRMiniLoader I com.pega.pegarules.internal.bootstrap.PRMiniLoader Will load phase 2 bootstrap from Pega-EngineCode:
[8-11-19 12:46:21:757 CET] 00000057 PRMiniLoader W com.pega.pegarules.internal.bootstrap.PRMiniLoader PRMiniLoader - unable to load classes from the database: ORA-00942: Tabel of view bestaat niet.

[8-11-19 12:46:21:759 CET] 00000057 SystemOut O /opt/was85/as/profiles/nodeo01/installedApps/cello01/rbg-prpc-intranet.ear.ear/APP-INF/lib/boot/prbootphase2.jar (No such file or directory)
[8-11-19 12:46:21:759 CET] 00000057 SystemOut O Perhaps executing with a non-standard classpath (e.g. JUnit tests)?
[8-11-19 12:46:21:761 CET] 00000057 PRBootstrap I com.pega.pegarules.internal.bootstrap.PRBootstrap
============ PegaRULES Bootstrap Configuration ============
Date: Fri Nov 08 12:46:21 CET 2019
Java Version: IBM Corporation 1.8.0_191
Configuration: wsjar:file:/opt/was85/as/profiles/nodeo01/installedApps/cello01/rbg-prpc-intranet.ear.ear/APP-INF/lib/prresources.jar!/
Database: Oracle Oracle Database 12c Enterprise Edition Release - 64bit Production
Driver: Oracle JDBC driver

(!) Unable to use given database configuration
(!) Unable to locate classes on filesystem
=============== End Bootstrap Configuration ===============

[8-11-19 12:46:21:761 CET] 00000057 PRBootstrap E com.pega.pegarules.internal.bootstrap.PRBootstrap Error initializing PRAppLoader
java.lang.ClassNotFoundException: com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl
at com.pega.pegarules.internal.bootstrap.PRMiniLoader.loadClass(

We have verified the DB connections and they all work fine.

Also if we point to old rules schema and bring up the server, it works. So pointers from any one on how to fix this issue.


Keep up to date on this post and subscribe to comments

November 12, 2019 - 7:46am

I think that your DB synonyms have to be updated to point to the new schema also.
Since you've got 2 rules schema, but only one synonym per table, you need to update synonyms to point to new schema. Above, it's not finding DB table info, it's like tables are not there.

November 13, 2019 - 1:18am
Response to Anthony_Gourtay

You could also check the procedure of the new rules schema, since schema name is in it.

November 12, 2019 - 10:50am

The tables which get copied with the out-of-place upgrade (migrate script) depends on what options you selected with the file.

But did you also check the permissions by: -

1. Log into SQL directly with your Data user

2. Verify that you have access to the Rule schema: 


select * from pegarules.pr4_base

where rownum=1



November 12, 2019 - 11:54pm

Can you check the configuration file? Did you deploy the new prweb ?


November 18, 2019 - 6:44am

Hi All,

The issue was related to available grants on the new rules schema. The new rules schema didn't had required grants to the data schema. Once we fixed the issue manually the issue was resolved.