Question
AI4Process
GB
Last activity: 25 Apr 2018 7:36 EDT
Pega 7.3.1 Update - Failed to find current installed version
We are executing the update scripts for Pega 7.1.5 to Pega 7.3.1.We have encountered below build failed issue -
[pega:getupgradefromversion] Failed to find current installed version of PRPC.
Any suggestion Please.
Note -
1. We have split schema configuration.We are doing in-place update for both Rules and Data schema. And we have faced this issue while executing the update.sh script for Rule schema.
2. In PDN, I have found few resolutions, but none of the are applicable for our case -
We are using deployment user which has access to all the tables in both "Rules" and "Data" schema.
we are facing issue while updating "Rules" schema.
3. The deployment user has all the required privileges and roles as defined in Upgrade document.
We are executing the update scripts for Pega 7.1.5 to Pega 7.3.1.We have encountered below build failed issue -
[pega:getupgradefromversion] Failed to find current installed version of PRPC.
Any suggestion Please.
Note -
1. We have split schema configuration.We are doing in-place update for both Rules and Data schema. And we have faced this issue while executing the update.sh script for Rule schema.
2. In PDN, I have found few resolutions, but none of the are applicable for our case -
We are using deployment user which has access to all the tables in both "Rules" and "Data" schema.
we are facing issue while updating "Rules" schema.
3. The deployment user has all the required privileges and roles as defined in Upgrade document.
4. We have updated the log level in deploylogging.properties from INFO to CONFIG, but that did not produce any additional information in log file.
Please see the log file.
Accepted Solution
AI4Process
GB
This particular issue is resolved. previously we unzipped the media file in windows machine and the transferred it to Linux box and tried to execute. But, later we copied the entire media file to Linux box and unzip it there.And then execute the script and found the issue is resolved.
OCBC Bank
SG
Hi,
Can you run below query by logging in as the user which you were using for updating your Pega
SELECT DISTINCT pzcodesetversion, pzcodeset, count(pzcodesetversion) FROM <RULES_SCHEMA_NAME>.PR_ENGINECLASSES GROUP BY pzcodesetversion, pzcodeset
Also please share the permissions you have granted to the user.
Try below steps to trace the DB related issues while performing update.
1. Use the ojdbc6_g.jar version of the JDBC driver. This jar will work with jdbc tracing.
In setupDatabase.properties set pega.jdbc.driver.jar=location of ojdbc6_g.jar
2. Create a file JDBCConfig.properties file to set the level of trace that you want.
.level=SEVERE
oracle.level=FINE
oracle.jdbc.level=FINE
oracle.jdbc.handlers=java.util.logging.FileHandler
java.util.logging.FileHandler.level=FINE
java.util.logging.FileHandler.pattern=jdbcTraceUpgrade.log
java.util.logging.FileHandler.count=20
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.FileHandler.append=true
Hi,
Can you run below query by logging in as the user which you were using for updating your Pega
SELECT DISTINCT pzcodesetversion, pzcodeset, count(pzcodesetversion) FROM <RULES_SCHEMA_NAME>.PR_ENGINECLASSES GROUP BY pzcodesetversion, pzcodeset
Also please share the permissions you have granted to the user.
Try below steps to trace the DB related issues while performing update.
1. Use the ojdbc6_g.jar version of the JDBC driver. This jar will work with jdbc tracing.
In setupDatabase.properties set pega.jdbc.driver.jar=location of ojdbc6_g.jar
2. Create a file JDBCConfig.properties file to set the level of trace that you want.
.level=SEVERE
oracle.level=FINE
oracle.jdbc.level=FINE
oracle.jdbc.handlers=java.util.logging.FileHandler
java.util.logging.FileHandler.level=FINE
java.util.logging.FileHandler.pattern=jdbcTraceUpgrade.log
java.util.logging.FileHandler.count=20
java.util.logging.FileHandler.formatter=java.util.logging.SimpleFormatter
java.util.logging.FileHandler.append=true
3. Before you run the upgrade.sh script you need to set ANT_OPTS like this. For the second parameter is the location where you put the JDBCConfig.properties.properties file. If you put the config file in the scripts directory you can just set ANT_OPTS like this. If you put it someplace else then include the path.
For Unix:
export ANT_OPTS="-Doracle.jdbc.Trace=true -Djava.util.logging.config.file=JDBCConfig.properties"
For Windows:
set ANT_OPTS="-Doracle.jdbc.Trace=true -Djava.util.logging.config.file=JDBCConfig.properties"
4. Then just run ./upgrade.sh (or update.bat) and the jdbcTraceUpgrade.log file that is generated.
The generated log file shows if there are any DB related exceptions while update.
AI4Process
GB
Hello Sandeep,
Thanks a ton for your reply. Please find the result of the query and list of privileges for deployment user as attachments. Meanwhile I follow the other instructions.
Regards
Chandramouli
AI4Process
GB
Hello Sandeep,
We have done following -
1. updated setupDatabase.properties to set pega.jdbc.driver.jar=location of ojdbc6_g.jar
2. Created JDBCConfig.properties file under script folder with given details
3. updated update.sh file with following text - export ANT_OPTS="-Doracle.jdbc.Trace=true -Djava.util.logging.config.file=JDBCConfig.properties"
4. executed the update.sh script.
But, NO jdbcTraceUpgrade.log is generated under script/logs directory.
AI4Process
GB
Want to add few more information -
1. We are following Pega 7.3.1 update document(https://docs-previous.pega.com/pega-731-platform-update-guide
).2. We are doing in-place update, but in the above document specify only about out-of-place update.
3. We have not updated migrateSystem.properties ,as we are executing In-place update. And the source and destination database are same for in-place update.
Accepted Solution
AI4Process
GB
This particular issue is resolved. previously we unzipped the media file in windows machine and the transferred it to Linux box and tried to execute. But, later we copied the entire media file to Linux box and unzip it there.And then execute the script and found the issue is resolved.