NagarajuB0579 Member since 2014 12 posts
Posted: January 17, 2017
Last activity: April 6, 2018

Upgrade Estimator tool not working for Pega 6.1SP2

Hi, I'm trying to run the upgrade estimator tool, but it does not seem to be working. I'm getting below error

The keys of EFFORTESTIMATES table is not as per the structure of the given class in the pegaupgradeEE rulest. Attached the screenshot too.
ECS-PreUpg-Effort-Estimator PegaUpgradeEE

Steps to Reproduce
See PDN article:

Installing the tool
Create the EFFORTESTIMATES table if you do not have database administrator privileges. Skip this step if you are running PRPC 6.2 or earlier versions.
Extract the contents of the file and open the Scripts folder.
Run the appropriate script for your database. For example, run MSSQL.sql if you are using a Microsoft SQL Server database.
You must have PRPC administrator privileges.

Perform the following steps to install the tool.

Download the file.
Extract the contents to your local folder.
Open the folder that corresponds to your PRPC version. This folder might contain a .zip or .jar file.
Import the file as an administrator. Ensure that you select the Check Compile Libraries check box when you import the RAP file. For more information about how to import RAPs, see the PRPC Online Help.
Open the application that you want to upgrade.
Add the estimator tool ruleset to the application rule:
Open the Profile menu, and click Application. For more information about how to access the Profile menu, see the PRPC Online Help.
In the application rule form, add the PegaUpgradeEE:<Version> ruleset to the top of the application ruleset list.
Add UpgradeEstimator portal as the secondary portal:
Open the Profile menu, and click Access Group > Settings.
In the Secondary Portal Layouts area, add the UpgradeEstimator portal as the secondary portal.
Customizing the tool
The upgrade estimator tool calculates the total effort based on various factors such as environment complexity, rule customizations, deprecated features, average architect’s productivity, risk factors, and so on. These factors can vary from case to case. You can calibrate the tool before running it to arrive at a more accurate estimate. To update the tool’s decision logic:

To customize the tool decision logic, perform the following steps:
Search for and open the tyGetEfforts decision tree.
Update the effort required to perform each upgrade task, based on your judgment and the complexity of your environment.
Save the decision tree to a higher ruleset.

Calculating the required effort
Open the upgrade estimator portal:
If you are running PRPC 5.x, click File > Open > Portal > UpgradeEstimator.
If you are running PRPC 6.x, click Run > Open Portal > Upgrade Estimator.
If you are running Pega 7.x, click Launch > Upgrade Estimator.

Ensure that the application that you want to update contains the PegaUpgradeEE ruleset and that the access group has SysAdmin privileges.
Optional: Change the selected application and version.

