PEGA DB2 SQL View
I have an instance of PEGA 7.1.6 and the view 'PWBV4_RULE_LOCKING' is differnet in our Development region from our QA and Production region. Does anyone have the correct SQL script that this view uses? I need to sync up our database regions. Below are the 2 definitions pof the view that we have. Thanks for the help.
From Development:
create view PROD.pwbv4_rule_locking
AS
SELECT
pxCreateDateTime,
'Data-Rule-Locking' AS pxObjClass,
pxInsName,
pyClass,
pyClassName,
pxUpdateDateTime,
pxUpdateOpName,
I have an instance of PEGA 7.1.6 and the view 'PWBV4_RULE_LOCKING' is differnet in our Development region from our QA and Production region. Does anyone have the correct SQL script that this view uses? I need to sync up our database regions. Below are the 2 definitions pof the view that we have. Thanks for the help.
From Development:
create view PROD.pwbv4_rule_locking
AS
SELECT
pxCreateDateTime,
'Data-Rule-Locking' AS pxObjClass,
pxInsName,
pyClass,
pyClassName,
pxUpdateDateTime,
pxUpdateOpName,
pxUpdateOperator,
pyLabel,
pyRuleName,
pyRuleSet,
pyRuleSetVersion,
pyCircumstanceProp,
pxInstanceLockedBy,
pzInsKey,
pyCircumstanceVal,
pyRuleAvailable
FROM PROD.pr4_rule_vw WHERE pyClass != 'Rule-Obj-Class';
From QA
--------------------------------------------------
-- Create View PROD.PWBV4_RULE_LOCKING
--------------------------------------------------
CREATE VIEW pwbv4_rule_locking AS SELECT 'Data-Rule-Locking' AS pxObjClass,pxInsName,pxObjClass AS pyClass,pxUpdateDateTime,pxUpdateOpName,pxUpdateOperator,pyLabel,pyRuleSet,pyRuleSetVersion,pyCircumstanceProp,pxInstanceLockedBy,pzInsKey FROM pr4_rule WHERE pxObjClass LIKE 'Rule-%' UNION SELECT 'Data-Rule-Locking' AS pxObjClass,pxInsName,pxObjClass AS pyClass,pxUpdateDateTime,pxUpdateOpName,pxUpdateOperator,pyLabel,pyRuleSet,pyRuleSetVersion,pyCircumstanceProp,pxInstanceLockedBy,pzInsKey FROM pr4_rule_file WHERE pxObjClass LIKE 'Rule-%' UNION SELECT 'Data-Rule-Locking' AS pxObjClass,pxInsName,pxObjClass AS pyClass,pxUpdateDateTime,pxUpdateOpName,pxUpdateOperator,pyLabel,pyRuleSet,pyRuleSetVersion,pyCircumstanceProp,pxInstanceLockedBy,pzInsKey FROM pr4_fieldvalue WHERE pxObjClass LIKE 'Rule-%' UNION SELECT 'Data-Rule-Locking' AS pxObjClass,pxInsName,pxObjClass AS pyClass,pxUpdateDateTime,pxUpdateOpName,pxUpdateOperator,pyLabel,pyRuleSet,pyRuleSetVersion,pyCircumstanceProp,pxInstanceLockedBy,pzInsKey FROM pr4_rule_flow WHERE pxObjClass LIKE 'Rule-%' UNION SELECT 'Data-Rule-Locking' AS pxObjClass,pxInsName,pxObjClass AS pyClass,pxUpdateDateTime,pxUpdateOpName,pxUpdateOperator,pyLabel,pyRuleSet,pyRuleSetVersion,pyCircumstanceProp,pxInstanceLockedBy,pzInsKey FROM pr4_rule_property WHERE pxObjClass LIKE 'Rule-%' UNION SELECT 'Data-Rule-Locking' AS pxObjClass,pxInsName,pxObjClass AS pyClass,pxUpdateDateTime,pxUpdateOpName,pxUpdateOperator,pyLabel,pyRuleSet,pyRuleSetVersion,pyCircumstanceProp,pxInstanceLockedBy,pzInsKey FROM pr4_rule_sysgen WHERE pxObjClass LIKE 'Rule-%';
***Updated by Moderator: Marissa to update categories***
Accepted Solution
Cahaba Gba
US
I found this when I was trying to delete a user from PEGA. Using the original view from our development region, it did not return any rows for rules that the user had checked out. However,when trying to delete the user, PEGA would tell me that they still had rules checked out. Using the script in our QA region, I found the rules in question and was able to delete them from the database. This allowed me to remove the user from PEGA.
This is why I am wondering if the view from QA is the view that should be used instead of the view from our development region.
Cahaba Gba
US
I found this when I was trying to delete a user from PEGA. Using the original view from our development region, it did not return any rows for rules that the user had checked out. However,when trying to delete the user, PEGA would tell me that they still had rules checked out. Using the script in our QA region, I found the rules in question and was able to delete them from the database. This allowed me to remove the user from PEGA.
This is why I am wondering if the view from QA is the view that should be used instead of the view from our development region.
Accepted Solution
Cahaba Gba
US
I found this when I was trying to delete a user from PEGA. Using the original view from our development region, it did not return any rows for rules that the user had checked out. However,when trying to delete the user, PEGA would tell me that they still had rules checked out. Using the script in our QA region, I found the rules in question and was able to delete them from the database. This allowed me to remove the user from PEGA.
This is why I am wondering if the view from QA is the view that should be used instead of the view from our development region.