Issue generating DDL or upgrading application to pega 8.6.3 on DB2zOS v12
I have recently tried and upgraded PRPC 8.5.3 to 8.6.3 connecting from RHEL 7 application server to DB2zOS database dual schema v12 and to generate the DDL from Command Line it took BUILD SUCCESSFUL Total time: 123 minutes 47 seconds
This is with using a 4x16 VM and allocating the following custom property.
custom.jvm.args=-Xcompressedrefs -verbose:gc -Xverbosegclog:/tempDir/pegagc.log -Xgcpolicy:gencon -Xmn8192m -Xmx10240m
JDBC Driver version is 4.31
I have recently tried and upgraded PRPC 8.5.3 to 8.6.3 connecting from RHEL 7 application server to DB2zOS database dual schema v12 and to generate the DDL from Command Line it took BUILD SUCCESSFUL Total time: 123 minutes 47 seconds
This is with using a 4x16 VM and allocating the following custom property.
custom.jvm.args=-Xcompressedrefs -verbose:gc -Xverbosegclog:/tempDir/pegagc.log -Xgcpolicy:gencon -Xmn8192m -Xmx10240m
JDBC Driver version is 4.31
To upgrade the application with out upgrading the custom application the process took the following time. BUILD SUCCESSFUL Total time: 320 minutes 12 seconds The reason for this is the process is reading the SYSIBM,SYSFUN and not using the indexes to do so. PLAN + Thread: Plan=DISTSERV Connid=SERVER Corrid=db2jcc_appli Authid=XXXXXX + Dist : Type=DATABASE ACCESS, Luwid=GA027727.B95C.DB579342D4D7=92593 + Location : :: Proprietary information hidden + DB2: DDD3 call + SQL call is active, call information is as follows : + + Thread Status = IN-SQL-CALL SQL Request Type = DYNAMIC + Total SQL Reqs = 3 SQL Call Type = OPEN + SQL DBRM Name = SYSLH200 SQL Statement Number = 00000 + Collection ID = NUL12510 + + select STYPE from SYSIBM.SYSCOPY where tsname in (select tsname from SYS + IBM.SYSTABLES where name = ?) order by timestamp desc
statements are 10 to 15 second as it is reading syscopy and other catalog tables.
SYSCOPY contain information about copies, loads etc.
The key on SYSCOPY is DBNAME. TSNAME is second column so you are getting a non matching index scan.
After explaining all that Has anyone ran across this problem before and is there a patch from Pega out there to fix this problem.
***Edited by Moderator: Pooja Gadige to add capability tag, change category from Product to Update***
Pegasystems Inc.
US
@ANGLINA1I don't think that I have seen this issue before. In the past upgrades has the generateddl taken anywhere near that long? There are conf files that are there for zos but we don't have a ton of clients on it so it isn't something I look at often. Let me check the deployment guides and if nothing obvious then you should open an INC so we can look at this.
Pegasystems Inc.
US
@CelesteDufresne_GCS Platform support guide mentions needing 4.19.56 JDBC or higher. You also need to be sure that you are using the correct version that matches with the database. I am reading over your problem description and I am not sure what you are comparing. I am assuming that the times above are for the total upgrade and not for simply the generating of the ddl is it taking 123 minutes to generate ddl. And you are not connecting with an app server or using dual user for the upgrade. What is it that you are running that you see the 320 minutes? Is that an upgrade of a different environment? Logs would be helpful here. Do you using the same jdbc driver version, java version, etc. when running on 8.5.3 as you use for the upgrade? Have you started the environment after upgrading?
Pegasystems Inc.
US
@CelesteDufresne_GCSThe DB2SiteDependent.properties is probably what you need to be looking at for the time difference issue you are seeing.
https://docs-previous.pega.com/pega-platform-87-update-guide-ibm-websphere-and-ibm-db2-zos