Using the Rational® Common Reporting XML ODBC driver.
When configuring system DSN, you encounter one of the following
errors: The setup routines for the Rational Common Reporting XML ODBC Driver could not be loaded due to system error
126
- ratlxml_resources ures_openU fail!
- Verify the settings in the Windows® registry:
- Click Start, click Run, type regedit and click OK.
- In the registry, go to My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\IBM® Rational Common Reporting XML ODBC Driver and make sure the Driver and Setup properties point
to the correct file path of ratlxml.dll.
- In the registry, go to My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBCINST.INI\ODBC
Drivers and make sure IBM Rational Common Reporting XML ODBC Driver is found to be installed.
- In the registry, go to My Computer\HKEY_LOCAL_MACHINE\SOFTWARE\ODBC\ODBC.INI\ODBC
Data Sources and make sure the system DSN you are configuring
is using IBM Rational Common Reporting XML ODBC Driver.
- Verify the setting of the JDBC driver path:
- On the desktop, right-click My Computer and click Properties,
- On the System Properties page, click Advanced and click Environment Variables.
- Make sure that $INSTALLDIR\dataconfig\jdk\bin\classic appears at the beginning of the PATH and Path variables of user variables and system variables.
When Testing the Connection of an ODBC data source in IBM Cognos® BI Server, you get the following error: Data name
not found, and no default driver specified
- When you use the helper application of driver manager, e.g., the
isql application of unixODBC, to access a system DSN, 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 Quality Manager
Report Authoring XML ODBC Driver. If the DSN does not exist,
add it as shown in the example:
[RationalQualityManager]
Driver = IBM Rational Common Reporting XML ODBC Driver
DataSource = Rational Quality Manager
Description = A DSN example
Configuration = /opt/ibm//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//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/RationalInsight/AppServer/java/jre/bin/classic.
- If the JDBC driver throws a Premature EOF exception
- Increase the write timeout for the HTTP inbound channel for the
HTTP port for the data service. To do so:
- Determine the server and port for the data service being used
for the collection by looking for the URL in the XML data configuration.
- Open the WebSphere® Application Server administrative console for the WebSphere Application Server instance for the
data service.
- Click .
- Click Rational Common Reporting Server.
- Expand and click
on the Web container transport chains.
- Click the transport chain for the port used by the data service.
- Click the HTTP inbound channel.
- Increase the length of the Write timeout. This determines how
long WAS will wait when attempting to write to a client stream. The
default value is 60 seconds.
- Click OK and click Save directly
to the master configuration.
- Stop and restart the Rational Common ReportingWebSphere Application Server profile.
- If you get a ParseException message
- Make sure the modifiedsince clause in the SQL
query confirm to the time format Like #dd-MMM-yyyy hh:mm:ss
Z#.
- If you get a CRREE2416E message
- Make sure the where clause in the SQL query
contains values with the associated column names in the queried table.
- If you get a CRREE2403E message
- Make sure the where clause in the SQL query
does not contain column names that are not valid for the queried database.
- If you get a CRREE1401E message
- Make sure the data service is accessible and the URL of the resource
group is defined correctly in the XML data configuration file.
- If you get a CRREE1406E message
- Make sure the user name and password of the queried resource group
is correct.
- If you get a HTTP 4XX message in the JDBC log file
- In the XML data configuration file:
- Make sure the user name, password, and URL of the queried resource
group are correct and pass the Test Connection test.
- Make sure the URL and schema of the resources being used are correct.
- Open the data mapping table editor being used and click Modify an existing data mapping template. Make sure there
are no errors.
- If you get a HTTP 5XX message in the JDBC log file
- Verify your network connection status. Make sure the network configuation
in the data service server is correct. For more information, see the
data service server log.