Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Question

 Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN
Avinash.Haridasu Member since 2014 306 posts
Morgan Stanley
Posted: May 5, 2016
Last activity: May 10, 2016
Posted: 5 May 2016 4:12 EDT
Last activity: 10 May 2016 3:53 EDT
Closed
Solved

How to determine the codeset version

Hi

I have a few questions on the codeset:

1. Where do we usually set the codeset

2. How to determine the codeset version the system is currenly running on

3. How do i know which codeset is related to which Pega Version

Regards

Avinash

To see attachments, please log in.
Pega Customer Service

Accepted Solution

Posted: 8 years ago
Posted: 10 May 2016 3:53 EDT
Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN

Our infra team has figured it out what the issue is...

While resetting the instance they have hardcoded the engineclasses codeset to 07-10-13 version in setupDatabase.properties file.

Now that they have reset the instance again by removing them.

To see attachments, please log in.
Posted: 8 years ago
Updated: 8 years ago
Posted: 5 May 2016 4:44 EDT
Updated: 5 May 2016 4:49 EDT
Harish Gunneri (Harish_Gunneri)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

Hi Avinash,

Usually while running Pega platform, you can find two codesets and with specific versions.

1. Pega-Engine codeset - Contains Pega shipped java classes.

2. Customer codeset - To import third party or customer specific jar files.

You can't set the Pega-Engine codeset, as it is unique for every shipped Pega platform version.

Eg:- 07-10-15 for Pega717, 07-10-17 for Pega718 & 07-10-19 for Pega719.

Customer codeset will be set to 06-01-01 by default and this you can update while importing any external jars into PRPC database.

You can determine pega-engine codeset version of the current system from the system startup logs, at prbootstrap configuration. (something like below, this is for 719 version).

============ PegaRULES Bootstrap Configuration ============

          Date: Wed May 04 07:55:41 IST 2016

  Java Version: Oracle Corporation 1.7.0_71

  Configuration: file:/C:/Pega-Instances/Pega-719/webapps/prweb/WEB-INF/classes/prbootstrap.properties

Pega-EngineCode: 07-10-19

    ASM Version: 554097615

      Database: Microsoft SQL Server 11.00.2100

        Driver: Microsoft JDBC Driver 4.0 for SQL Server 4.0.2206.100

Active CodeSets: pega-enginecode:07-10-19 at (latest patch)

Show More

Hi Avinash,

Usually while running Pega platform, you can find two codesets and with specific versions.

1. Pega-Engine codeset - Contains Pega shipped java classes.

2. Customer codeset - To import third party or customer specific jar files.

You can't set the Pega-Engine codeset, as it is unique for every shipped Pega platform version.

Eg:- 07-10-15 for Pega717, 07-10-17 for Pega718 & 07-10-19 for Pega719.

Customer codeset will be set to 06-01-01 by default and this you can update while importing any external jars into PRPC database.

You can determine pega-engine codeset version of the current system from the system startup logs, at prbootstrap configuration. (something like below, this is for 719 version).

============ PegaRULES Bootstrap Configuration ============

          Date: Wed May 04 07:55:41 IST 2016

  Java Version: Oracle Corporation 1.7.0_71

  Configuration: file:/C:/Pega-Instances/Pega-719/webapps/prweb/WEB-INF/classes/prbootstrap.properties

Pega-EngineCode: 07-10-19

    ASM Version: 554097615

      Database: Microsoft SQL Server 11.00.2100

        Driver: Microsoft JDBC Driver 4.0 for SQL Server 4.0.2206.100

Active CodeSets: pega-enginecode:07-10-19 at (latest patch)

                customer:06-01-01 at (latest patch)

=============== End Bootstrap Configuration ===============

You can also query pr_engineclasses Db table on your PRPC DB to check the pega-engine codeset versions, it can contain multiple pega-engine codeset versions if it's an upgraded system.


Hope this information helps, let me know if you have any specific queries.


BR//

Harish


Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 5 May 2016 5:11 EDT
Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN

Our tomcat server is not starting after an upgrade of our Horizontal. The platform remains same, we are on Pega 7.2 version.

Below is the error log from our server:

05-May-2016 01:58:34.002 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

05-May-2016 01:58:34.002 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

05-May-2016 01:58:34.002 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine classes schema: pegarules

05-May-2016 01:58:34.002 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Assembled classes schema: pegarules

05-May-2016 01:58:34.018 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings

