Error initializing PRA ppLoader
Hi Team
After pega upgrade 8.3.1 to 8.6.2 i am getting below warning message in the logs
<com.pega.pegarules.internal.bootstrap.PRMiniLoader> <BEA-000000> <PRMiniLoader - unab le to load classes from the database: ORA-00942: table or view does not exist
Unable to load phase 2 bootstrap class: com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl <Feb 7, 2022 12:53:26,757 PM AST> <Error> <com.pega.pegarules.internal.bootstrap.PRBootstrap> <BEA-000000> <Error initializing PRA ppLoader
What will be cause
1) Datasource is configured correctly
2) new prweb.war file deployed
3) Database connection is successful.
Accepted Solution
Updated: 29 Mar 2022 7:44 EDT
Pegasystems Inc.
GB
The errors during startup look like the application can't connect to the database.
--> Can you clarify what update documentation you followed?
--> Can you confirm that you applied the required privileges for the database user which is configured in the data source?
The error extract is a known issue in Pega if the external database is on a different platform than a PegaRULES - the operations will fail due to hard code optimization changes . To resolve this, the helper class has been enhanced to work with external databases by passing the database name as a parameter so it will properly calculate the query based on the type of target. An error in the name of the class has also been corrected, and is now available as PerformanceHelper rather than the previous "PerformaneHelper".
The below link explain the same and solution for the same.
Solution:
Apply the latest Pega 8.6 Patch Release then either enable optimization:
Try below things:
1) by default in 8.4.4 optimization is enabled , grant below privileges.
grant select on sys.v_$parameter to <externalUser>
grant alter session to <externalUser>
The errors during startup look like the application can't connect to the database.
--> Can you clarify what update documentation you followed?
--> Can you confirm that you applied the required privileges for the database user which is configured in the data source?
The error extract is a known issue in Pega if the external database is on a different platform than a PegaRULES - the operations will fail due to hard code optimization changes . To resolve this, the helper class has been enhanced to work with external databases by passing the database name as a parameter so it will properly calculate the query based on the type of target. An error in the name of the class has also been corrected, and is now available as PerformanceHelper rather than the previous "PerformaneHelper".
The below link explain the same and solution for the same.
Solution:
Apply the latest Pega 8.6 Patch Release then either enable optimization:
Try below things:
1) by default in 8.4.4 optimization is enabled , grant below privileges.
grant select on sys.v_$parameter to <externalUser>
grant alter session to <externalUser>
<externalUser> is the database username that is configured to connect to the external Oracle database.
The SELECT permission on the v$parameter table gives the Pega Platform information about Oracle database’s optimizer_mode, which is temporarily altered for the current Pega session for running the metadata query.
If the application is adequately performant and if the Oracle DBA chooses not to grant the database privileges, the optimization can be disabled by setting the DSS value for allowOptimization to true.
Ruleset: Pega-Engine Name: prconfig/database/oracle/allowOptimization/default Value: true
The default for 'database/oracle/allowOptimization' should be set to false in earlier patches and "true" for the 8.6 releases
Also, what changes did you make in the web.xml and weblogic.xml? Those should have been isolated to the just new servlet definitions and not something that would affect the connection to the database.
Did you test the JDBC datasource connectivity in websphere console?
You may need to log a support incident for this if you need someone to look into the log file and prconfig.xml files.