OpenAPI Status Codes

DATABASE

    Sponsored Links

    Next

  • 1. Building Ingres: It lives, it breathes, it quacks like a duck!
    This is really too sad for words ......................
  • 2. jdbc connection problem
    Richard, 1. Check that the JDBC server on host "myhost" is configured (and has a count of 1). Check its config and errlog.log to see its using port II7. Ensure you haven't started too many GCC's and the port JDBC is now using is different (check errlog.log). 2. Can you ping "myhost" from the box you're running the Java program on ? If the java program and DBMS are on the same box, try localhost instead of myhost. 3 Ensure you have the latest JDBC patch from CA (there is a separate JDBC patch on the support downloads for the edbc.jar and .class files). The 2.6 installation I put in was not patched to the latest JDBC client levels ! You can get the version by running the command java -classpath ${II_SYSTEM}/ingres/lib:${II_SYSTEM}/ingres/lib/edbc.jar EdbcInfo The output should be at least: - Driver version: CA-EDBC JDBC Driver 1.4 Hope this helps Gary

OpenAPI Status Codes

Postby Richard Marsden » Thu, 21 Apr 2005 00:48:09 GMT

Unfortunately I can't reproduce the problem, but a customer is having a 
problem with ODBC->Ingres. This is a local Ingres database on a Windows 
machine.

OpenAPI is reporting "IIapi_initialize() return code = 5".
I've found the IIapi_initialize documentation, and I assume "5" refers 
to one of the Ingres status codes IIAPI_ST_OUT_OF_MEMORY or 
IIAPI_ST_FAILURE. I've tried searching the docs and Google without any 
luck on finding these values.

The ODBC loc reports that SQLAllocHandle on SQL_HANDLE_ENV failed.

We thought there might be a user/pwd problem, but the above two error 
messages don't appear to be related; and we've tried to fix any user/pwd 
problems at our end.
Apparantly other apps are accessing Ingres okay.

Does anyone have any ideas? Are handles limited, and it is running out 
of them?   What does the code "5" refer to?
Is this a common kind of error?


-- 
Richard Marsden
Winwaed Software Technology,  http://www.**--****.com/ 
 http://www.**--****.com/  for MapPoint tools and add-ins

Re: OpenAPI Status Codes

Postby Mike Lay » Thu, 21 Apr 2005 20:52:32 GMT



We've seen this sort of thing in two instances:

a) Where an older version of IIAPI.DLL exists and the program was 
somehow finding it.