05-May-2016 01:58:34.049 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Using latest detected engine version:(EngineCodeSetVersion= 07-10-23). To specify a different version, use the setting com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode in prbootstrap.properties.

05-May-2016 01:58:34.065 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:07-10-23

05-May-2016 01:58:34.096 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

Show More

Our tomcat server is not starting after an upgrade of our Horizontal. The platform remains same, we are on Pega 7.2 version.

Below is the error log from our server:

05-May-2016 01:58:34.002 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

05-May-2016 01:58:34.002 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

05-May-2016 01:58:34.002 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine classes schema: pegarules

05-May-2016 01:58:34.002 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Assembled classes schema: pegarules

05-May-2016 01:58:34.018 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings

05-May-2016 01:58:34.049 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Using latest detected engine version:(EngineCodeSetVersion= 07-10-23). To specify a different version, use the setting com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode in prbootstrap.properties.

05-May-2016 01:58:34.065 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:07-10-23

05-May-2016 01:58:34.096 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.112 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. ============================= Failed to bootstrap PegaRULES =============================

05-May-2016 01:58:34.112 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.127 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Could not load the java class 'com/pega/pegarules/internal/bootstrap/phase2/PRBootstrapImpl.class' from the database table 'pegarules.pr_engineclasses'

05-May-2016 01:58:34.127 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. This is usually due to an empty 'pegarules.pr_engineclasses' table, or possibly it does not contain the configured codeset version.

05-May-2016 01:58:34.127 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. In this run the prbootstrap.properties specified 'pega-enginecode:07-10-23', checking database...

05-May-2016 01:58:34.127 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.299 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. 'pegarules.pr_engineclasses' contains a total of 113128 classes, searching for available codesets...

05-May-2016 01:58:34.299 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.330 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.   Codeset                  |Version

05-May-2016 01:58:34.346 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. passbook                   |07-13-01

05-May-2016 01:58:34.346 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pega-enginecode            |07-10-13

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pega-enginecode            |07-10-23

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pegamkt                    |07-21-01

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pegamkt3rdparty            |01-01-01

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pegamkt_kpi_parser         |07-13-01

05-May-2016 01:58:34.377 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. progallconstraint          |07-01-01

05-May-2016 01:58:34.377 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. puma                       |06-02-01

05-May-2016 01:58:34.377 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pushnotification           |07-13-01

05-May-2016 01:58:34.377 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. segmentvisualisation       |07-13-01

05-May-2016 01:58:34.393 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.393 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Subsequent exceptions relating to class not being found are all related to this root cause...

05-May-2016 01:58:34.393 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Check to make sure the database is correctly configured and that the codeset version specified was correct and is present in that database.

05-May-2016 01:58:34.393 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. =========================================================================================

05-May-2016 01:58:34.393 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

C:\Tomcat8032\apache-tomcat-8.0.32\webapps\prweb\WEB-INF\lib\boot\prbootphase2.jar (The system cannot find the path specified)

Perhaps executing with a non-standard classpath (e.g. JUnit tests)?

05-May-2016 01:58:34.424 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap.

============ PegaRULES Bootstrap Configuration ============

           Date: Thu May 05 01:58:34 PDT 2016

   Java Version: Oracle Corporation 1.8.0_45

  Configuration: file:/C:/Tomcat8032/apache-tomcat-8.0.32/webapps/prweb/WEB-INF/classes/prbootstrap.properties

Pega-EngineCode: 07-10-23

       Database: DB2/LINUXX8664 SQL10055

         Driver: IBM Data Server Driver for JDBC and SQLJ 4.19.26

Unable to use given database configuration

Unable to locate classes on filesystem

=============== End Bootstrap Configuration ===============

Unable to load phase 2 bootstrap class: com.pega.pegarules.internal.bootstrap.phase2.PRBootstrapImpl

