Skip to main content

This content has been archived and is no longer being updated. Links may not function; however, this content may be relevant to outdated versions of the product.

Support Article

Invalid identifier error when running generateddl script

SA-19424

Summary



User is executing the below commands for Pega 7.1.9 and both are giving invalid identifier error. 

>generateddl.sh --action upgrade --dbSchema MY_PEGA_RULES --dbDataSchema MY_PEGA_DATA --outputDirectory /dir_name/.
>generateddl.sh --action upgrade


The same settings in setupDatabase properties file worked well for earlier 7.1.5 system, they used basic command :- generateddl.sh --action upgrade without any dbSchema parameters in 7.1.5. Now for 7.1.9 package, this command is throwing error.

Error Messages



com.pega.pegarules.data.ddl.SchemaGenerator main
SEVERE: Error generating ddl for oracledate, MY_PEGA_RULES
ORA-00904: : invalid identifier
java.sql.SQLSyntaxErrorException: ORA-00904: : invalid identifier
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:445)
at oracle.jdbc.driver.T4CTTIoer.processError(T4CTTIoer.java:396)
at oracle.jdbc.driver.T4C8Oall.processError(T4C8Oall.java:879)
at oracle.jdbc.driver.T4CTTIfun.receive(T4CTTIfun.java:450)
at oracle.jdbc.driver.T4CTTIfun.doRPC(T4CTTIfun.java:192)
at oracle.jdbc.driver.T4C8Oall.doOALL(T4C8Oall.java:531)
at oracle.jdbc.driver.T4CPreparedStatement.doOall8(T4CPreparedStatement.java:207)
at oracle.jdbc.driver.T4CPreparedStatement.executeForDescribe(T4CPreparedStatement.java:884)
at oracle.jdbc.driver.OracleStatement.executeMaybeDescribe(OracleStatement.java:1167)

Steps to Reproduce



Run the generateddl.sh script after updating required properties in setupDatabase.properties file based on the deployment guide:

https://pdn.pega.com/documents/pega-719-platform-update-guide


Root Cause



Execute privileges for DBMS_METADATA package and SELECT_CATALOG_ROLE were not granted to the deployment user.


Resolution



Perform the following local-change:

1. Grant the deployment user with SELECT_CATALOG_ROLE, which is a role, not a privilege.
2. Grant execute privilege for DBMS_METADATA package.

Suggest Edit

Published February 9, 2016 - Updated October 8, 2020

Did you find this content helpful? Yes No

Have a question? Get answers now.

Visit the Collaboration Center to ask questions, engage in discussions, share ideas, and help others.

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

Pega Community 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
Contact us