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

 Bidyun Kundu (Bidyun) LTIMindtree
LTIMindtree
SA
Bidyun Member since 2015 31 posts
LTIMindtree
Posted: Aug 12, 2016
Last activity: Apr 6, 2018
Posted: 12 Aug 2016 10:14 EDT
Last activity: 6 Apr 2018 19:26 EDT
Closed

Getting error Schema does not exist for 7.2.1 Update

Hi,

We are updating our application from 72 to 721 and for that we have created a new Rules schema in the same database instance.

I have checked from Oracle Entreprise manager and the newly created schema is available and is in 'online' mode.

But whenever I am running the migrate.bat script, I am geeting an error "NewRulesSchema" does not exist in this database.

We have verified and cross checked the migratesystem.properties file a number of time but no luck.

Any idea on what might have gone wrong?

Regards,

Bidyun



**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
Posted: 12 Aug 2016 16:01 EDT
Bidyun Kundu (Bidyun) LTIMindtree
LTIMindtree
SA

 

It would be really great if anyone can share their experiences in this. 

We had two schemas RULES72 and DATA72 ie a split schema for Pega 7.2

Now for the update we have created a new Rules schema RULES721 

But whenever the migrate.bat script is executed an error is thrown which says Schema 'RULES721' doesn't exist in this database. 

We have a single database instance PEGA72 and are using the same deployment user credentials for the source and target schema in the migrate script.

 

To see attachments, please log in.
Posted: 8 years ago
Posted: 15 Aug 2016 14:29 EDT
Bidyun Kundu (Bidyun) LTIMindtree
LTIMindtree
SA
The Deployment User running the scripts has the previous RULES72 schema as the 'Default Tablespace'. And the new schema name is RULES721. Can this be a probable reason that the deployment user cannot access the newly created rules schema for migration?
To see attachments, please log in.
Posted: 8 years ago
Posted: 15 Aug 2016 21:13 EDT
John Peterson (JohnPeterson) PEGA Senior Director of Cloud Engineering
Pegasystems Inc.
US

Make sure your deployment user has the required privleges and roles to perform a deployment of PRPC.  The Pega7 deployment guide has them itemized for reference.   Also please check to make sure you are connecting to the same system that your Oracle Enterprise Manager is connected to.   It is possible the user/schema you created is not on the same system you are trying to update.

To see attachments, please log in.
Posted: 8 years ago
Posted: 16 Aug 2016 6:56 EDT
Bidyun Kundu (Bidyun) LTIMindtree
LTIMindtree
SA

Hi John,

Thanks for the response. yes, the deployment user indeed has all the requisite privileges and it is the same one which we used for the Installation of the 72 platform. We are connecting with the same system the Oracle Enterprise Manager is connected to.

The tablespaces list in OEM shows the three schemas- RULES72 and DATA72 (Pega72) and the newly created RULES721 (for rules migration in 721).

To see attachments, please log in.

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