| **Navigation:**  SQL Drivers > Oracle >====== Oracle Accelerator Troubleshooting ====== | [[oracle accelerator data types.htm|{{btn_prev_n.gif|Previous page}}]][[coming future.htm|{{btn_home_n.gif|Return to chapter overview}}]][[scalable sql accelerator driver.htm|{{btn_next_n.gif|Next page}}]] |
|  ||

**Clarion Won't Accept Oracle File Driver**

Clarion's Dictionary Editor allows you to select the Oracle file driver only if Oracle is installed on your machine. That is, the Oracle DLLs must be installed in a directory in your path before Clarion's Dictionary Editor will recognize the Oracle driver. Attempting to run the Oracle example program will produce error windows that tell you which DLLs are missing.

**Oracle Not Available (-1034)**

If you receive this error (Oracle error number -1034), make sure the Oracle server is properly installed and is available to the client.

**Unable to allocate memory on user side (-1019)**

This message may indicate some of the required Oracle DLLs are not installed to a directory in your system path. See [[oracle accelerator system requirements.htm|System Requirements--Software]]//.//

**Unable to spawn new ORACLE (-9352)**

This message may indicate the Oracle database is not started. Start the Oracle database and retry.

**Could Not Log On:Oracle Accelerator**

This message may indicate an invalid username, password, or servername. It may also indicate that the Oracle server is not installed or is otherwise not available. Make sure the Oracle server is properly installed and is available to the client.

**Invalid Field Type Descriptor: Oracle Accelerator**

The Clarion error: //Invalid Field Type Descriptor// is generated at runtime if you supply a field name in the field's NAME attribute that does not match any field name in the Oracle table. By turning logging on (see /LOGFILE) you can re-run your program and receive a list of valid field names in the log file. Use the dictionary import facility to import the field descriptions into your Clarion data dictionary to avoid this problem.

**Unexpected End of SQL Command (-921)**

If you receive this error (Oracle error number -921), make sure that the SQL Select statement selects the same number of columns as the receiving Clarion FILE structure declares.

This error may also occur when a CREATE statement generates incorrect SQL statements when the last field is OVER a previous field. Change the file layout so the last field declared is not declared OVER a previous field.

**File Not Found:Oracle Accelerator**

If you receive this error (or Oracle error number 942--Table or View Does Not Exist), check that the file name you are passing to the Oracle driver is valid. The most common occurrence of this error is when the name of the Oracle table is not correct. If the table is owned by another user, you must explicitly identify the owner as follows:

**owner.table**

**Error 47:Oracle Accelerator**

An Error 47 indicates there is a field defined in your Clarion data dictionary that does not exist on the Oracle server. To identify the field, use /LOGFILE.

**Internal Error 02: WSLDIAL:Oracle Accelerator**

Use the **Project Editor** dialog to add the ..\LIBSRC\ORALOON.RSC file to your application's **Library, object and resource files**.

To add resource files to your project:

1.From the Application Tree dialog, press the **Project **button.

2.Highlight **Library, object and resource files,** then CLICK on the **Add File** button.

3.Navigate to the ..\LIBSRC folder, then select the resource file (ORALOON.RSC) from the Windows File dialog.

4.Press the **OK **button to return to the **Project Editor** dialog.

**No Interface Driver Connected(-03121)**

This indicates you have not entered a correct database name. Be sure to enter the correct database name in the **Host **or **Database **field.

__**Oracle could not be found**__

See [[dll coding practices.htm|DLL Coding Practices]]