Reports

Creating, running, and viewing reports.
Checking the SQL code that was executed at report runtime
  1. Start IBM® Cognos® Connection and click Administration.
  2. Click Configuration.
  3. Click Dispatchers and Services.
  4. Click the listed dispatcher, for example http://localhost:9080/insight.
  5. Locate Report Services and click Set Properties.
  6. Click Settings.
  7. Select Yes for Logging Audit the native query for report service.
  8. Run a report.
  9. Go to log directory of IBM Rational® InsightCognos installation. The default location is C:/Program Files/IBM/Rational Insight/cognos/logs.
  10. Sort the files according to the time they were modified, and open the latest file of the log named cogserver.log
  11. Find the select clauses in it. These are the SQL statements that were executed against database at report runtime.
Verifying that Rational Insight 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.
  1. Make sure that Rational Insight Data Service is available.
  2. 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.
  3. Make sure the system ODBC is pointing to the correct XML data configuration file.
  4. Make sure the data source on Cognos Connection is connected.
  5. Make sure the processing model of the query of the report is set to Limited Local.
  6. Activate the debug model of jdbc, odbc, and cognos logs and check the log:
    • Rational Insight 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 Insight ODBC log

      Open the registry editor, find the key: HKEY_LOCAL_MACHINE>SOFTWARE>ODBC>ODBCINST.INI>IBM Rational Insight 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 [rational_insight_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 IBM Rational Insight 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:
  1. Start IBM Cognos Report Studio and open the chart source query.
  2. 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>) )
  3. Save your work and close IBM Cognos Report Studio.
Linux 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
  1. Check the odbcinst.ini file:
    1. Open the odbcinst.ini file in a text editor.
    2. Go to the [IBM Rational Insight XML ODBC Driver] slot.
    3. Make sure the Driver property points to the correct file path of libratlxml.so
  2. Check the odbc.ini file:
    1. Open the odbc.ini file in a text editor.
    2. Make sure the desired system DSN exists and the value of its Driver property is IBM Rational Insight XML ODBC Driver. If the DSN does not exist, add it as shown in the example:
      [ClearCase]
         Driver = IBM Rational Insight XML ODBC Driver
         DataSource = ClearCase
         Description = A DSN example
         Configuration = /opt/ibm/RationalInsight/dataconfig/Configuration/clearcase.xdc
  3. Verify the JVM path
    1. On the console, run the export command.
    2. Make sure the variable "LD_LIBRARY_PATH" includes the path of IBM Java™ Virtual Machine carried by IBM Rational Insight.An example is /opt/ibm/RationalInsight/AppServer/java/jre/bin;/usr/local/lib.
    3. Make sure the variable "PATH" includes the path of IBM Java Virtual Machine carried by IBM Rational Insight. An example is /opt/ibm/RationalInsight/AppServer/java/jre/bin/classic.

Feedback