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.

Question

 Prashanth Sheela (PrashanthS1006)
Infosys
IN
PrashanthS1006 Member since 2017 6 posts
Posted: Jun 28, 2019
Last activity: Jul 17, 2019
Posted: 28 Jun 2019 7:24 EDT
Last activity: 17 Jul 2019 7:24 EDT
Closed
Solved

ORA-00904: "PXSAVEDATETIME": invalid identifier

While executng the upgrade.sh with 8.2 getting below errors please help me here, admin user has proper rights.

Show More

While executng the upgrade.sh with 8.2 getting below errors please help me here, admin user has proper rights.

[java] 2019-06-28 06:14:34,348 [ main] [ ] [ ] [ ] (y.internal.PRRuleMgmtUtilsImpl) INFO - rule-o
bj-class.zip is v6 Archive
[java] Jun 28, 2019 6:14:36 AM com.pega.pegarules.internal.bootstrap.PRBootstrap
[java] SEVERE: Problem during method invocation (main)
[java] com.pega.pegarules.pub.PRException: PRException
[java] From: (unknown)
[java] at com.pega.pegarules.deploy.internal.archive.importer.synchronization.AppBundleSynchronizer.performSynchronization(AppBundleSynchronizer.java:74)
[java] at com.pega.pegarules.deploy.internal.archive.importer.ArchiveImporterAbstract.importArchive(ArchiveImporterAbstract.java:45)
[java] at com.pega.pegarules.deploy.internal.archive.importer.ArchiveImporterAbstract.importArchive(ArchiveImporterAbstract.java:27)
[java] at com.pega.pegarules.deploy.internal.archive.importer.Upgrader.handleArchive(Upgrader.java:184)
[java] at com.pega.pegarules.deploy.internal.archive.importer.AppBundleHandler.deploy(AppBundleHandler.java:92)
[java] at com.pega.pegarules.deploy.internal.archive.importer.Upgrader.runUpgrade(Upgrader.java:72)
[java] at com.pega.pegarules.deploy.external.util.UpgradeUtil.main(UpgradeUtil.java:69)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke0(Native Method)
[java] at sun.reflect.NativeMethodAccessorImpl.invoke(NativeMethodAccessorImpl.java:90)
[java] at sun.reflect.DelegatingMethodAccessorImpl.invoke(DelegatingMethodAccessorImpl.java:55)
[java] at java.lang.reflect.Method.invoke(Method.java:508)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethod(PRBootstrap.java:381)
[java] at com.pega.pegarules.internal.bootstrap.PRBootstrap.invokeMethodPropagatingThrowable(PRBootstrap.java:422)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethodPropagatingThrowable(AppServerBridgeToPega.java:224)
[java] at com.pega.pegarules.boot.internal.extbridge.AppServerBridgeToPega.invokeMethod(AppServerBridgeToPega.java:273)
[java] at com.pega.pegarules.pub.PegaRULES.main(PegaRULES.java:85)
[java] Caused by: com.pega.pegarules.pub.database.DatabaseException: Database-General ORA-00904: "PXSAVEDATETIME": invalid identifier
[java] 904 42000 ORA-00904: "PXSAVEDATETIME": invalid identifier
[java]
[java] DatabaseException caused by prior exception: java.sql.SQLSyntaxErrorException: ORA-00904: "PXSAVEDATETIME": invalid identifier
[java]
[java] | SQL Code: 904 | SQL State: 42000


Show Less
To see attachments, please log in.
Pega Platform
System Administration
Installation and Deployment
Updates

Accepted Solution

Posted: 5 years ago
Posted: 17 Jul 2019 5:09 EDT
Prashanth Sheela (PrashanthS1006)
Infosys
IN

The issue has been resolved, below are the changes made.

 

Seems the issue occurred because we didn’t apply the DDL and also kept the below parameter to true in setupdatabase.properties file.

bypass.pega.schema=true

 

bypass.pega.schema

To see attachments, please log in.
Posted: 5 years ago
Posted: 3 Jul 2019 11:45 EDT
Laurence Brannigan (LaurenceB_GCS)
PEGA
Senior Software Solutions Engineer
PEG
GB

Do you have the rest of the exception?

I can see the caused by block but not the java stack I'd normally except to accompany it.

Does it show the SQL which is causing the problem? And if so does this table contain a column called PXSAVEDATETIME?

 

To see attachments, please log in.

Accepted Solution

Posted: 5 years ago
Posted: 17 Jul 2019 5:09 EDT
Prashanth Sheela (PrashanthS1006)
Infosys
IN

The issue has been resolved, below are the changes made.

 

Seems the issue occurred because we didn’t apply the DDL and also kept the below parameter to true in setupdatabase.properties file.

bypass.pega.schema=true

 

bypass.pega.schema

To see attachments, please log in.

Related content:

Discussion

pyCommitError.** ** ORA-00904: "INPUTS"."SERVICEID#1":invalid identifier

Question Solved

Getting ORA-00904: invalid identifier error while running generateddl.sh

Question

ORA-00904: "PEGADATA"."PR_READ_FROM_STREAM": invalid identifier

Question

Pega 73 Upgrade Error - There was a problem getting a list: code: 904 SQLState: 42000 Message: ORA-00904: "PXSAVEDATETIME": invalid identifier

Question

pyCommitError: (History-ABC-DEF-Work)** ORA-00904: "QUANTITYCONTRACT": invalid identifier

Question Solved

ORA-00904 PYITEMSTATUS Invalid Identifier

Discussion

ORA-00904 Invalid identifier error when running upgrade.sh for 7.1.9

Question

ORA-00904

Question

Error: ORA-00904 on run report definition

Question

Script for creating the table PCM_CONFIGURATION_BESTPRACTICE throws an error "ORA-00972: identifier is too long".

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