Question
Ford Motor Company
Ford Motor Company
US
Ford Motor Company
Posted: Jul 9, 2019
Last activity: Jul 10, 2019
Last activity: 10 Jul 2019 16:38 EDT
Closed
Solved
Getting an error while Upgrading from 7.1.9 to 7.4
Targets:Update
Unable to locate tools.jar.
Show More
Targets:Update
Unable to locate tools.jar. Expected to find it in C:\Program Files\Java\jre8\lib\tools.jar
Buildfile: C:\Users\*******\Desktop\115944_Pega74-U\.\pegaGuiInstallerTemp\build.xml
SetupProperties:
Update:
[echo] calling update ....
update:
startover_or_resume:
[pega:propertyparser] Reading Properties from: C:\Users\*******\Desktop\115944_Pega74-U\scripts/setupDatabase.properties
[echo] Performing update...
Initialization:
[echo] Performing Update Finalization
[echo] Using logging configuration from: ./config/deploylogging.properties
[mkdir] Created dir: C:\Users\*******\Desktop\115944_Pega74-U\scripts\taskRuntimes
[pega:propertyparser] Reading Properties from: C:\Users\*******\Desktop\115944_Pega74-U\scripts/setupDatabase.properties
pega.jdbc.driver.jar=C:\Users\****\Desktop\sqljdbc4.jar
pega.jdbc.driver.class=com.microsoft.sqlserver.jdbc.SQLServerDriver
pega.database.type=mssql
pega.jdbc.url=jdbc:sqlserver://*******:1433;databaseName=*****;SelectMethod=cursor;SendStringParametersAsUnicode=false
pega.jdbc.username=*******
pega.jdbc.password=*****
pega.admin.password=*****
rules.schema.name=Rules
data.schema.name=dbo
customerdata.schema.name=
user.temp.dir=
pega.zos.properties=
system.name=pega
production.level=2
multitenant.system=false
update.existing.applications=false
update.applications.schema=true
automatic.resume=true
pega.jdbc.driver.jar=C:\Users\*******\Desktop\sqljdbc4.jar
pega.jdbc.driver.class=com.microsoft.sqlserver.jdbc.SQLServerDriver
pega.database.type=mssql
pega.jdbc.url=jdbc:sqlserver://*******:1433;databaseName=*****;SelectMethod=cursor;SendStringParametersAsUnicode=false
pega.jdbc.username=*****
pega.jdbc.password=*****
pega.admin.password=*****
rules.schema.name=Rules
data.schema.name=dbo
customerdata.schema.name=
user.temp.dir=
pega.zos.properties=
system.name=pega
production.level=2
multitenant.system=false
update.existing.applications=false
update.applications.schema=true
automatic.resume=true
[pega:propertyparser] pega.jdbc.driver.class=com.microsoft.sqlserver.jdbc.SQLServerDriver
[pega:propertyparser] update.existing.applications=false
[pega:propertyparser] pega.jdbc.password=*****
[pega:propertyparser] update.applications.schema=true
[pega:propertyparser] automatic.resume=true
[pega:propertyparser] pega.jdbc.driver.jar=C:\Users\*******\Desktop\sqljdbc4.jar
[pega:propertyparser] rules.schema.name=Rules
[pega:propertyparser] pega.jdbc.url=jdbc:sqlserver://******:1433;databaseName=*****;SelectMethod=cursor;SendStringParametersAsUnicode=false
[pega:propertyparser] pega.database.type=mssql
[pega:propertyparser] user.temp.dir=
[pega:propertyparser] production.level=2
[pega:propertyparser] pega.zos.properties=
[pega:propertyparser] customerdata.schema.name=
[pega:propertyparser] pega.jdbc.username=******
[pega:propertyparser] pega.admin.password=*****
[pega:propertyparser] multitenant.system=false
[pega:propertyparser] system.name=pega
[pega:propertyparser] data.schema.name=dbo
[echo] *** JVM Arguments -XX:MaxHeapSize=1280m ***
[propertyfile] Creating new property file: C:\Users\*******\Desktop\115944_Pega74-U\scripts\resume.properties
[propertyfile] Updating property file: C:\Users\*******\Desktop\115944_Pega74-U\scripts\resume.properties
Found 99264240KB of free space on 'C:\Users\*******\AppData\Local\Temp\'
[echo] setting to generated ddl
[echo] Driver Path: C:\Users\*******\Desktop\sqljdbc4.jar
[mkdir] Created dir: C:\Users\*******\AppData\Local\Temp\PegaInstallTemp-09-July-2019-09.13.52\load
[mkdir] Created dir: C:\Users\*******\AppData\Local\Temp\PegaInstallTemp-09-July-2019-09.13.52\pr_temp
[touch] Creating C:\Users\*******\Desktop\115944_Pega74-U\scripts\logs\Warnings.log
[echo] Using C:\Users\*******\AppData\Local\Temp\/PegaInstallTemp-09-July-2019-09.13.52 for install scratch space...
[unzip] Expanding: C:\Users\*******\Desktop\115944_Pega74-U\archives\prweb.war into C:\Users\*******\AppData\Local\Temp\PegaInstallTemp-09-July-2019-09.13.52\load
[unzip] Expanding: C:\Users\*******\Desktop\115944_Pega74-U\archives\pegadbinstall-classes.zip into C:\Users\*******\AppData\Local\Temp\PegaInstallTemp-09-July-2019-09.13.52\load
[copy] Copying 1 file to C:\Users\*******\AppData\Local\Temp\PegaInstallTemp-09-July-2019-09.13.52\load\WEB-INF\classes
[copy] Copying 1 file to C:\Users\*******\AppData\Local\Temp\PegaInstallTemp-09-July-2019-09.13.52
Checking Configuration Files:
[echo] Rules schema has been set to 'Rules'
[echo] ***writing resume property upgrade.from.version=07-10-20 to file***
[propertyfile] Updating property file: C:\Users\*******\Desktop\115944_Pega74-U\scripts\resume.properties
[echo] Upgrading from Pega-RULES product version 07-10-20
Processing Configuration Files:
[propertyfile] Creating new property file: C:\Users\*******\AppData\Local\Temp\PegaInstallTemp-09-July-2019-09.13.52\prbootstrap.properties
Configuration:
[echo] Database Type: mssql
[echo] JDBC Driver JAR: C:\Users\*******\Desktop\sqljdbc4.jar
[echo] Bootstrap Config: C:\Users\*******\AppData\Local\Temp\/PegaInstallTemp-09-July-2019-09.13.52/prbootstrap.properties
[echo] PegaRULES Config: C:\Users\*******\AppData\Local\Temp\/PegaInstallTemp-09-July-2019-09.13.52/prconfig.xml
[echo] PegaRULES Logging Config: C:\Users\*******\AppData\Local\Temp\/PegaInstallTemp-09-July-2019-09.13.52/prlog4j2.xml
[echo] Deployment Logging Config: ./config/deploylogging.properties
Verify ML Readiness:
System meets basic requirements for update to 07-10-35
PRPC_Rules build date: 2018-04-11 12.36 UTC
No superseded code or rules.
Generate Upgrade DDL:
[mkdir] Created dir: C:\Users\*******\Desktop\115944_Pega74-U\schema\generated\mssql\upgrade
[mkdir] Created dir: C:\Users\*******\Desktop\115944_Pega74-U\schema\generated\mssql\util
Execute SQL In Transaction:false
_clean:
[echo] Cleaning up previous invocation...
[delete] Deleting directory C:\Users\*******\Desktop\115944_Pega74-U\schema\generated\mssql
[echo] Cleaning up previous invocation...(Complete)
_createOutputDirs:
[echo] Creating output directory at C:\Users\*******\Desktop\115944_Pega74-U\scripts/../schema/generated/mssql
[mkdir] Created dir: C:\Users\*******\Desktop\115944_Pega74-U\schema\generated\mssql
_callDDLUtilityUpgrade:
[echo] Call DDL Generation Upgrade Utility...
[echo] C:\Users\*******\Desktop\115944_Pega74-U\scripts/lib/xercesImpl.jar;C:\Users\*******\Desktop\115944_Pega74-U\scripts/lib/xml-apis.jar;C:\Users\*******\Desktop\115944_Pega74-U\scripts/lib/resolver.jar;
[echo] archive_dir: C:\Users\*******\Desktop\115944_Pega74-U\scripts/lib
[java] 2019-07-09 09:14:41,245 ( install) INFO - Initializing properties with default values
[java] 2019-07-09 09:14:41,355 ( install) INFO - Setting default Entity Value for pega_enable_nologging = true
[java] 2019-07-09 09:14:41,355 ( install) INFO - Getting database metadata
[java] 2019-07-09 09:14:44,789 ( install) INFO - Reading views from schema "dbo"
[java] Exception in thread "main" java.lang.RuntimeException: Error during execution of upgrade on platform mssql using schemas Rules, dbo, dbo
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1569)
[java] Caused by: com.pega.pegarules.data.ddl.DatabaseException: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pr4_rule_vw'.
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:439)
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:480)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.saveCurrentSchemaState(SchemaGenerator.java:496)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1395)
[java] Caused by: com.microsoft.sqlserver.jdbc.SQLServerException: Invalid object name 'pr4_rule_vw'.
[java] at com.microsoft.sqlserver.jdbc.SQLServerException.makeFromDatabaseError(SQLServerException.java:216)
[java] at com.microsoft.sqlserver.jdbc.TDSTokenHandler.onEOF(tdsparser.java:254)
[java] at com.microsoft.sqlserver.jdbc.TDSParser.parse(tdsparser.java:84)
[java] at com.microsoft.sqlserver.jdbc.SQLServerResultSet.<init>(SQLServerResultSet.java:311)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.getNextResult(SQLServerStatement.java:1526)
[java] at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.doExecutePreparedStatement(SQLServerPreparedStatement.java:404)
[java] at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement$PrepStmtExecCmd.doExecute(SQLServerPreparedStatement.java:350)
[java] at com.microsoft.sqlserver.jdbc.TDSCommand.execute(IOBuffer.java:5696)
[java] at com.microsoft.sqlserver.jdbc.SQLServerConnection.executeCommand(SQLServerConnection.java:1715)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeCommand(SQLServerStatement.java:180)
[java] at com.microsoft.sqlserver.jdbc.SQLServerStatement.executeStatement(SQLServerStatement.java:155)
[java] at com.microsoft.sqlserver.jdbc.SQLServerPreparedStatement.executeQuery(SQLServerPreparedStatement.java:285)
[java] at com.pega.pegarules.data.ddl.JDBCIntrospector.getTablesDependentonViews(JDBCIntrospector.java:1631)
[java] at com.pega.pegarules.data.ddl.JDBCIntrospector.readViews(JDBCIntrospector.java:496)
[java] at com.pega.pegarules.data.ddl.JDBCIntrospector.createDatabaseJaxbObjectByIntrospection(JDBCIntrospector.java:120)
[java] at com.pega.pegarules.data.ddl.SchemaManager.createDomDocumentFromDbIntrospection(SchemaManager.java:2039)
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:435)
[java] ... 3 more
Show Less
Earlier,our System was Upgraded from PRPC v6.2SP2 , where we had both schema's in dbo, few views, stored procs, scalar functions referring dbo schema where they changed to Rules schema in the later versions of PRPC.
After we deleted the below Stored Proc/Functions/Views .... Rules and Data Upgrade went successful.
====
Rules Upgrade:
====
DROP PROCEDURE [Rules].[sppc_data_uniqueid_withouttran]
DROP FUNCTION [dbo].[fn_LsnSegmentToHexa]
DROP FUNCTION [dbo].[fn_NumericLsnToHexa]
DROP PROCEDURE [Rules].[sppr_aggregate_usage]
DROP PROCEDURE [Rules].[sppr_populate_index_data]
DROP PROCEDURE [Rules].[sppr_sys_getindextime]
DROP PROCEDURE [Rules].[sppr_sys_statusnodes_set]
DROP PROCEDURE [Rules].[sppr_sys_updatescache_flush]
DROP PROCEDURE [Rules].[sppr_sys_updatescache_gettime]
====
Data Upgrade:
====
DROP VIEW [dbo].[pcv4_assignment_summary]
DROP VIEW [dbo].[pcv4_assignmentwb_summary]
DROP VIEW [dbo].[pcv4_work_history]
DROP VIEW [dbo].[pwbv4_circumstance_duplicates]
DROP VIEW [dbo].[pwbv4_rule_locking]
DROP VIEW [dbo].[pwbv4_rule_overrides]
DROP VIEW [dbo].[pwbv4_rule_summary]
--->
https://community.pega.com/support/support-articles/unable-update-or-upgrade-existing-sql-server-722
Earlier,our System was Upgraded from PRPC v6.2SP2 , where we had both schema's in dbo, few views, stored procs, scalar functions referring dbo schema where they changed to Rules schema in the later versions of PRPC.
After we deleted the below Stored Proc/Functions/Views .... Rules and Data Upgrade went successful.
====
Rules Upgrade:
====
DROP PROCEDURE [Rules].[sppc_data_uniqueid_withouttran]
DROP FUNCTION [dbo].[fn_LsnSegmentToHexa]
DROP FUNCTION [dbo].[fn_NumericLsnToHexa]
DROP PROCEDURE [Rules].[sppr_aggregate_usage]
DROP PROCEDURE [Rules].[sppr_populate_index_data]
DROP PROCEDURE [Rules].[sppr_sys_getindextime]
DROP PROCEDURE [Rules].[sppr_sys_statusnodes_set]
DROP PROCEDURE [Rules].[sppr_sys_updatescache_flush]
DROP PROCEDURE [Rules].[sppr_sys_updatescache_gettime]
====
Data Upgrade:
====
DROP VIEW [dbo].[pcv4_assignment_summary]
DROP VIEW [dbo].[pcv4_assignmentwb_summary]
DROP VIEW [dbo].[pcv4_work_history]
DROP VIEW [dbo].[pwbv4_circumstance_duplicates]
DROP VIEW [dbo].[pwbv4_rule_locking]
DROP VIEW [dbo].[pwbv4_rule_overrides]
DROP VIEW [dbo].[pwbv4_rule_summary]
--->
https://community.pega.com/support/support-articles/unable-update-or-upgrade-existing-sql-server-722
com.pega.pegarules.data.ddl.DatabaseException: com.microsoft.sqlserver.jdbc.SQLServerException: The dependencies reported for entity "dbo.sp_upgraddiagrams" might not include reference
Root Cause
A defect or configuration issue in the operating environment.The diagramming facility of MS/SQL interferes with the update process.
Resolution
Perform the following local-change:Remove the diagramming feature from the database instance and restart the update.
https://stackoverflow.com/questions/525610/how-to-remove-diagramming-support-objects-from-sql-server
DROP PROCEDURE sp_upgraddiagrams
DROP PROCEDURE sp_helpdiagrams
DROP PROCEDURE sp_helpdiagramdefinition
DROP PROCEDURE sp_creatediagram
DROP PROCEDURE sp_renamediagram
DROP PROCEDURE sp_alterdiagram
DROP PROCEDURE sp_dropdiagram