05-May-2016 01:58:34.455 SEVERE [localhost-startStop-1] 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(PRMiniLoader.java:388)

        at java.lang.ClassLoader.loadClass(ClassLoader.java:357)

        at com.pega.pegarules.internal.bootstrap.PRBootstrap.loadPhase2BootstrapClass(PRBootstrap.java:720)

        at com.pega.pegarules.internal.bootstrap.PRBootstrap.checkForStartup(PRBootstrap.java:662)

        at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:408)

        at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:223)

        at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:272)

        at com.pega.pegarules.internal.web.servlet.WebAppLifeCycleListenerBoot.contextInitialized(WebAppLifeCycleListenerBoot.java:83)

        at org.apache.catalina.core.StandardContext.listenerStart(StandardContext.java:4812)

        at org.apache.catalina.core.StandardContext.startInternal(StandardContext.java:5255)

        at org.apache.catalina.util.LifecycleBase.start(LifecycleBase.java:147)

        at org.apache.catalina.core.ContainerBase.addChildInternal(ContainerBase.java:725)

        at org.apache.catalina.core.ContainerBase.addChild(ContainerBase.java:701)

        at org.apache.catalina.core.StandardHost.addChild(StandardHost.java:717)

Any insight in this regard would be of great help..

Thanks


Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 5 May 2016 7:50 EDT
Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN

No, we have a clean install of our platform version 7.2

Yesterday we had updated our horizontal layer Pega Marketing to GA version and ever since the upgrade the appserver is not starting.

But, I don't think the horizontal upgrade has anything to do with the codeset version..

The log just says the below:

05-May-2016 01:58:34.018 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings

05-May-2016 01:58:34.049 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Using latest detected engine version:(EngineCodeSetVersion= 07-10-23). To specify a different version, use the setting com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode in prbootstrap.properties.

05-May-2016 01:58:34.065 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:07-10-23

05-May-2016 01:58:34.096 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.112 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. ============================= Failed to bootstrap PegaRULES =============================

05-May-2016 01:58:34.112 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

Show More

No, we have a clean install of our platform version 7.2

Yesterday we had updated our horizontal layer Pega Marketing to GA version and ever since the upgrade the appserver is not starting.

But, I don't think the horizontal upgrade has anything to do with the codeset version..

The log just says the below:

05-May-2016 01:58:34.018 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings

05-May-2016 01:58:34.049 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Using latest detected engine version:(EngineCodeSetVersion= 07-10-23). To specify a different version, use the setting com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode in prbootstrap.properties.

05-May-2016 01:58:34.065 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:07-10-23

05-May-2016 01:58:34.096 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.112 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. ============================= Failed to bootstrap PegaRULES =============================

05-May-2016 01:58:34.112 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.127 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Could not load the java class 'com/pega/pegarules/internal/bootstrap/phase2/PRBootstrapImpl.class' from the database table 'pegarules.pr_engineclasses'

05-May-2016 01:58:34.127 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. This is usually due to an empty 'pegarules.pr_engineclasses' table, or possibly it does not contain the configured codeset version.

05-May-2016 01:58:34.127 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. In this run the prbootstrap.properties specified 'pega-enginecode:07-10-23', checking database...

05-May-2016 01:58:34.127 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.299 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. 'pegarules.pr_engineclasses' contains a total of 113128 classes, searching for available codesets...

05-May-2016 01:58:34.299 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.330 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.   Codeset                  |Version

05-May-2016 01:58:34.346 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. passbook                   |07-13-01

05-May-2016 01:58:34.346 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pega-enginecode            |07-10-13

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pega-enginecode            |07-10-23

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pegamkt                    |07-21-01

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pegamkt3rdparty            |01-01-01

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pegamkt_kpi_parser         |07-13-01

05-May-2016 01:58:34.377 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. progallconstraint          |07-01-01

05-May-2016 01:58:34.377 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. puma                       |06-02-01

05-May-2016 01:58:34.377 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pushnotification           |07-13-01

05-May-2016 01:58:34.377 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. segmentvisualisation       |07-13-01

05-May-2016 01:58:34.393 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

05-May-2016 01:58:34.393 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Subsequent exceptions relating to class not being found are all related to this root cause...

05-May-2016 01:58:34.393 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Check to make sure the database is correctly configured and that the codeset version specified was correct and is present in that database.

05-May-2016 01:58:34.393 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader.

One difference i observed is that the pr_engineclasses table in the db does not have 07-10-23 code set version for the PRBootstrapImpl class but other machines which are on 7.2 have 07-10-23 against PRBootstrapImpl class.

select * from pegarules.pr_engineclasses where pzclass like '%PRBootstrapImpl%';


Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 5 May 2016 7:58 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

From the log we can see that it is finding the pr_engineclasses table and that there is a Pega-EngineCode:07-10-23 like there should be.  It just doesn't seem to find the PRBootstrapImpl class in that codeset in the table.

