FAQ
OpenRDA ODBC Driver for UNIX and OpenVMS

 
Q1: When I execute odbcisql or oaisql. I get the following error: print_disclaimer (): rda_config is not set in the ini file: openrda.ini. Unable to print the disclaimer.

Q2: When I try to connect from the oaisql I get the resource not available error. 2

Q3: When try to connect to database using oaisql I get connection exception – server lookup failed error.

Q4: When try to connect to database using oaisql I get the following error – server is down or running on a different port or incorrect IP address.

Q5: How to execute stored procedure that returns the result set.

Q6: We are having a problem building the shared library (using makefile).

Q7: I am not successful in connecting my client to the server. This is the dialogue.

Q8: I would like to setup query on web running Apache Web Server and cgi-bin script.

Q9: When we install your OpenRDA product on our os/2 system (client).

Q10: What is the syntax for a select statement with a date range. For instance, I would like to select all records that have a start date between 10/1/1999 and 12/1/1999. How should the query look?

Q11: OpenRDA server appears to time-out when it is running overnight or over several days. Is this a limitation of the demo copy?

Q12: Is there a way to read the system table "mysysobjects" of ms-access though ODBC and OpenRDA?

Q13: How do I use MSQuery from excel to access ODBC data sources.

Q14: I am running Cold Fusion on my Unix System and cannot get a connection to my database on NT.

Q15: The cgi script works from the command line, but not from the Linux cron.

Q16: How do I generate the oaodbc.so shared library on hp-ux 9.

Q17: If I execute a stored procedure in SQL Server with a parameter markers it does not return any records?

Q18: How to set CONCAT_NULL_YIELDS_NULL to OFF with OpenAccess ADK?

Q19: I am unable to connect using Brio Server and OpenRDA running on my RS6000/AIX 4.3.x system to ODBC Database on windows.

Q20: We are unable to connect using Oracle Generic Connectivity after we reboot our Unix Server.

Q21: How do I use the Oracle Generic Connectivity on 64-bit HP system to connect to my database on windows.

Q22 How do I Install and Use OpenRDA on OpenVMS 7.0 , 7.1, 7.2 or 7.3.

Q23 We don't have UCX running on our VMS box, instead we use Multinet for our TCP/IP, When I install the OpenRDA ODBC Driver it gives following error's when linking executables.

%LINK-F-OPENIN, error opening SYS$COMMON:[SYSLIB]UCX$IPC.OLB; as input -RMS-E-FNF, file not found

%LINK-F-OPENIN, error opening SYS$COMMON:[SYSLIB]SQL$USER.OLB; as input -RMS-E-FNF, file not found

Q24 Installing OpenRDA on Windows XP gives the following error.

D:\is6\Code|XT|RunTime\ISFunc\MsgBox.rul

The box below is an "Unhandled Exception" and in the box

Error Number: 0x80040706
Description: Object reference not set Setup will now terminate

Q25 Installing OpenRDA on Windows XP gives the following error.

C:\Windows\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications.

Choose 'Close' to terminate the application.

Solution: The OPENRDA_INI and OA_ROOT environment variable is not set You need you setup the required variables by running the environment file setenv.sh script from the root folder located at {root}/config/ssunos5 folder.

1. Change to the installation {root} directory.

2. {root} source config/ssunos5/setenv.sh

Then run the odbcisql or oaisql. Please refer to page 2-5 of Installation and configuration Guide for further reference

print_err: Error Message = RDA error: Resource not available - [Microsoft][O

DBC Driver Manager] Data source name not found and no default driver specified

SQL: isql_connect() failure

Solution: It seems as if you didn't specified connect string at the time of installation. To add the connect string to the existing datasource Execute OpenRDA Administration Tool from the OpenAccess program group or run the RDAADMIN tool from the command line at c:\{root}\bin\iwinnt\rdaadmin This will bring up the main menu.

Select 2 to view/edit/delete database entry.

Select E to edit the existing data base entry and specify the connect string which is the ODBC data source name you have setup to access your target database.

Solution: The OpenRDA database name is either not registered with the OpenRDA administrator or it does not contain the Port and IP address of the server. Use the OpenRDA administrator tool (rdaadmin) to check the OpenRDA database name