b) Where the PATH contains a non existent directory. This one can be 
particularly entertaining to track down since Windows does not always 
evaluate the path in the same order (so I'm told). Removing the defunct 
path entry seemed to solve the problem.

However, I would regard it odd that one application is causing the 
problems; we tended to see this issue sporadically on effected user 
machines regardless of what they were running.

Hope that helps...

Re: OpenAPI Status Codes

Postby Richard Marsden » Thu, 21 Apr 2005 23:43:47 GMT


...


Thanks Mike - that gives us some more to go on, and is less destructive 
than Paul's suggestion  :-)

I've forward the suggestions. It should be easy enough to get the end 
user to check for the extra DLL. The path might need some thinking about 
- perhaps a special diagnostic program on our part.


Thanks,

Richard

---
Richard Marsden
Winwaed Software Technology,  http://www.**--****.com/ 
 http://www.**--****.com/  for MapPoint tools and add-ins

Re: OpenAPI Status Codes

Postby Richard Marsden » Fri, 29 Apr 2005 23:55:31 GMT

Is IIAPI.DLL the correct name, and where should it be?

Yes this problem keeps coming back (that's the problem with a customer 
chain). The end customer is reporting that they can't find IIAPI.DLL. 
I've just a search on this PC and can't find it - but then Windows 
decided the Winnt\system(32) directories would not interest me!!!
Manual searches of the two system directories failed to come up with 
anything.
A search for ii*.dll came up with some ii*api.dll files in the Ingres 
directory.


At the moment I'm beginning to suspect Jet->ODBC->Ingres is at fault.
(ie. Jet's handling of ODBC fails when the end database is Ingres)

Yes Jet is old, and we have a plan to replace it for direct ODBC in the 
near future.


-- 
Richard Marsden
Winwaed Software Technology,  http://www.**--****.com/ 
 http://www.**--****.com/  for MapPoint tools and add-ins

Re: OpenAPI Status Codes

Postby Richard Marsden » Sat, 30 Apr 2005 01:06:08 GMT

Further to this post, I have the following Ingres dlls when I do a 
disk-wide search on ii*.dll     (comes up with a lot of IIS stuff of course)
IIICEAPI.DLL or iilibapi.dll is perhaps the closest?

  Directory of C:\Program Files\CA\Ingres [II]\ingres\bin

12/07/2004  03:04p             176,128 iigetver.dll
12/07/2004  01:20p              81,920 IIICEAPI.DLL
12/10/2004  01:37p             499,712 iilibadf.dll
12/10/2004  01:44p             118,784 iilibadfdata.dll
12/07/2004  12:57p             212,992 iilibapi.dll
12/07/2004  12:27p             610,304 iilibcompat.dll
12/07/2004  12:27p              49,152 iilibcompatdata.dll
12/07/2004  12:34p              38,912 iilibcuf.dll
12/07/2004  02:11p           2,732,032 iilibdmf.dll
12/07/2004  02:11p              29,696 iilibdmfdata.dll
12/14/2004  08:35p             749,568 iilibembed.dll
12/14/2004  09:55p              11,264 iilibembeddata.dll
12/07/2004  02:37p           1,077,248 iilibframe.dll
12/07/2004  02:37p              65,536 iilibframedata.dll
12/07/2004  12:57p             163,840 iilibgcf.dll
12/07/2004  12:57p              27,136 iilibgcfdata.dll
12/07/2004  02:08p             139,264 iilibgwf.dll
12/07/2004  02:27p              13,312 iilibgwfdata.dll
12/07/2004  03:04p             217,088 iilibinterp.dll
12/07/2004  03:04p               6,144 iilibinterpdata.dll
12/07/2004  02:11p             819,200 iilibopf.dll
12/07/2004  02:27p               6,656 iilibopfdata.dll
12/07/2004  02:11p           1,228,800 iilibpsf.dll
12/07/2004  02:37p             196,608 iilibq.dll
12/07/2004  01:02p               6,144 iilibqdata.dll
12/07/2004  02:27p             847,872 iilibqef.dll
12/07/2004  02:27p              13,824 iilibqefdata.dll
12/07/2004  12:34p              41,984 iilibqsf.dll
12/07/2004  02:00p               6,144 iilibqsfdata.dll
12/07/2004  01:53p             200,704 iilibrdf.dll
12/07/2004  01:53p              18,432 iilibrdfdata.dll
12/07/2004  12:51p              98,304 iilibrqf.dll
12/07/2004  01:53p               6,144 iilibrqfdata.dll
12/07/2004  02:11p           1,589,248 iilibscf.dll
12/07/2004  02:11p              12,800 iilibscfdata.dll
12/07/2004  02:07p             143,360 iilibsxf.dll
12/07/2004  02:27p               6,144 iilibsxfdata.dll
12/07/2004  12:52p             122,880 iilibtpf.dll
12/07/2004  01:53p               9,728 iilibtpfdata.dll
12/07/2004  12:29p               6,144 iilibudt.dll
12/07/2004  12:34p              54,272 iilibulf.dll
12/07/2004  12:34p              11,776 iilibulfdata.dll
12/16/2004  11:09a             106,496 iilibutil.dll
12/07/2004  02:30p              69,632 iilibxa.dll
12/07/2004  02:00p             208,896 IIPFCTRS.DLL



-- 
Richard Marsden
Winwaed Software Technology,  http://www.**--****.com/ 
 http://www.**--****.com/  for MapPoint tools and add-ins

Re: OpenAPI Status Codes

Postby Mike Lay » Sat, 30 Apr 2005 21:24:34 GMT




With an INGRES 2.6 installation, it looks like OIAPI.DLL is what you're 
after. On my machine its loafing in C:\IngresII\ingres\lib

Re: OpenAPI Status Codes

Postby Richard Marsden » Sun, 01 May 2005 01:32:43 GMT

Thanks Mike. I've passed your comments on.

I couldn't find the DLL on my PC - but I'm running with 3.0


-- 
Richard Marsden
Winwaed Software Technology,  http://www.**--****.com/ 
 http://www.**--****.com/  for MapPoint tools and add-ins

Similar Threads:

1.[Info-ingres] OpenAPI Status Codes

2.[Info-ingres] OpenAPI Status Codes

On 4/19/05, Richard Marsden < XXXX@XXXXX.COM > wrote:
> Unfortunately I can't reproduce the problem, but a customer is having a
> problem with ODBC->Ingres. This is a local Ingres database on a Windows
> machine.
> 
> OpenAPI is reporting "IIapi_initialize() return code = 5".
> I've found the IIapi_initialize documentation, and I assume "5" refers
> to one of the Ingres status codes IIAPI_ST_OUT_OF_MEMORY or
> IIAPI_ST_FAILURE. I've tried searching the docs and Google without any
> luck on finding these values.
> 
> The ODBC loc reports that SQLAllocHandle on SQL_HANDLE_ENV failed.
> 
> We thought there might be a user/pwd problem, but the above two error
> messages don't appear to be related; and we've tried to fix any user/pwd
> problems at our end.
> Apparantly other apps are accessing Ingres okay.
> 
> Does anyone have any ideas? Are handles limited, and it is running out
> of them?   What does the code "5" refer to?
> Is this a common kind of error?
> 

5 refers to IIAPI_ST_FAILURE which has to do with the version of the
API. This error has occurred in the past when there's been a mixture
of files from different Ingres versions on the machine.

Easiest way to fix it is to uninstall/re-install.However since you've
got local databases that would mean an unload/reload.

If there's more than one installation of Ingres, at different
versions, and one is unused, you could try removing the unused one, if
possible.

Otherwise it's a question of making sure that the paths only contain
directories to one version of Ingres at a time.

HTH


-- 
Paul Mason

3.pgbuildfarm - client-code: support for success status date and changed

4.Hide status bar (not status area)

Is there a way to hide the status bar by using a script?

5.pgsql: Have pg_ctl status always output to stdout, even stopped status,

6. [Info-ingres] OpenAPI Caling a database procedure

7. Problem on OpenAPI

8. [Info-ingres] OpenAPI Weirdness



Return to DATABASE

 

Who is online

Users browsing this forum: No registered users and 71 guest