Discussion
Coforge
US
Last activity: 6 Apr 2018 19:26 EDT
Sample Schema in Different DataBase
Hi, we are upgrading from v5.5 to 7.1.9 and CSI FW upgrade to 7.1.4.
Regarding importing sample application jar testing sample application, we are seeing following issues,
In sample application some important data pages (like D_ContactList, D_Contact_Policies ) refers report definitions in which there are class joins between PegaIns-Interface-*, PegaApp-Interface-*, PegaCA-Interface-* . Looks like classes PegaCA-, PegaIns- database tables are mapped to PegaData but PegaApp- classes are mapped to Sample schema (different database) and so report definitions are failing with error ( Error:** ** Reports with classes mapped to different databases is not supported, ) ,
so is this expected behavior ? or for pega 7 all schemas including Sample should be there in only one database ..?
Please Note: In existing v5.5 application we had separate Database and Schema for Sample and separate database for PegaRules, For upgrade to v7 also we are following similar structure where GISample database will have Sample Schema and GIPRPC database have PegaData and PegaRules schema.
**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.
Pegasystems Inc.
Yes, the Report Definitions will not work if classes are mapped to different databases.
With respect to frameworks (7.1.4), 'Sample' is a part of PegaDATA schema which is a jar that loads the rules. Ideally the sample tables should not be referred in the application as they are meant for sample.
In this case, probably you can try moving the tables to PegaDATA schema and remap the classes. Hope this works.
Coforge
US
Hi Natan thanks for your reply.
Actually with respect to CSi sample it is giving lot of issues,
1> In CSI distribution they gave Drop scripts to drop sample tables and we used it to drop tables
2> Now when we are trying to import Sample jar .. it is not generating any ddl's at all.... and it is failing to import data because no tables
3> We verified ddls generated as part of CSI application jar, in that scripts i see same sample tables names created in PegaData schema, but not all tables, like some important tables pa_account, pa_address are missing.
Now my confusing is which jar should have generated tables related to sample application .. is it CSi app jar or CSI sample jar ? and what to do with this missing tables.... please help
Scotiabank
CA
The Sample jar, which you are saying not generating any DDL at all, does it contains the DADT instances (Data-Admin-DB-Table) for those classes. Generally during RAP import pega creates tables if it is not present in DB but present in DADT mapping.