Solution:The OpenRDA database on the client side does not contain the correct Port & IP address for the server or the server is not running or is configured at a different port number. Please check the Openrda.ini file for the port number. Use the OpenRDA administrator tool (rdaadmin) to check the IP address.

Solution: We categorize stored procedures into 2 groups:

- Stored procedures that return results rows (just like a select query)

- Stored procedures that do not return result rows (they may be doing insert, update, delete type of queries)

Procedures that return result rows

To call a stored procedure that returns result rows you need

SQL Syntax: {CALL procedure_name(a, b, c)}

From ISQL, you need to use! Or EXEC to tell ISQL that it is an SQL command:

ISQL> !{CALL procedure_name (a, b, c

ISQL>EXEC {CALL procedure_name(a, b, c)};

This will not execute commit if in Auto Commit mode.

Procedures that do not return data

To call a stored procedure that does not return results rows:

SQL Syntax: procedure_name

From ISQL, you need to use ! or EXEC to tell ISQL that it is an SQL command:

ISQL> !procedure_name(a, b, c);

ISQL> EXEC procedure_name (a, b, c);

This will execute Commit Transaction if in Auto Commit mode.

Solution: The environment variable ENV_MAKEFILE is not declared. To set this environment variable you need to run the setenv.sh script file from the {root} directory where you installed the product by typing:

source config/{Platform}/setenv.sh

OR

You can download it from the URL you were given for the initial OpenRDA ODBC download. It's in the second table on that page as part of pre-build oaodbc.so

Currently we support the shared library oaodbc.so on Solaris, Digital Unix, Linux, Sco-OpenServer and HP

print_err: SQL State = HZ520print_err:

Error Message = [ATI][OpenRDA ODBC]RDA error: Connection failure

SQL: isql_connect() failure

print_err: Native error = 0(0)

Solution: The error message seems to indicate that the connection problems could be TCP/IP related. Please check that your OpenRDA server is running and you are able to ping the server machine.

Solution: To execute a Perl script from Linux using our OpenRDA ODBC driver. Please follow the instructions in our Installation and Configuration Guide Chapter 5.

Solution: To install OpenRDA on OS/2 you need to have Windows sub system on your OS/2 machine. We require Win-OS/2 system only at the installation time. And is not required in the runtime environment.

Solution: The syntax for a select statement with a date range can be given as:

ISQL> select * from emp where date >= {ts '1999-01-01 01:01:00'} and date <= {ts '2000-02-02 02:02:00'};

Solution: The demo copy is identical to the released version and has no limitations.

The client expects to receive a response within 3600 sec. So if the server is taking longer than 1 hr to process the results it would time out. You can change this setting by editing the Openrda.ini Configuration file on the client side to have may be a 6hr timeout. The maximum setting should be less than 32000 sec's.

[CLIENT]

RESPONSE_TIME_OUT=21600

Solution: To read and view the system tables of Access through ODBC you need to change the settings in Access. To make system objects visible, click Options on the Tools menu, click the View tab, and then select the System Objects check box.

To read the system table of Access 97 through ODBC Open the Database and to set the permissions, click Security on the Tools menu and click User and Group Permissions and in the Permissions section select the Read Data check Box.

Solution: EXCEL uses MSQuery to access ODBC data sources. Since MSQuery 97 only supports FileDSN ODBC data sources (it does not support System DSN or User DSN data sources), you need to first setup a file DSN.

To setup a File DSN, Please refer to the OpenRDA SDK Installation & Configuration Guide.

Solution: Check to see if you are using iodbc driver manager or Inter Solve driver manager. As iodbc driver manager is not thread safe and ColdFusion require the multithreaded shared library so you need to use intersolve driver manager which comes along with the ColdFusion to connect to your database on NT.

Solution: The Cron jobs do not inherit the environment variables of the user running the job. Therefore, execute your. profile before the perl script.

i.e. 23,52 8-20 * * * ( . $HOME/.profile ; /usr/local/perl_script ) >/dev/null

Solution: Once you install the client please change the {oaroot}\sdk\oaodbc\makefile to use ld instead of $LINKER. Change

$(LINKER) $(GSFLAGS) $(LFLAGS) -o $(MODULE) *$(O) $(SYS_LIBS)

To

ld $(GSFLAGS) $(LFLAGS) -o $(MODULE) *$(O) $(SYS_LIBS)

Then execute the makefile.

Solution: The problem is that in SQL Server, SQLPrepare() is not able to report the number of columns in the result set if the query contains parameter markers. This causes our code to return no results. This means that your client code should send a query without parameter markers and specify the parameter value and pass directly to the SQLExecDirect().

Solution:When you define the System DSN for SQL Server "uncheck" the following:

Use ANSI nulls, paddings and warnings.

It has the same affect as setting the "CONCAT_NULL_YIELDS_NULL" to OFF for the ODBC session.

Solution:
1. Download the following ODBC Driver manager library (libodbc.a.tar).
2. Copy the downloaded library under {oa_root}/lib/raix on your client     system.
3. Make sure you have {oa_root}/lib/raix in your LIBPATH before     {Brio_root}/lib.
4. Now try connecting to your database using OpenRDA & Brio.

This happens since we copy the OpenRDA Configuration file (openrda.ini) in the /tmp folder which gets deleted when you reboot the Unix Server.

Solution:

Please define OPENRDA_INI in your oracle HS ODBC initialization file: {$ORAHOME}/hs/admin/inithsodbc.ora.

OPENRDA_INI = {oa_root}/config/{platform}/openrda.ini

Oracle is providing a 32-bit libraries for Oracle Generic Connectivity on 64-bit HP-UX 11. Include the /ORA_HOME/Lib32 folder in your SHLIB_PATH environment variable.

Click here for complete instructions on using Oracle Generic Connectivity with OpenRDA.

The OpenRDA ODBC 5.0 for OpenVMS was built on OpenVMS 6.2. You must perform the following steps to install and use it on a OpenVMS 7.x system.

1.Please follow the instructions in Chapter 11 "OpenVMS Installation Notes" in the Installation and Configuration Guide. Complete steps 1-7 in the installation guide and then continue with steps below.

NOTE: Some customers have had trouble using the command EXCHANGE /FDL. If you get and error with this command then please do the following:

set file /attr=(rfm:fix,lrl:32256,mrs:32256) avms.sav

2. After extracting the save set file in step 7. Change to AVMS folder
   $ set def oa_root:[AVMS]

3. Under OpenVMS V7.x and higher, to link object files that were compiled under OpenVMS V6.2, Modify the oaisql.opt and odbcisql.opt command files.

Look for:
   SYS$SHARE:CMA$OPEN_RTL/SHARE

   SYS$SHARE:POSIXC$SHARE/SHARE

Replace with:
   oa_root:[avms72]CMA$OPEN_RTL/SHARE

4. Create the AVMS72 folder under OA_root folder.
   $ set def OA_root:[000000]
   $ create /dir [.AVMS72]

5. Also add this line at the end of disql_o.opt file.

   oa_root:[avms72]CMA$OPEN_RTL/SHARE

6. Transfer the CMA$OPEN_RTL.EXE (Click on the file name to get it) under [.AVMS72] folder.
   $ Set def OA_root:[AVMS72]

7. Continue with the instruction in our installation and Configuration Guide step 8.

Building the example Connect program

Follow the instructions in step 3 above to Modify the AVMS.OPT command file at the following folder to build the sample connect program.

$ Set def OA_root:[sdk.odbcsamp]

You will have to change the permissions to modify this file using

SET FILE/PROTECTION=(S:RWED,O=RWED,G:RWE,W:RWE) avms.opt

Q25 Installing OpenRDA on Windows XP gives the following error.
C:\Windows\SYSTEM32\AUTOEXEC.NT. The system file is not suitable for running MS-DOS and Microsoft Windows applications.

Here is the article on Microsoft site for this error message, please follow the instruction in this article.

http://support.microsoft.com/default.aspx?scid=kb;en-us;324767

Technical Support Number and Hours

Phone support is available from 8:00 AM to 6:00 PM PST by calling 408-350-7023 and selecting "1" for OpenRDA and FIX-ODBC support and "2" for the OpenAccess SDK family of products.

Email

For technical questions we suggest email. Please send your email to: support@OpenAccessSoftware.com You can expect a response based on your support plan.