Question

5
Replies
62
Views
ParmeetSinghH Member since 2015 7 posts
Infosys Limited
Posted: 1 year ago
Last activity: 1 year 1 month ago
Closed

DEVOPS - Schema not priveleged

Dears,

With Pega Deployment Manager 02.01.03 we are delivering package of 2 products.

Rule jar ( list of all ruleset) and Data Instance (All Data instances for DB, DB Table, Class etc).

1 - When we import Rule Jar, if there are any aged updates then the pipeline fails with status, pyStatusMessage: "There are aged updates in the archive. Exiting the import process. List of aged updates" and the pipeline fails.

the alternative is we save the list of aged rules in Development Environment and then re-import using the same utility tool. This way Import was successful. Is there any alternative to handle this?

2 - When we import Data Instance, we get a screen with checkbox for Automatic and Manual. We import via Manual skipping the auto update of Schema, but Deployment Manager takes the automatic by default and sends the status value as failed. is there any alternative to handle this?

the DSS value for "AutoDBSchemaChanges" is enabled.

,"pySchemaSQL":"--execute on the database specified by Data-Admin-DB-Name PegaRULES:\nALTER TABLE MCOM_SCHEMA.pc_BGC_BE_IDSync_MCOM_Work ADD \"MYFIRSTNAME\" VARCHAR2 (50)\n;\n\n--execute on the database specified by Data-Admin-DB-Name PegaRULES:\n

--execute on the database specified by Data-Admin-DB-Name PegaRULES,"

pyStatusValue":"SCHEMA_NOT_PRIVILEGED"

DevOps
Moderation Team has archived post
Share this page LinkedIn