Schema not found error when importing a Rule-Admin-Product file
Valid from Pega Version 7.1.8
If you import a Rule-Admin-Product file (RAP) file that includes a schema that has a view, grammar parsing changes can mean that the Pega 7 Platform is unable to find the schema.
To enable the Pega 7 Platform to find the schema:
- Review the error message that indicates that the schema was not found and identify the following items:
- The name of the schema that is causing the error
- The table name in the format: wrong_schema_name.table_name...
- The DDL that the Pega 7 Platform is trying to apply
- Use the table name to identify the correct schema name in your system. This schema is usually your data schema, but might also be an external database.
- Download the DDL.
- Correct the schema name and save the DDL.
- Manually apply the DDL.
New Schema Tools and Query Inspector landing pages for Pega Cloud
Valid from Pega Version 7.2
Two landing pages have been added for advanced database administration tasks for Pega Cloud customers who use a Pega-hosted instance. These landing pages minimize the operations that need to be performed outside of the Pega 7 Platform. They are available only for customers who use a Postgres database.
From the new Schema Tools landing page, you can view PegaRULES and PegaDATA database schemas, increase the size of a column, add a composite or function index, update database statistics for a table, and defragment a table.
From the new Query Inspector landing page, you can enter an SQL query and generate an explain plan.
To use these landing pages, you must have the new PegaRULES:DatabaseAdministrator role. You access the landing pages by clicking or by clicking . The individual features that you can access are determined by the privileges that are assigned to you.
For more information, see Schema Tools and Query Inspector landing pages for tuning and maintaining databases in the Pega Cloud.