Topic
  • 1 reply
  • Latest Post - ‏2008-02-21T15:56:04Z by vonbarg
SystemAdmin
SystemAdmin
228 Posts

Pinned topic OAT error

‏2008-01-21T10:58:07Z |
Hi,

we try to use the openadmin tools (newest version). After the login we get following error:

Connection Failed:
DSN:informix:host=192.168.1.3;service=9089;database=sysmaster;protocol=onsoctcp;server=demo_on;TRANSLATIONDLL=/opt/IBM/informix2/lib/esql/igo4a304.so;Driver=/o pt/IBM/informix2/lib/cli/libifdmr.so;
could not find driver


The error log from the apache:

Tue Jan 15 10:32:58 2008 error http://client 192.168.1.107 Connection Failed:
DSN:informix:host=192.168.1.3;service=9089;database=sysmaster;protocol=onsoctcp;server=demo_on;TRANSLATIONDLL=/opt/IBM/informix2/lib/esql/igo4a304. so;Driver=/opt/IBM/informix2/lib/cli/libifdmr.so;
could not find driver, referer: http://192.168.1.3/oat/index.php?act=show&do=showCommands
Tue Jan 15 10:33:00 2008 error http://client 192.168.1.107 Connection Failed:
DSN:informix:host=192.168.1.3;service=9089;database=sysmaster;protocol=onsoctcp;server=demo_on;TRANSLATIONDLL=/opt/IBM/informix2/lib/esql/igo4a304. so;Driver=/opt/IBM/informix2/lib/cli/libifdmr.so;
could not find driver, referer: http://192.168.1.3/oat/index.php?act=show&do=showCommands
Tue Jan 15 10:33:08 2008 error http://client 192.168.1.107 Connection Failed:
DSN:informix:host=192.168.1.3;service=9089;database=sysmaster;protocol=onsoctcp;server=demo_on;TRANSLATIONDLL=/opt/IBM/informix2/lib/esql/igo4a304. so;Driver=/opt/IBM/informix2/lib/cli/libifdmr.so;
could not find driver, referer: http://192.168.1.3/oat/index.php


On a second Suse Linux server we get another error. After the login we get a blank page without any error message.

the error log from the apache:

Tue Jan 15 10:30:45 2008 error http://client 192.168.1.107 PHP Notice: Use of undefined constant ROOT_PATH - assumed 'ROOT_PATH' in /srv/www/htdocs/oat/admin/index.php on line 860, referer: http://192.168.1.230/oat/admin/index.php?act=admin&do=addconn
Tue Jan 15 10:30:45 2008 error http://client 192.168.1.107 PHP Notice: Constant ROOT_PATH already defined in /srv/www/htdocs/oat/lib/initialize.php on line 21, referer: http://192.168.1.230/oat/admin/index.php?act=admin&do=addconn
Tue Jan 15 10:30:53 2008 error http://client 192.168.1.107 Query:
SELECT DBINFO('version','full') AS vers , ha_type FROM sysha_type
Error: -206
InformixInformix ODBC DriverInformixThe specified table (sysha_type) is not in the database. (SQLPrepare-206 at /usr/lib/php5/extensions/informix_driver.c:131)
, referer: http://192.168.1.230/oat/
Tue Jan 15 10:30:53 2008 error http://client 192.168.1.107 PHP Fatal error: Call to a member function getVersion() on a non-object in /srv/www/htdocs/oat/templates/template_global.php on line 174, referer: http://192.168.1.230/oat/


Both systems use the same Suse and apache version. A Suse Linux Server is our informix Dynamic Server 11.10 UC1DE (developer Edition). The informix instance is online and dbaccess and our testprogramm seems to be OK.

Any Idea?

Best regards

Christian
Updated on 2008-02-21T15:56:04Z at 2008-02-21T15:56:04Z by vonbarg
  • vonbarg
    vonbarg
    1 Post

    Re: OAT error

    ‏2008-02-21T15:56:04Z  
    This message was also posted on the IIUG Admin Tools forum (www.iiug.org/forums/admin-tools) and responded to initially there. But for completeness, I'll also post a response to these errors here.

    In the first error, it is not able to load the ODBC driver.
    Here is what should be checked if you see this error:
    • Is Informix Client-SDK or I-Connect properly installed?
    • Does INFORMIXDIR in your Apache env point to the CSDK/I-Connection location?
    • Does the library it is looking for (/opt/IBM/informix2/lib/cli/libifdmr.so) exist?

    In the second error, the blank error page is caused by this error:
    SELECT DBINFO('version','full') AS vers , ha_type FROM sysha_type
    Error: -206

    For IDS version 11.10 and above the sysha_type table should exist in the sysmaster database. I have seen a customer with this error before and it turned out that their sysmaster database was not built correctly.