move DW database from one db2 server to another db2 server
Hi,
We need to move only the DW database from one db2 server to another one, as there was some mistake in the DW JDBC configuration.
JTS/QM/RM databases are in db2 server1. But somebody pointed the DW database to db2 server2, and mixed up with Rational Insight data. DW database in db2 server1 contains very old data we don't need. DW database in db2 server2 contains Rational Insight data along with data from db2 server1.
We need to change the JDBC Location in Server Administration -> Reports -> Data Warehouse Connection
Can we just drop DW in db2 server1 and create an empty DW in db2 server1 ?(as we don't want Rational Insight data mixed with this DW data)
Or we still need to move old DW to db2 server1 with old Rational Insight data ?
Any ideas would be appreciated?
Regards
Sonic
We need to move only the DW database from one db2 server to another one, as there was some mistake in the DW JDBC configuration.
JTS/QM/RM databases are in db2 server1. But somebody pointed the DW database to db2 server2, and mixed up with Rational Insight data. DW database in db2 server1 contains very old data we don't need. DW database in db2 server2 contains Rational Insight data along with data from db2 server1.
We need to change the JDBC Location in Server Administration -> Reports -> Data Warehouse Connection
from //hostname1:60000/RIDW:user=db2inst1;password={password}; to //hostname2:60000/DW:user=db2inst1;password={password};As far as I know, the data from DW database comes from etl jobs.
Can we just drop DW in db2 server1 and create an empty DW in db2 server1 ?(as we don't want Rational Insight data mixed with this DW data)
Or we still need to move old DW to db2 server1 with old Rational Insight data ?
Any ideas would be appreciated?
Regards
Sonic
Accepted answer
Hello Sonic,
you can create an empty data warehouse on db2 server1and repopulate it with the CLM data collection job.
The first run will be a full load (that is 12h work item job that you noticed) and will fully repopulate the operational data store part of the data warehouse.
You will anyway lose the metrics part, as this is not recreated (this is used for reports based on metrics like for example burndown charts).
Migration jobs are probably due to the fact that this was the first run against an empty data warehouse.
Best Regards,
Francesco Chiossi
you can create an empty data warehouse on db2 server1and repopulate it with the CLM data collection job.
The first run will be a full load (that is 12h work item job that you noticed) and will fully repopulate the operational data store part of the data warehouse.
You will anyway lose the metrics part, as this is not recreated (this is used for reports based on metrics like for example burndown charts).
Migration jobs are probably due to the fact that this was the first run against an empty data warehouse.
Best Regards,
Francesco Chiossi