Skip to main content

This content is closed to future replies and is no longer being maintained or updated.
Links may no longer function. If you have a similar request, please write a new post.

Discussion

 Vigneshwaran Aravindhan (VigneshAravind)
Cognizant
Senior Technology Architect
Cognizant
IN
VigneshAravind Member since 2007 29 posts
Cognizant
Posted: May 4, 2016
Last activity: Apr 6, 2018
Posted: 4 May 2016 2:33 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

ORA-01749 : you may not GRANT/REVOKE privileges to/from yourself

We were performing the third step of a split schema upgrade (6.2.1 to 7.1.9) "Generate and Apply Rules Schema Objects".

We have received the following error while running the migrate.sh in a Unix + Oracle Setup. Kindly post your suggestions.

[java] 2016-05-03 04:41:34,429 ( SQLLoader) INFO - GRANT ALL ON
[java] 2016-05-03 04:41:34,436 ( SQLLoader) INFO - File: oracledate00550.sql
[java] 2016-05-03 04:41:34,437 ( SQLLoader) INFO - GRANT INSERT ON
[java] 2016-05-03 04:41:34,443 ( SQLLoader) WARNING - Failed to execute SQL in file oracledate00550.sql
[java]
[java] java.sql.SQLSyntaxErrorException: ORA-01749: you may not GRANT/REVOKE privileges to/from yourself
[java]
[java] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
[java] at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
[java] at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
[java] at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
[java] at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
[java] at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
[java] at oracle.jdbc.driver.T4CStatement.doOall8(T4CStatement.java:193)
[java] at oracle.jdbc.driver.T4CStatement.executeForRows(T4CStatement.java:1033)
[java] at oracle.jdbc.driver.OracleStatement.doExecuteWithTimeout(OracleStatement.java:1329)
[java] at oracle.jdbc.driver.OracleStatement.executeInternal(OracleStatement.java:1909)
[java] at oracle.jdbc.driver.OracleStatement.execute(OracleStatement.java:1871)
[java] at oracle.jdbc.driver.OracleStatementWrapper.execute(OracleStatementWrapper.java:318)
[java] at com.pega.pegarules.install.SQLLoader.main(SQLLoader.java:266)
[java] 2016-05-03 04:41:34,445 ( SQLLoader) WARNING - Statement: GRANT insert ON PEGA_APP.pr_sys_updatescache TO pega_user
[java] Exception in thread "main" com.pega.pegarules.install.SQLLoader$SQLLoaderException:
[java] ********************************************************************************
[java]
[java] Encountered a SQL Exception, clean schema before running again.
[java]
[java] ********************************************************************************
[java] at com.pega.pegarules.install.SQLLoader.fail(SQLLoader.java:359)
[java] at com.pega.pegarules.install.SQLLoader.main(SQLLoader.java:316)



**Moderation Team has archived post**


This post has been archived for educational purposes. Contents and links will no longer be updated. If you have the same/similar question, please write a new post.

To see attachments, please log in.
Updates

Posted: 8 years ago
Updated: 8 years ago
Posted: 4 May 2016 2:51 EDT
Updated: 4 May 2016 3:20 EDT
Vigneshwaran Aravindhan (VigneshAravind)
Cognizant
Senior Technology Architect
Cognizant
IN

This issue could occur if the migrateSystem.properties is mis-configured.
Among the 4 schema properties found in the migrateSystem.properties 3 of them require a value for
performing a Generate and Apply Rules Schema Objects

  • pega.source.rules.schema=PEGA_NEW
  • pega.source.data.schema=(Leave it blank)
  • pega.target.rules.schema=PEGA_NEW
  • pega.target.data.schema=PEGA_OLD

In our case we had forgot to provide a value for pega.target.rules.schema resulting in ORA-01749.

According to this article https://community.pega.com/support/support-articles/upgrade-fails-db-permissions this 

issue could occur if the deployment user does not have all the privileges listed in the upgrade guide 

however this was not our scenario.

To see attachments, please log in.
Posted: 8 years ago
Posted: 26 Jan 2017 11:03 EST
Surendra Babu Mamillapalli (SURENDRA)
Mphasis

Mphasis
US

VigneshAravind: In the above reply you have specified pega.source.rules.schema=PEGA_NEW

the upgrade doucment tells the value of source should be PEGA_OLD. Are you sure about the source schema to be new ?

 

To see attachments, please log in.

Related content:

We'd prefer it if you saw us at our best.

Pega Collaboration Center has detected you are using a browser which may prevent you from experiencing the site as intended. To improve your experience, please update your browser.

Close Deprecation Notice