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

 Bhushan Patil (BHUSHANPATIL)
AIG
Bhushan Patil
AIG
US
BHUSHANPATIL Member since 2008 51 posts
AIG
Posted: Dec 30, 2015
Last activity: Apr 6, 2018
Posted: 30 Dec 2015 5:26 EST
Last activity: 6 Apr 2018 19:26 EDT
Closed

MSSQL two database; Missing table while migrating from TEMP to actual

We are having mismatch issues for 2 database approach, while moving Rule schema tables back actual DB env.

Database : MSSQL

Pega Version -7.1.8

Prior we did same for DB2 and Oracle(difference customer), we didn’t had issues of missing table etc; but MSSQL looks like some important table are not pull with “migrate.sh”; Configuration is good, don’t have any exception in script execution.

Following tables are missed; do you see concern?

pr_sys_cache_dep

pr_sys_ruleset_index

PR_SYS_APPCACHE_ENTRY

PR_SYS_APPCACHE_SHORTCUT

PR_SYS_RULE_IMPL

PR_ASSEMBLEDCLASSES

PR_DATA_MAP_ENTRIES

PR_SYSGEN_STATIC_CONTENT

PR_SYS_CLASS_ANCESTORS

PR_DATA_PRODUCTS

PR_DATA_RESTORE

PR_SYS_CACHE_ENTRY

PR_SYS_CACHE_IMPL

PR_SYS_APPCACHE_DEP

PR_SYS_APP_RULESET_INDEX

PR_SYS_APP_HIERARCHY_FLAT


**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

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