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

 Nandhini Nataraj (natan)
PEGA
Principal Software Engineer - Customer Success
Pegasystems Inc.
natan Member since 2012 32 posts
PEGA
Posted: Jun 4, 2015
Last activity: Apr 6, 2018
Posted: 4 Jun 2015 9:11 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

What would be the impact during upgrade, If I customize my system name other than "Pega"

Got "pega!BATCH” not found error displayed during data upgrade and the upgrade failed



**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: 9 years ago
Posted: 5 Jun 2015 2:12 EDT
Murali Krishnan Divakaran (Murali.Krishnan.D)
Labb Ltd
Murali Krishnan Divakaran
Labb Ltd
GB

Looks like system name is customized.

Specify the customized name in system.name property in setupDatabase.properties. If its not specified it will search with default system name thats why its failing.

To see attachments, please log in.
Posted: 9 years ago
Posted: 24 Jun 2015 2:07 EDT
Ashok Kumar Bommisetty (Ashok_Bommisetty)
Areteans Technology

Areteans Technology
IN

Hello natan,

 

If you are upgrading in oracle database and split schema, the record pega!batch is missing saying the table is not found in the database. The problem is with oracle synonyms.  You need to drop private synonyms of the user and rebuild synonmys for the user you are using to run the data upgrade.

 

Please refer to other links below :

https://pdn.pega.com/forums/prpc/integration/nonexistenttableexception

 

Thanks,

Ashok

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