Question
Tata Consultancy Services
SA
Last activity: 27 May 2025 9:28 EDT
Pega Upgrade Issue from 8.8.3 to 24.1.3
We are trying to upgrade Pega platform from 8.8.3 to 24.1.3.
During upgrade we are facing issue with sql executions related to views , earlier we faced issue with Stored procedure and we executed upgrade with elevated DB user and stored procedure got executed successfully.
Now issue with views with the same elevated user. Please find the stack trace below, we are in k8s environment.
We are trying to upgrade Pega platform from 8.8.3 to 24.1.3.
During upgrade we are facing issue with sql executions related to views , earlier we faced issue with Stored procedure and we executed upgrade with elevated DB user and stored procedure got executed successfully.
Now issue with views with the same elevated user. Please find the stack trace below, we are in k8s environment.
[java] Exception in thread "main" java.lang.RuntimeException: Error during execution of upgrade on platform oracledate using schemas SYSTEM, SYSTEM, SYSTEM
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1500)
[java] Caused by: com.pega.pegarules.data.ddl.DatabaseException: java.sql.SQLException: ORA-31603: object "MVIEW_EVALUATIONS" of type VIEW not found in schema "SYSTEM"
[java] ORA-06512: at "SYS.DBMS_METADATA", line 6731
[java] ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
[java] ORA-06512: at "SYS.DBMS_METADATA", line 6718
[java] ORA-06512: at "SYS.DBMS_METADATA", line 9734
[java] ORA-06512: at line 1
[java]
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:430)
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:471)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.getSchemaManagerFromConnection(SchemaGenerator.java:249)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.getSchemaManagerFromConnection(SchemaGenerator.java:225)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.generateUpgradeDDL(SchemaGenerator.java:578)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1371)
[java] Caused by: java.sql.SQLException: ORA-31603: object "MVIEW_EVALUATIONS" of type VIEW not found in schema "SYSTEM"
[java] ORA-06512: at "SYS.DBMS_METADATA", line 6731
[java] ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
[java] ORA-06512: at "SYS.DBMS_METADATA", line 6718
[java] ORA-06512: at "SYS.DBMS_METADATA", line 9734
[java] ORA-06512: at line 1
[java]
[java] at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:526)
[java] at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:462)
[java] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1104)
[java] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:553)
[java] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:269)
[java] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:655)
[java] at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:270)
[java] at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:91)
[java] at oracle.jdbc.driver.T4CPreparedStatement.executeForRows(T4CPreparedStatement.java:970)
[java] at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1020)
[java] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1176)
[java] at oracle.jdbc.driver.OraclePreparedStatement.executeInternal(OraclePreparedStatement.java:3671)
[java] at oracle.jdbc.driver.T4CPreparedStatement.executeInternal(T4CPreparedStatement.java:1426)
[java] at oracle.jdbc.driver.OraclePreparedStatement.executeQuery(OraclePreparedStatement.java:3718)
[java] at oracle.jdbc.driver.OraclePreparedStatementWrapper.executeQuery(OraclePreparedStatementWrapper.java:1167)
[java] at com.pega.pegarules.data.ddl.JDBCIntrospector.readObjectBodies(JDBCIntrospector.java:2031)
[java] at com.pega.pegarules.data.ddl.JDBCIntrospector.readViews(JDBCIntrospector.java:498)
[java] at com.pega.pegarules.data.ddl.JDBCIntrospector.createDatabaseJaxbObjectByIntrospection(JDBCIntrospector.java:119)
[java] at com.pega.pegarules.data.ddl.SchemaManager.createDomDocumentFromDbIntrospection(SchemaManager.java:2041)
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:426)
[java] ... 5 more
[java] Caused by: Error : 31603, Position : 7, Sql = select dbms_metadata.get_ddl('VIEW',:1 ,:2 ) as def from dual, OriginalSql = select dbms_metadata.get_ddl('VIEW',?,?) as def from dual, Error Msg = ORA-31603: object "MVIEW_EVALUATIONS" of type VIEW not found in schema "SYSTEM"
[java] ORA-06512: at "SYS.DBMS_METADATA", line 6731
[java] ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
[java] ORA-06512: at "SYS.DBMS_METADATA", line 6718
[java] ORA-06512: at "SYS.DBMS_METADATA", line 9734
[java] ORA-06512: at line 1
[java]
[java] at oracle.jdbc.driver.T4CTTIoer11.processError(T4CTTIoer11.java:530)
[java] ... 24 more
[java] Exception in thread "main" java.lang.RuntimeException: Error during execution of upgrade on platform oracledate using schemas SYSTEM, SYSTEM, SYSTEM
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.main(SchemaGenerator.java:1500)
[java] Caused by: com.pega.pegarules.data.ddl.DatabaseException: java.sql.SQLException: ORA-31603: object "MVIEW_EVALUATIONS" of type VIEW not found in schema "SYSTEM"
[java] ORA-06512: at "SYS.DBMS_METADATA", line 6731
[java] ORA-06512: at "SYS.DBMS_SYS_ERROR", line 105
[java] ORA-06512: at "SYS.DBMS_METADATA", line 6718
[java] ORA-06512: at "SYS.DBMS_METADATA", line 9734
[java] ORA-06512: at line 1
[java]
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:430)
[java] at com.pega.pegarules.data.ddl.SchemaManager.<init>(SchemaManager.java:471)
[java] at com.pega.pegarules.data.ddl.SchemaGenerator.getSchemaManagerFromConnection(SchemaGenerator.java:249)
***Edited by Moderator Marije to add Support Case Details ; update capability tags***
Accepted Solution
Updated: 27 May 2025 9:28 EDT
Pegasystems Inc.
GB
HCA Healthcare
US
The error you're facing during the upgrade from Pega 8.8.3 to 24.1.3 is due to a missing view (MVIEW_EVALUATIONS) in the Oracle SYSTEM schema. This typically happens when the upgrade script tries to introspect or fetch metadata of database objects that don't exist. Even though you're using an elevated user, it seems the script is referencing an object that should not be expected in the SYSTEM schema. To fix this, verify your setupDatabase.properties or upgrade configuration file to ensure only the correct Pega rules and data schemas are listed and not the SYSTEM schema. This could be a misconfiguration causing the tool to wrongly introspect SYSTEM instead of your actual application schema. Also, confirm if the MVIEW_EVALUATIONS view exists in your Pega schema; if not, it’s likely safe to exclude it from introspection or add it manually if needed. Consider opening a Pega support ticket if this persists, as it may be a tooling or environment-specific issue during upgrade execution.
Do you want help verifying the correct schema configuration for the upgrade script?
Tata Consultancy Services
SA
@Sairohith Thanks for the response. I have submitted the ticket with Pega as well. Even the team is not sure why the script is being called in the first place.
Oracle is configured as pluggable DB and there is known restriction from Oracle not to execute this system view from pluggable database. Upgrade scripts are trying to execute this view but without any use, since the system view is empty.
We cannot manually exclude this view execution since we don't have explicit control over upgrade scripts in kubernetes environment.
Happy to connect with you, if you have some workaround this.
Pegasystems Inc.
US
Hello @PrasannaB2043
Could you share your ticket number here so we can connect it with this Question?
Thank you!
Pegasystems Inc.
GB
@PrasannaB2043 I have added open ticket INC-C17923 to this question. Please post a reply here once the support team have helped you resolve the issue.
Accepted Solution
Updated: 27 May 2025 9:28 EDT
Pegasystems Inc.
GB
The support ticket was resolved with the below explanation:
Here is our analysis:
-
User switched to "System" user instead of custom application user for Pega
-
The SYSTEM user will not be applicable in this case. You will need to adhere to the Upgrade Process as outlined in our documentation.
Please refer to the following link where you will need to create the necessary users and grant the required privileges for the upgrade:
-
Have you reviewed the ZDT upgrade guide prior to initiating the upgrade? https://github.com/pegasystems/pega-helm-charts/blob/master/docs/upgrading-pega-deployment-zero-downtime.md
-
Upon reviewing the YAML file, we noticed that the targetRulesSchema and targetDataSchema fields are not set, which are mandatory. User explained their plan was to do a in place upgrade with the existing schema that's the reason they didn't provide the new schema names.
The support ticket was resolved with the below explanation:
Here is our analysis:
-
User switched to "System" user instead of custom application user for Pega
-
The SYSTEM user will not be applicable in this case. You will need to adhere to the Upgrade Process as outlined in our documentation.
Please refer to the following link where you will need to create the necessary users and grant the required privileges for the upgrade:
-
Have you reviewed the ZDT upgrade guide prior to initiating the upgrade? https://github.com/pegasystems/pega-helm-charts/blob/master/docs/upgrading-pega-deployment-zero-downtime.md
-
Upon reviewing the YAML file, we noticed that the targetRulesSchema and targetDataSchema fields are not set, which are mandatory. User explained their plan was to do a in place upgrade with the existing schema that's the reason they didn't provide the new schema names.
-
Pega response: User current specification of the upgrade type as "zero-downtime" without setting the "targetRuleSchema" and "targetDataSchema" is leading to the upgrade failure.
For comprehensive instructions on the upgrade process, please refer to the following link: https://github.com/pegasystems/pega-helm-charts/blob/master/docs/upgrading-pega-deployment-zero-downtime.md.
-
Additionally, you will need to create the necessary users and assign the required privileges for the upgrade, as outlined here: https://docs.pega.com/bundle/platform/page/platform/install/db/k8s-configure-oracle-install.html#configure-oracle-user-permissions.
-
-
Please ensure that you follow all the recommendations above and rerun the upgrade, then inform us of the outcome.
-
Note: It is advisable to have a dedicated deployment user instead of using the "system" user.
An additional issue was encountered relating to index creation, script is trying to create a index which already exists in the existing data schema and i have verified it has been created in the new dataschema as well.
Pega response:
Support document addresses an issue related to Oracle databases : https://support.pega.com/support-doc/update-fails-ora-01451-ora-02429-ora-02443-and-ora-00955-sdr-301.
To resolve the problem, you should remove the indexes and primary key from the affected table. The upgrade process will reinstate them
Dropping these indexes and retrying the upgrade is successful
The support ticket was resolved with the below explanation:
Here is our analysis:
User switched to "System" user instead of custom application user for Pega
The SYSTEM user will not be applicable in this case. You will need to adhere to the Upgrade Process as outlined in our documentation.
Please refer to the following link where you will need to create the necessary users and grant the required privileges for the upgrade:
https://docs.pega.com/bundle/platform/page/platform/install/db/k8s-configure-oracle-install.html#configure-oracle-user-permissions
Have you reviewed the ZDT upgrade guide prior to initiating the upgrade? https://github.com/pegasystems/pega-helm-charts/blob/master/docs/upgrading-pega-deployment-zero-downtime.md
Upon reviewing the YAML file, we noticed that the targetRulesSchema and targetDataSchema fields are not set, which are mandatory. User explained their plan was to do a in place upgrade with the existing schema that's the reason they didn't provide the new schema names.
The support ticket was resolved with the below explanation:
Here is our analysis:
User switched to "System" user instead of custom application user for Pega
The SYSTEM user will not be applicable in this case. You will need to adhere to the Upgrade Process as outlined in our documentation.
Please refer to the following link where you will need to create the necessary users and grant the required privileges for the upgrade:
https://docs.pega.com/bundle/platform/page/platform/install/db/k8s-configure-oracle-install.html#configure-oracle-user-permissions
Have you reviewed the ZDT upgrade guide prior to initiating the upgrade? https://github.com/pegasystems/pega-helm-charts/blob/master/docs/upgrading-pega-deployment-zero-downtime.md
Upon reviewing the YAML file, we noticed that the targetRulesSchema and targetDataSchema fields are not set, which are mandatory. User explained their plan was to do a in place upgrade with the existing schema that's the reason they didn't provide the new schema names.
Pega response: User current specification of the upgrade type as "zero-downtime" without setting the "targetRuleSchema" and "targetDataSchema" is leading to the upgrade failure.
For comprehensive instructions on the upgrade process, please refer to the following link: https://github.com/pegasystems/pega-helm-charts/blob/master/docs/upgrading-pega-deployment-zero-downtime.md.
Additionally, you will need to create the necessary users and assign the required privileges for the upgrade, as outlined here: https://docs.pega.com/bundle/platform/page/platform/install/db/k8s-configure-oracle-install.html#configure-oracle-user-permissions.
Please ensure that you follow all the recommendations above and rerun the upgrade, then inform us of the outcome.
Note: It is advisable to have a dedicated deployment user instead of using the "system" user.
An additional issue was encountered relating to index creation, script is trying to create a index which already exists in the existing data schema and i have verified it has been created in the new dataschema as well.
Pega response:
Support document addresses an issue related to Oracle databases : https://support.pega.com/support-doc/update-fails-ora-01451-ora-02429-ora-02443-and-ora-00955-sdr-301.
To resolve the problem, you should remove the indexes and primary key from the affected table. The upgrade process will reinstate them
Dropping these indexes and retrying the upgrade is successful