Question
Tata Consultancy Services
IN
Last activity: 19 May 2016 9:13 EDT
We upgraded from Pega 7.1.7 to Pega 7.2 andwe see that build is success. As part of the Post-Upgrade activity, i have checked PRPC Schema Report wizard and I see there are some missing DB entity type of Index under both the schemas. How I can install thes
We have upgraded from Pega 7.1.7 to Pega 7.2 and we see that build is success. As part of the Post-Upgrade activity, we checked PRPC Schema Report wizard and I see there are some missing DB entity type of Index under both the schemas.
How I can install these missing Index objects and make it available.
Message was edited by: Gangaprasad Yepuri
-
Like (0)
-
Share this page Facebook Twitter LinkedIn Email Copying... Copied!
Pegasystems Inc.
AU
Hi Gangaprasad,
Can you share the screen print of the indexes from 7.1.7 which are missing in the v7.2
Updated: 18 May 2016 5:40 EDT
Tata Consultancy Services
IN
Hi Basavaraj,
I have attached screenshot of first page. It has total 6 pages.
Updated: 18 May 2016 9:20 EDT
Pegasystems Inc.
US
What process did you follow to upgrade from 7.1.7 to 7.2? Did you do an upgrade or update? It seems like you missed a step as those indexes should be on the system.
You can get the missing indexes installed using the generateddl script to generate them and apply but I want to understand how your system ended up with them missing in the first place.
Tata Consultancy Services
IN
HI Celeste,
I used command line scripts to Upgrade to Pega 7.2. I have done In-place upgrade of my test instance where I am upgrading my actual Rules and Data schemas.
1. Updated setupdatabase.properties with required config. In this file, I have kept rebuild.indexes=false which is by default and the note says that
(
# Rebuild Database Rules Indexes after Rules Load to improve Database Access Performance
# It can be executed manually by running the stored procedure SPPR_REBUILD_INDEXES
# Default is false except for z/OS, where the default is true
)
2. Generated Upgrade DDL using generateddl.sh script. Executed the generated DDL to create new objects on the existing Rules schema.
3. Executed Upgrade.sh script which upgraded the existing Rules schema.
4. Executed Upgrade.sh script with Data only option which upgraded existing Data schema
I am able to successfully login to new Pega 7.2 Designer studio. But I want to understand why it missed creating those missing indexes and what would be the impact.
Thanks
Ganga
Pegasystems Inc.
US
That property just controls rebuilding the indexes. It has nothing to do with actually creating them in the first place.
From the process you followed I see the issue. As an FYI, you could have done an update from 7.1.7 to 7.2 instead of a full upgrade. If you wanted to do an in place upgrade (or update) you could have done it with just executing the upgrade script setting both the rules and data schema properties appropriately. If you needed to generate ddl and have dba apply you would again need to set both the data and rules schema during that step.
To fix this set both the data and rules schema properties and run the generateddl script again.
Tata Consultancy Services
IN
Hi Celeste,
I mean that I have executed generateddl.sh with both Rules and Data schema as below
generateddl.sh --action upgrade --outputDirectory ../schema/generated --dbType udb --dbSchema GNWRULES --dbDataSchema GNWDATA
Attached is the file generated after executing generateddl.sh. I have executed this SQL manually which updated both rules and data schema
Pegasystems Inc.
US
In the attached udb.sql file you do not see any drops of these indexes. When you did this step #3 did you have both the rules and data schema names specified in the properties file and choose bypass.pega.schema=true?
3. Executed Upgrade.sh script which upgraded the existing Rules schema.
Please run this command again and post the generated udb.sql file
generateddl.sh --action upgrade --outputDirectory ../schema/generated --dbType udb --dbSchema GNWRULES --dbDataSchema GNWDATA
Tata Consultancy Services
IN
To answer your query, I have given both Rules and Data schema under setupdatabase.prop file and bypass schema is set as true in the same file.
I have executed generateddl again and it generated udb.sql file. But the file is generated out of Pega 7.2 DB now as the system is upgraded from 7.1.7 to 7.2
Attached udb.sql file
Pegasystems Inc.
US
Yes, I know the sql was generated against the 7.2 DB. That is what I wanted. I wanted to see if it would add the missing indexes in the sql. It doesn't have them which makes me wonder if the indexes are actually there and the problem is with the schema report wizard. Can you pick an index from each schema and see if they actually exist?
Tata Consultancy Services
IN
Hi Celeste,
I randomly verified few Indexes on both the schemas and the Index actually exist but they are displayed in Missing schema Report wizard. I have raised one SR with Pega on this SR-A62713.
Thanks
Ganga
Pegasystems Inc.
US
Thank you Gangaprasad Yepuri for letting us know the SR. I have updated your thread and therefore connected your SR with this post so that the Engineer working it may see all the troubleshooting done here.