Question
Citizens Bank
US
Last activity: 20 Sep 2019 3:58 EDT
Schema name changes to custom schema names like RULES1 and DATA1 in 7.1.7 version
We have a request to change the default split schema names (RULES and DATA to APP_RULES and APP_DATA) in the existing application DB.
If anyone made such changes, can you please provide the places to make the schema name changes.
***Edited by Moderator Marissa to update platform capability tags****
Pegasystems Inc.
IN
Hi Sridahr,
If you want to change the schema name in the DB then you can follow the below steps:
- Create new schemas APP_RULES and APP_DATA
- migrate the data from RULES to APP_RULES and from DATA to APP_DATA
- refer the new schemas in the data source of the application server configuration.
Regards,
Vikash
Pegasystems Inc.
US
Are you asking about what changes you need to make on the app server after making the schema name changes on the databases? In WebSphere you would need to update the namespace bindings for the PegaRULES and PegaDATA defaultSchemas.
Also be sure that when you did the rename at the database level you updated the stored procedures, functions, triggers, etc. Most database tools will only rename the signature line and not the references within the body. For example, it would rename the stored procedure DATA.sppr_sys_statusnodes_set to APP_DAA.sppr_sys_statusnodes_set but it would not correct the references within the stored procedure to the DATA.pr_sys_statusnodes table to APP_DATA.pr_sys_statusnodes.
Citizens Bank
US
Thanks for the response!
Just need one more clarification, are the name space binding values to default pega schemas would be enough to refer the new schemas? or do we need to make any additional changes at the Websphere level or any local files?
Coforge Technologies (Erstwhile Incessant Technologies)
GB
All the queries, stored procedure, functions and trigger rules where the schema is referred to be updated.