Troubleshooting
Problem
At times, it may be necessary to check if the Microsoft® ODBC Driver functions outside of IBM® Rational® RequisitePro®. This can help isolate the cause of RequisitePro Oracle® errors.
Resolving The Problem
Instructions for Windows XP/Windows 2003 Server (it's slightly different on Windows NT)
Go to >Start (>Settings) >Control Panel >Administrative Tools >Data Sources (ODBC).
Choose tab 'System DSN'.
Click Add and scroll down to Microsoft ODBC Driver for Oracle.
Highlight it and click Finish.
The Microsoft ODBC Driver for Oracle Setup dialog comes up. Enter the following information.
Data Source Name: <any name)
Description: <any description>
User Name: <Oracle ReqPro user>
Server: <service alias name>
Click OK twice.
Right-click on Desktop. Go to New >Text Document. A text document will appear on the desktop. Rename the file with extension *.udl.
NOTE: Microsoft Access needs to be installed on the machine so that the file extension can be changed to *.udl!
Click YES when the warning "If you change a filename extension, the file may become unusable. Are you sure you want to change it?" appears.
Double-click on the file on the desktop. The Data Link Properties dialog comes up. Go to the tab Connection. Specify the source of data (browse for the Data Source Name that has been created), enter username and password and click on Test Connection.
If the test fails, you can try to re-install the Oracle client or the Microsoft ODBC driver or contact Microsoft. This test is to check if the Microsoft ODBC driver works outside of RequisitePro. If it fails, there is a problem with the driver itself, which would require assistance from the product vendor. Once the connection succeeds, IBM Rational Support will then be able to assist further if there are additional problems.
Was this topic helpful?
Document Information
Modified date:
16 June 2018
UID
swg21134396