Select an application from the Select Application Name drop-down list. By default, the current application, its version, and access groups are selected.
Click Switch Application. You cannot proceed if the selected application does not contain the PegaUpgradeEE ruleset or the access group does not have SysAdmin privileges.
For versions earlier than PRPC 6.2, you must click Refresh.
Click Select Rulesets to choose the rulesets that need to be considered for the upgrade. By default, all the rulesets are considered for the estimate.
Optional: Select your industry solutions:
Click Select Industry Solutions.
Select the source and target framework application versions, and click Submit.
Click Calculate Efforts. The tool scans the entire application to analyze the rules and the effort required. A message displays the status on the top right of the screen.
Error Message
01:58:15,214 [j2ee14_ws,maxpri=10]] (exity.Rule_HTML_Section.Action) INFO Jonathan@nncc - Error in loop in activity tyComputeRuleComplexity of section
01:58:15,214 [j2ee14_ws,maxpri=10]] ( internal.access.DatabaseImpl) ERROR Jonathan@nncc - Cannot open the requested instance '': class or class group "" does not exist.
01:58:15,214 [j2ee14_ws,maxpri=10]] (exity.Rule_HTML_Section.Action) ERROR Jonathan@nncc - Error in Obj-Open-By-Handle Class does not exist
From: (BB00143A3268C367F3FE1AFEBEB682B01)
at com.pegarules.generated.activity.ra_action_tycomputerulecomplexity_ef0c61c73669ab15394077c827be7e16.step3_2_circum0(
at com.pegarules.generated.activity.ra_action_tycomputerulecomplexity_ef0c61c73669ab15394077c827be7e16.step3_0_circum0(
at com.pegarules.generated.activity.ra_action_tycomputerulecomplexity_ef0c61c73669ab15394077c827be7e16.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pegarules.generated.activity.ra_action_txcomputerulecomplexity_8176838e6a1ac00742607541accd34cc.step4_3_circum0(
at com.pegarules.generated.activity.ra_action_txcomputerulecomplexity_8176838e6a1ac00742607541accd34cc.step4_0_circum0(
at com.pegarules.generated.activity.ra_action_txcomputerulecomplexity_8176838e6a1ac00742607541accd34cc.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pegarules.generated.activity.ra_action_txestimateallruleeffort_42fdcf6cf89e7db1152dd0c9fc9b409a.step19_circum0(
at com.pegarules.generated.activity.ra_action_txestimateallruleeffort_42fdcf6cf89e7db1152dd0c9fc9b409a

05:18:07,189 [j2ee14_ws,maxpri=10]] (mateAllRuleEffort.Rule_.Action) INFO nagaraju@nncc - Effort Estimator Activity has Started Running for application : NNCorporate
05:18:22,198 [j2ee14_ws,maxpri=10]] (uteRuleComplexity.Rule_.Action) INFO nagaraju@nncc - Effort Estimator has started for Rule Type : Rule-PortalSkin
05:18:22,328 [j2ee14_ws,maxpri=10]] ( internal.access.DatabaseImpl) ERROR nagaraju@nncc - Cannot open the requested instance '': class or class group "" does not exist.
05:18:22,329 [j2ee14_ws,maxpri=10]] (plexity.Rule_PortalSkin.Action) ERROR nagaraju@nncc - Error in Obj-Open-By-Handle Class does not exist
From: (BF295EBD1593BE6D3189E3CC69E4D192D)
at com.pegarules.generated.activity.ra_action_tycomputerulecomplexity_25d1d0251a1ea119ed18a2d3b49d859c.step6_2_circum0(
at com.pegarules.generated.activity.ra_action_tycomputerulecomplexity_25d1d0251a1ea119ed18a2d3b49d859c.step6_0_circum0(
at com.pegarules.generated.activity.ra_action_tycomputerulecomplexity_25d1d0251a1ea119ed18a2d3b49d859c.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pegarules.generated.activity.ra_action_txcomputerulecomplexity_2df358d240ca92fab8710ca82e8f53e5.step4_3_circum0(
at com.pegarules.generated.activity.ra_action_txcomputerulecomplexity_2df358d240ca92fab8710ca82e8f53e5.step4_0_circum0(
at com.pegarules.generated.activity.ra_action_txcomputerulecomplexity_2df358d240ca92fab8710ca82e8f53e5.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pegarules.generated.activity.ra_action_txestimateallruleeffort_42fdcf6cf89e7db1152dd0c9fc9b409a.step19_circum0(
at com.pegarules.generated.activity.ra_action_txestimateallruleeffort_42fdcf6cf89e7db1152dd0c9fc9b409a.perform(
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivitiesAlt(
at com.pega.pegarules.session.internal.mgmt.base.ThreadRunner.runActivities(
at com.pega.pegarules.session.internal.mgmt.PRThreadImpl.runActivities(
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.executeBatchTask(
at com.pega.pegarules.session.internal.async.agent.QueueProcessor.execute(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
at com.pega.pegarules.session.internal.PRSessionProviderImpl.doWithRequestorLocked(
at com.pega.pegarules.session.internal.async.Agent.runBatchTask(
at com.pega.pegarules.session.internal.engineinterface.etier.impl.AsyncServant.processAsyncTask(

**Moderation Team has archived post**

This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

Low-Code App Development Upgrades
Moderation Team has archived post
Share this page LinkedIn