It's all about the answers!

Ask a question

How do I move the insight databases?


1
1
Mark Ireland (26125748) | asked Jul 06 '09, 6:42 a.m.
Hi,

How do i go about moving the Insight databases from one server to another?
The question is two fold,

1. Recomeneded move instructions (DB2)
I used db2move etc
2. Where in Insight do I change the database locations?

I have three Db's RICM, RIDW and RIEXP, all seemed to move ok to new server, and I was able to see tables etc on them, but unable to purswade Insight to access them.
Is it the way DB's created? Moved?
Or Insight setup?

Many thanks in advance

Regards

Mark.

2 answers



permanent link
Petroula Pantazopoulos (36612) | answered Jul 08 '09, 3:38 p.m.
JAZZ DEVELOPER
Hi,
The best way to do this is to do a database backup then restore on the intended system.


For the RICM database, you need to modify information about the content store using the "Cognos Configuration" application. Launch it and navigate in the tree to the "Data Access->Content Manager->Content Store" node. In the right pane you can modify the database connectivity information to connect to the correct content store database. Save your changes and re-start WebSphere.

The Insight database connection information needs to be changed on the Cognos BI Server, for the RIDW datasource. Go to IBM Cognos Administration->Configuration->Data Source Connections. Click on the RIDW data source, then click on the properties icon of the RIDW connection. Go to the Connection tab, click on the "edit the connection string" button located next to the "Connection String" text box. Specify the correct DB2 alias information. Click on OK to save your changes. Click on the RIDW connection. This will take you to the pre-defined rptuser signon. Click on the properties icon of the signon, click on the signon tab, then click on the "Edit the Signon" link. In there specify the account information to use to connect to the Insight database. From the datamanager client, locate the Connections node in the tree, then locate the connection profile called "Rational Data Warehouse". Double-click on it, go to the connection details tab and enter the database information in there.

permanent link
Omprakash Thammishety (1461178) | answered Jul 30 '12, 4:26 p.m.
If we backup and restore using db2move command then there will be problem with content store databases (RICM) . For example we have RICM databases in source server in db2inst1 instance then tables will create in DB2INST1 schema by default. If we migrate to RICM database in db2inst2 instance in destination server then still the schema will be with DB2INST1 only. Because of this schema different content store database will not start and its complaints the error as "CM-CFG-5137 Content Manager was unable to complete the initialization of the content store. For more information, review the log file. Before you restart Content Manager, you may need to recreate the content store database or clean it using dbClean_*.sql.  "

Some like below also you can see in the cogserver.log file. "NO ACTIVE CONTENT DATABASE WERE FOUND".

I faced this problem yesterday and I have fixed this problem by creating the same instance on destination server and then restore the database as usual using db2 utility and then its works for me without any problem.

When I change the schema while creating the tables and importing the data then server came up but given errors on few of the reports and when I access IBM cognos administration page then it did not load. Even got the error. I forgot to capture the error.

I don't know how we can restore the content store database from one instance to another instance in different server. If we still restore the databases in different instance then we may have to create old instance ID in db2 users and access the databases using db2 users only. It also work.

My work around is worked for me but if we get the exact procedure to follow for migration then it would be really great help.

Thanks,
Om.

Your answer


Register or to post your answer.


Dashboards and work items are no longer publicly available, so some links may be invalid. We now provide similar information through other means. Learn more here.