critical issue in RCR! HELP!!
RCR cannot support chinese words. After ETL, all chinese words in RQM is messy code in DB2 ODS table so RCR BI server cannot show normal chinese words.
For example, I have one project area name in Chinese word in RQM. After ETL, I run a report in RCR and the project name is not chinese word, but messy code. So, I checked the DB2 ODS table "PROJECT" and find the project area name is messy code that I cannot read. I am chinese TS by the way.
I am sure I followed the procedure to install the RCR - automatically install cognus, automatically install RIDW. Actually, I spent days to verify this issue by installing it for a couple of times.
If I use live data getting data from RQM server directly, the chinese words show up as normal which is good.
For example, I have one project area name in Chinese word in RQM. After ETL, I run a report in RCR and the project name is not chinese word, but messy code. So, I checked the DB2 ODS table "PROJECT" and find the project area name is messy code that I cannot read. I am chinese TS by the way.
I am sure I followed the procedure to install the RCR - automatically install cognus, automatically install RIDW. Actually, I spent days to verify this issue by installing it for a couple of times.
If I use live data getting data from RQM server directly, the chinese words show up as normal which is good.
One answer
Hi,
There is a new help topic for solving this problem.
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/index.jsp
The topic is called:
Configuring the ODBC connections to use the Unicode data standard
Here is the content of the help topic:
If the database is configured for Unicode, administrators can ensure that the data displays properly by changing the ODBC connections to use the Unicode data standard.
About this task
To configure the Rational Quality Manager live connection and data warehouse connection:
1. To configure the Rational Quality Manager live connection:
1. Open the Cognos Web application at http://server:port/insight/servlet/dispatch.
2. Open the Cognos administration page by clicking Launch > IBM Cognos Administration.
3. Click the Configuration tab.
4. In the left pane, click Data Source Connections.
5. Under the Name column, click RQM.
6. Under the Actions column, click Set Properties.
7. Click the Connection tab, and then click Edit the connection string icon.
8. In the Edit the connection string - ODBC page, select Unicode ODBC.
9. Click OK, and then click OK again
2. To configure the Rational Quality Manager data warehouse connection:
1. To return to the data source connections, click Cognos above the Name column.
2. Under the Name column, click RQM (ETL).
3. Repeat f through i in step 1.
Hopefully this will solve your problem too.
Mark
There is a new help topic for solving this problem.
http://publib.boulder.ibm.com/infocenter/rqmhelp/v2r0/index.jsp
The topic is called:
Configuring the ODBC connections to use the Unicode data standard
Here is the content of the help topic:
If the database is configured for Unicode, administrators can ensure that the data displays properly by changing the ODBC connections to use the Unicode data standard.
About this task
To configure the Rational Quality Manager live connection and data warehouse connection:
1. To configure the Rational Quality Manager live connection:
1. Open the Cognos Web application at http://server:port/insight/servlet/dispatch.
2. Open the Cognos administration page by clicking Launch > IBM Cognos Administration.
3. Click the Configuration tab.
4. In the left pane, click Data Source Connections.
5. Under the Name column, click RQM.
6. Under the Actions column, click Set Properties.
7. Click the Connection tab, and then click Edit the connection string icon.
8. In the Edit the connection string - ODBC page, select Unicode ODBC.
9. Click OK, and then click OK again
2. To configure the Rational Quality Manager data warehouse connection:
1. To return to the data source connections, click Cognos above the Name column.
2. Under the Name column, click RQM (ETL).
3. Repeat f through i in step 1.
Hopefully this will solve your problem too.
Mark