This page explains how to synchronize the CAST Databases triplet. This is needed when reproducing an issue that is reported by a user on their environment.
Release | Yes/No |
---|---|
8.3.x | |
8.2.x | |
8.1.x | |
8.0.x | |
7.3.x |
RDBMS | Yes/No |
---|---|
Oracle Server | |
Microsoft SQL Server | |
CSS2 |
Please note: The below steps are shown for the CAST Storage Service database.
For the Oracle database, substitute the tables:
- cms_inf_store_oracle for cms_inf_store_css
- cms_inf_ora_localdb for cms_inf_css_localdb
- cms_inf_ora_centraldb for cms_inf_css_centraldb
For the SQL Server database, substitute the tables:
- cms_inf_store_sqlserver for cms_inf_store_css
- cms_inf_sqlsrv_localdb for cms_inf_css_localdb
- cms_inf_sqlsrv_centraldb for cms_inf_css_centraldb
Perform the following steps:
- Import management base (Management Service database), knowledge base (Analysis Service database), central schema (Dashboard Service database) to the Support server. For this refer to the following to the following page CSS Tools - Restore - Error - Failed to load main class com.castsoftware.cssadmin.cli.BackupSchema
- Change customer's host and port to your server's host (NEWHOST) and port.
Identify the ID of customer host and port first.
select * from <MNGT_schema>.CMS_INF_STORE_CSS
For example - the ID below is 13620 and will be used in the next step:
select * from test_tcc_mngt.CMS_INF_STORE_CSS --13620;"2016-09-29 12:56:00.67";"localhost:2280 on CastStorageService";0;"operator";"CRYPTED2:90B1A6EC1618661401B724DB5AC34595";"localhost";2280
Change customer's host and port to your server's host (NEWHOST) and port next using the ID found above.
UPDATE <MNGT_schema>.cms_inf_store_css SET host = 'NEWHOST', password='CRYPTED2:90B1A6EC1618661401B724DB5AC34595', port=2280, object_name = '<NEWHOST>' WHERE object_id = <id>
For example:
UPDATE test_tcc_mngt.cms_inf_store_css SET host = 'css', password='CRYPTED2:90B1A6EC1618661401B724DB5AC34595', port=2280, object_name = 'css' WHERE object_id = 13620
- Check and change local schema.
- Identify the KB_ID in the Mngt database CMS_INF_CSS_LocalDB. There are two ways of doing this, by running the following queries.
Run the following query If you know the name of the application name.
SELECT object_name, localdb_id FROM distribution2_mngt.cms_portf_application WHERE object_name = <YOUR APPLICATION NAME>
For example
SELECT object_name, localdb_id FROM distribution2_mngt.cms_portf_application WHERE object_name = 'MyApplication1' --"MyApplication1";13627 --Here the KB_ID = 13627
Run the following query If you know the name of the local database.
SELECT * FROM <MNGT_schema>.cms_inf_css_localdb WHERE object_name = 'db_local'
For example
SELECT * FROM test_tcc_mngt.cms_inf_css_localdb WHERE object_name = 'test_tcc_local' --13627;"2016-09-29 12:56:00.67";"test_tcc_local";"8.1.0.1";;13620;1485767932;"";0
Update the table CMS_INF_CSS_LocalDB with the new KB name by running the following query.
UPDATE <MNGT_schema>.cms_inf_css_localdb SET object_name= 'new_local_schema_name' WHERE object_id = <kb_id>
For example:
UPDATE test_tcc_mngt.cms_inf_css_localdb SET object_name= 'new_local_schema_name' WHERE object_id = 13627
- Identify the KB_ID in the Mngt database CMS_INF_CSS_LocalDB. There are two ways of doing this, by running the following queries.
Check and change central schema.
Identify the Central ID in the Mngt database CMS_INF_CSS_CentralDB by running the following query:
SELECT * FROM <MNGT_schema>.cms_inf_css_centraldb WHERE object_name = 'db_central'
For example:
SELECT * FROM test_tcc_mngt.cms_inf_css_centraldb WHERE object_name = 'test_tcc_central' --13635;"2016-09-29 12:56:00.67";"test_tcc_central";"8.1.0.1";;13620;1485767947;"";0;"My Corporate";""
Update the table CMS_INF_CSS_CentralDB with the new CB name by running the following query:
UPDATE <MNGT_schema>.cms_inf_css_centraldb SET object_name= 'new_central_schema_name' WHERE object_id = <cb_id>
For example:
UPDATE test_tcc_mngt.cms_inf_css_centraldb SET object_name= 'new_central_schema_name' WHERE object_id = 13635