05-May-2016 01:58:34.127 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Could not load the java class 'com/pega/pegarules/internal/bootstrap/phase2/PRBootstrapImpl.class' from the database table 'pegarules.pr_engineclasses'

You mention that you upgraded the horizontals. What did you change?  I would look at your PegaRULES datasource in context.xml and make sure you have all of the connection properties set.  Your url should look like this

jdbc:db2://localhost:50000/dbName:fullyMaterializeLobData=true;fullyMaterializeInputStreams=true;progressiveStreaming=2;useJDBC4ColumnNameAndLabelSemantics=2;

To see attachments, please log in.
Posted: 8 years ago
Posted: 5 May 2016 8:05 EDT
Celeste Dufresne (CelesteDufresne_GCS)
PEGA
Fellow, Technical Support, Cloud Service
Pegasystems Inc.
US

I missed the note where you said this was a fresh install.  If this is a fresh install you should only have one pega-enginecode codeset version but it looks like you have 2.  We need to look at where this 07-10-13 codeset version came from.  Since you have already opened an SR it will be worked under that.

05-May-2016 01:58:34.346 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pega-enginecode            |07-10-13

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pega-enginecode            |07-10-23

To see attachments, please log in.
Posted: 8 years ago
Updated: 8 years ago
Posted: 9 May 2016 4:30 EDT
Updated: 9 May 2016 4:34 EDT
Harish Gunneri (Harish_Gunneri)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

Hi Avinash,

PRBootstrap class is responsible for querying the engine classes DB table to get the list of pega-engine codesets from the specified datasource.

This class gets the list of Pega-engine codesets and determines the highest code-set.

The above process can be overridden through prbootstrap.properties file, you can set the respective pega-engine codeset value based on your version. This is only used incase of any discrepancies on upgraded systems and not recommended for new installations.

##########################################################################

#  Active CodeSets

##########################################################################

# Code sets (other than Pega-EngineCode) are now specified via Data-Admin-System-Settings, but you can override database settings with settings from the file.

# For Pega-EngineCode latest code set version available in the system will be used, but you can override this behavior with settings from the file.

#Example:

com.pega.pegarules.bootstrap.codeset.version.Pega-EngineCode=07-10-23 (this value represents 7.2 Pega-engine codeset)

#<code set version> should be of format dd-dd-dd, d for digit

To see attachments, please log in.
Posted: 8 years ago
Posted: 9 May 2016 5:01 EDT
Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN

Thanks Harish.

One of our pega instance is on 7.2 version.. However, the engine codeset version which it picks up is 07-10-13 and to my surprise the records in pr_engineclasses also does not have 07-10-23 codeset version records.

This is a new instance and was not upgraded from any earlier version.

Not sure from where the 13 version was getting picked up from.

Any thoughts?

To see attachments, please log in.
Posted: 8 years ago
Posted: 9 May 2016 5:09 EDT
Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN

Thanks Habeeb.

I think you mean select pzcodesetversion from pr_engineclasses;

The above query returns only the version 07-10-13 for pega-enginecode codebase which is really concerning.

The version is supposed to be 07-10-23

To see attachments, please log in.
Posted: 8 years ago
Posted: 9 May 2016 5:28 EDT
Habeeb Baig (BaigHabeeb)
Virtusa IT Consulting
Lead Decisioning Architect
Virtusa IT Consulting
AE

 

Can you give a try for below query?

 

select pzcodesetversion from pr_engineclasses where pzcodesetversion='07-10-23'

 

I think below entry is being returned from database

 

