Support Article
Error on importing the AES application bundle
SA-55915
Summary
After performing a new installation of Pega 7.3.1 and Autonomic Event Services (AES) 7.3, Oracle error message displays in the logs. Schema modifications by Pega application are not allowed by the Database Administrators (DBAs). Therefore, a separate Pega connect user is used in the WebLogic Java Database Connectivity (JDBC) connection to access the AES database. The Pega connect user has Data Manipulation Language (DML) privileges on the Pega database objects in the Rules schema and the Data Schema. As a result of this requirement, the user manually generates and applies the Data Definition Language (DDL) for Pega 7.3.1 and AES 7.3. The generateddl.bat script is used to generate the Pega 7.3.1 DDL. The DDL is generated as part of the import of the AES application bundle for AES 7.3. The Pega 7.3.1 DDL and the AES 7.3 DDL are applied before installing the rulebase (executing install.sh) and before installing (importing) the AES application bundle through Oracle SQL*Plus.
The Oracle exception displays during the import of the AES application bundle despite the preparation of the Oracle database (applying the Pega 7.3.1 DDL and the AES 7.3 DDL in advance).
Error Messages
618 [fault (self-tuning)'] [ STANDARD] [ PegaRULES] (nal.access.DBSchemaDDLExecutor) ERROR [email protected] - Error occured while trying to add Index columns for an property
pega.pegarules.pub.database.DatabaseException: Database-General Problem executing SQL to update database schema 1031 42000 ORA-01031: insufficient privileges
DatabaseException caused by prior exception: java.sql.SQLSyntaxErrorException: ORA-01031: insufficient privileges
| SQL Code: 1031 | SQL State: 42000
at com.pega.pegarules.data.internal.access.ExceptionInformation.createAppropriateExceptionDueToDBFailure(ExceptionInformation.java:354) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.ExceptionInformation.createExceptionDueToDBFailure(ExceptionInformation.java:333) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DBSchemaDDLExecutor.executeDBSchemaDDL(DBSchemaDDLExecutor.java:149) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DBSchemaDDLExecutor.executeDBSchemaUpdates(DBSchemaDDLExecutor.java:491) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DBSchemaDDLExecutor.executeDBAddIndexColumns(DBSchemaDDLExecutor.java:262) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DatabaseImpl.executeDBAddIndexColumns(DatabaseImpl.java:3460) ~[prprivate.jar:?]
at com.pega.pegarules.session.internal.mgmt.Executable.executeDBAddIndexColumns(Executable.java:8485) ~[prprivate.jar:?]
com.pegarules.generated.activity.ra_action_savecircumstanceindex_270ca6b67141c1ef0e3d20a38ca6c80d.step6_circum0(ra_action_savecircumstanceindex_270ca6b67141c1ef0e3d20a38ca6c80d.java:787) ~[?:?]
com.pegarules.generated.activity.ra_action_savecircumstanceindex_270ca6b67141c1ef0e3d20a38ca6c80d.perform(ra_action_savecircumstanceindex_270ca6b67141c1ef0e3d20a38ca6c80d.java:165) ~[?:?]
at com.pega.pegarules.session.internal.mgmt.Executable.doActivity(Executable.java:3597) ~[prprivate.jar:?]
at com.pega.pegarules.exec.internal.declare.infengine.ChainingEngineUtilImpl.runActivity(ChainingEngineUtilImpl.java:225) ~[prprivate.jar:?]
at com.pega.pegarules.exec.internal.declare.infengine.TriggerImpl.evaluateNetworks(TriggerImpl.java:307) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DatabaseImpl.performTriggers(DatabaseImpl.java:6686) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.Saver.performTriggers(Saver.java:735) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.Saver.saveDeferred(Saver.java:435) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DatabaseImpl.saveDeferred(DatabaseImpl.java:2735) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DatabaseImpl.saveDeferred(DatabaseImpl.java:8167) ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.BasicDeployDataModel.saveDeferred(BasicDeployDataModel.java:75) ~[prprivate.jar:?]
at com.pega.pegarules.deploy.internal.loaders.SaverLoader.importInstance(SaverLoader.java:669) ~[prprivate.jar:?]
com.pegarules.generated.activity.ra_action_pzimportcomponent_d2e7c47c5a5ed1549c03b34ef0253d0b.step1_circum0(ra_action_pzimportcomponent_d2e7c47c5a5ed1549c03b34ef0253d0b.java:171)com.pegarules.generated.activity.ra_action_pzimportcomponent_d2e7c47c5a5ed1549c03b34ef0253d0b.perform(ra_action_pzimportcomponent_d2e7c47c5a5ed1549c03b34ef0253d0b.java:70) ~[?:?] Caused by: java.sql.SQLSyntaxErrorException: ORA-01031: insufficient privileges
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:450) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:399) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:1059) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:522) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:257) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:587) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:210) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:30) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:931) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1150) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1792) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1745) ~[ojdbc7.jar:127.0.0.1]
at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:334) ~[ojdbc7.jar:127.0.0.1]
at weblogic.jdbc.wrapper.Statement.execute(Statement.java:490) ~[weblogic.server.merged.jar:127.0.0.1]
at com.pega.pegarules.data.internal.access.GenericExecutor.execute(GenericExecutor.java:34) ~[prprivate.jar:?]
at com.pega.pegarules.data.internal.access.DBSchemaDDLExecutor.executeDBSchemaDDL(DBSchemaDDLExecutor.java:141) ~[prprivate.jar:?]
Steps to Reproduce
Install Pega 7.3.1 and AES 7.3 with a connect user which has no DDL privileges on Rules schema and Data Schema.
Root Cause
Two columns which are to be added to the PR_INDEX_CIRCUMSTANCE_DEF table are not present in the DDL. Sufficient privileges are present to apply DDL changes according to the generate DDL. However, users restrict this privilege. Hence, a few SQLs fail. The users have no visibility of the failed SQLs and hence it is difficult to analyse which alter statements failed.
Resolution
- Apply HFix-43015
- Manually add the required columns to the DDL and the PR_INDEX_CIRCUMSTANCE_DEF table
Published August 19, 2019 - Updated October 8, 2020
Have a question? Get answers now.
Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.