Creating, running, and viewing reports.
- Checking the SQL code that was executed at report runtime
- Start IBM® Cognos® Connection and click Administration.
- Click Configuration.
- Click Dispatchers and Services.
- Click the listed dispatcher, for example http://localhost:9080/RCPR.
- Locate Report Services and click Set Properties.
- Click Settings.
- Check the item to ‘Yes': Logging Audit the native query for
report service
- Run a report.
- Go to log directory of Rational® Common ReportingCognos installation.
The default location is C:/Program Files/IBM/Rational Common
Reporting/cognos/logs.
- Sort the files according to the time they were modified, and open
the latest file of the log named cogserver.log
- Find the select clauses in it. These are the
SQL statements that were executed against database at report runtime.
- Verifying that Rational Common Reporting is getting the data and delivering it to the report
Note: The following recommendation applies to only to operational
reports from live data. The process must not be followed for reports
generated from the data in the data warehouse.
- Make sure the XML data configuration file is the correct one for
live reporting and is configured to the correct data service. Make
sure that the authentication type matches data service deployment.
- Make sure the system ODBC is pointing to the correct XML data
configuration file.
- Make sure the data source on Cognos Connection is connected.
- Make sure the processing model of the query of the report is set
to Limited Local.
- Activate the debug model of jdbc, odbc, and cognos logs and check
the log:
- Rational Common Reporting JDBC log default path of JDBC driver's log is (Window
for example):
The default path of the logs are:
- when testing data in FM: {user.home}\logs\ri_jdbc.log
- when running reports in QueryStudio or ReportStudio: C:\WINDOWS\system32\config\systemprofile\logs\ri_jdbc.log
The first time the log is generated, a file named log4j.properties
is copied to that folder. The default log level is info, change it
to debug if you need to.
- Rational Common Reporting ODBC log
Open the registry editor, find the key: HKEY_LOCAL_MACHINE>SOFTWARE>ODBC>ODBCINST.INI>IBM Rational Common
Reporting XML ODBC Driver, and add a string value to it:
where name is debug and value is the folder where the odbc log file should be put.
- Cognos ODBC log
In the installation directory
[rationalcommonreporting_installation_directory]/cognos/bin, locate the file cogdmod.ini, remove the comment before [TRACE]
and add lines like this:
[TRACE] output=C:\cognos.log data=yes
- Removing broken lines from line chart reports
- To optimize space, zero counts are not stored in the fact tables
of the Rational Common Reporting data warehouse. If your chart has a dimension value which
has no data, the line chart will have a broken line. To remove the
broken line:
- Start IBM Cognos Report Studio and open the chart source
query.
- Create a new data item and add the following lines of code to
replace the null value with a zero count:
IF ( <measure> is null ) THEN
( 0 )
ELSE
( total(<measure>) )
- Save your work and close IBM Cognos Report Studio.
When viewing a report in Web browser, which accesses IBM Cognos BI Server, you get the following error: Data name
not found, and no default driver specified
- Check the odbcinst.ini file:
- Open the odbcinst.ini file in a text editor.
- Go to the [Rational Common Reporting XML ODBC Driver] slot.
- Make sure the Driver property points to the
correct file path of libratlxml.so
- Check the odbc.ini file:
- Open the odbc.ini file in a text editor.
- Make sure the desired system DSN exists and the value of its Driver property is IBM Rational Common Reporting
XML ODBC Driver. If the DSN does not exist, add it as shown
in the example, but substitute your product:
[RationalQualityManager]
Driver = Rational Common Reporting XML ODBC Driver
DataSource = RationalQualityManager
Description = A DSN example
Configuration = /opt/ibm/Rational Common Reporting/dataconfig/Configuration/rationalqualitymanager.xdc
- Verify the JVM path
- On the console, run the export command.
- Make sure the variable "LD_LIBRARY_PATH" includes the path of IBM Java™ Virtual Machine carried by Rational Common Reporting .An example is /opt/ibm/Rational Common Reporting/AppServer/java/jre/bin;/usr/local/lib.
- Make sure the variable "PATH" includes the path of IBM Java Virtual Machine carried by Rational Common Reporting. An example is /opt/ibm/Rational Common Reporting/AppServer/java/jre/bin/classic.