05-May-2016 01:58:34.362 SEVERE [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. pega-enginecode            |07-10-23

 

 

Also please check prbootstrap.properties file in below location in tomcat

 

C:\apache-tomcat-7.0.32\webapps\prweb\WEB-INF\classes

 

From the error logs I believe you have single schema configuration?

To see attachments, please log in.
Posted: 8 years ago
Posted: 9 May 2016 5:33 EDT
Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN

The query returns just the below 6 rows.

Capture.PNG

We are on split schema and the bootstrap.properties file is the same as given by platform.. We have not modified its content.

To see attachments, please log in.
Posted: 8 years ago
Posted: 9 May 2016 9:17 EDT
Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN

When i deployed the 7.2 version of prweb i get the below exception.. I had reverted to my existing version.

09-May-2016 04:33:01.969 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Loading bootstrap properties from /prbootstrap.properties

09-May-2016 04:33:01.984 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI. Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup

09-May-2016 04:33:02.000 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI. Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup

09-May-2016 04:33:02.000 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

09-May-2016 04:33:02.000 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

09-May-2016 04:33:02.000 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Bootstrap datatables schema: null

09-May-2016 04:33:03.969 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Archive version [0]

09-May-2016 04:33:03.969 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine schema defined in allclasses: null

09-May-2016 04:33:03.969 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

Show More

When i deployed the 7.2 version of prweb i get the below exception.. I had reverted to my existing version.

09-May-2016 04:33:01.969 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Loading bootstrap properties from /prbootstrap.properties

09-May-2016 04:33:01.984 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI. Could not find java:comp/env/prbootstrap/ in the local JNDI context, skipping prconfig setting lookup

09-May-2016 04:33:02.000 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI. Could not find prbootstrap in the local JNDI context, skipping prconfig setting lookup

09-May-2016 04:33:02.000 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

09-May-2016 04:33:02.000 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

09-May-2016 04:33:02.000 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Bootstrap datatables schema: null

09-May-2016 04:33:03.969 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Archive version [0]

09-May-2016 04:33:03.969 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine schema defined in allclasses: null

09-May-2016 04:33:03.969 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

09-May-2016 04:33:03.984 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.SettingReaderJNDI.

09-May-2016 04:33:03.984 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Engine classes schema: null

09-May-2016 04:33:03.984 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. Assembled classes schema: null

09-May-2016 04:33:03.984 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. prbootstrap.properties merged with prbootstrap entries in Data-Admin-System-Settings

09-May-2016 04:33:04.063 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap. PRBootstrap.calculateEngineCodeVersionFromDB() - unable to calculate codeset version from database: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=PEGADATA.PR_ENGINECLASSES, DRIVER=4.19.26

09-May-2016 04:33:04.078 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. Will load phase 2 bootstrap from Pega-EngineCode:

09-May-2016 04:33:04.109 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRMiniLoader. PRMiniLoader - unable to load classes from the database: DB2 SQL Error: SQLCODE=-204, SQLSTATE=42704, SQLERRMC=PEGADATA.PR_ENGINECLASSES, DRIVER=4.19.26

09-May-2016 04:33:04.172 19830421 [localhost-startStop-1] com.pega.pegarules.internal.bootstrap.PRBootstrap.

============ PegaRULES Bootstrap Configuration ============

           Date: Mon May 09 04:33:04 PDT 2016

   Java Version: Oracle Corporation 1.8.0_45

  Configuration: file:/C:/Tomcat8032/apache-tomcat-8.0.32/webapps/prweb/WEB-INF/classes/prbootstrap.properties

Pega-EngineCode:

       Database: DB2/LINUXX8664 SQL10055

         Driver: IBM Data Server Driver for JDBC and SQLJ 4.19.26

Unable to use given database configuration

Unable to locate classes on filesystem

=============== End Bootstrap Configuration ===============


Show Less
To see attachments, please log in.
Posted: 8 years ago
Posted: 9 May 2016 9:22 EDT
Veera Gangababu Gollapalli (Gangababu)
PEGA
Principal Technical Solutions Engineer
PEG
IN

It looks it's not able to find the schema name. Can you give the schema name and try?

com.pega.pegarules.internal.bootstrap.PRBootstrapDataSource. Bootstrap datatables schema: null

Are you using single schema or split schema database configuration?

To see attachments, please log in.
Posted: 8 years ago
Posted: 9 May 2016 6:05 EDT
Harish Gunneri (Harish_Gunneri)
PEGA
Senior Principal Engineer, Technical Support
Pegasystems Inc.
US

Hi Avinash,

I feel 7.2 rule-base installation was somehow got messed up. Ideally we must be seeing more than 10k+ records in pr_engineclasses under 07-10-23 codeset for a valid 7.2 system.

Either it has to be an installation issue or somehow your data source is pointing to a wrong one. It's better to have this investigated on the SR.

To see attachments, please log in.

Accepted Solution

Posted: 8 years ago
Posted: 10 May 2016 3:53 EDT
Avinash Haridasu (Avinash.Haridasu)
Morgan Stanley

Morgan Stanley
IN

Our infra team has figured it out what the issue is...

While resetting the instance they have hardcoded the engineclasses codeset to 07-10-13 version in setupDatabase.properties file.

Now that they have reset the instance again by removing them.

To see attachments, please log in.

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice