Re: PHP access to Informix-SE
Posted in 2010
Hultgren, Walt wrote:
> I’m attempting to set up access to an Informix-SE database on a Sun
> server from a Web server running Apache/PHP on CentOS. So far, I’m
> having no success. Here’s the environment -- the two versions each of
> Apache and PHP mean that I’ve tried them in various combinations:
>
>
>
> Web Server:
>
> - CentOS 5.4
>
> - Apache 2.2.3 (w/CentOS), 2.0.63 (compiled locally)
>
> - PHP 5.1.6 (w/CentOS), 5.3.1 (compiled locally)
>
> - PDO Informix 1.2.6
>
> - Informix Client SDK 3.50.FC6
>
>
>
> Database Server:
>
> - Sun Solaris 10
>
> - Informx-SE 7.25.UC7
>
>
>
> One question I have is whether I need Informix Client SDK or Informix
> Connect on the db server for this type of access. I don’t currently
> have it, but just run sqlexecd. I can successfully connect to the Sun
> db server from a different Sun box using Informix tools (dbaccess, isql,…).
>
>
>
> The two errors I see the most are when attempting PHP access from the
> CentOS box are “-11005: Invalid connection string attribute” from PHP,
> and (when I actually make it across to the Sun box) “-408: Invalid
> message type received from the sqlexec process” in the sqlexecd log. I
> can connect to the Sun db server from a different Sun box using Informix
> tools (dbaccess, isql,…) with no problem.
>
>
>
> All of the info I’ve been able to find on the Web and various forums is
> geared toward IDS, and most of it is a little dated at this point.
>
>
>
> If anyone has this type of set-up (or something close) working, I’d
> appreciate any suggestions you have, including which versions of the
> various packages to use.
Uh, gosh, that's a bit of a poser. Like the man says, I don't know the
answer, but I do admire the problem. I was under the impression that
this couldn't actually be done ... I didn't think that the client SDK
"spoke" SE (or OnLine, for that matter!)
Am I just addlepated?
--
Cheers,
Obnoxio The Clown
http://obotheclown.blogspot.com
I will now proceed to pleasure myself with this fish.
--
This message has been scanned for viruses and
dangerous content by OpenProtect(http://www.openprotect.com), and is
believed to be clean.