Re: installing DBD-Informix on fedora 6

On 1/29/07, Oliver Howe <oliverj@xxxxxxxxxxxxxxxxxxx> wrote:


>> no i dont see anything from that server when running the esqltest. but
on the client i can telnet to the server on port 1526 as the user informix.
i have stopped iptables and ip6tables on the client
>
>can you snoop on the server to see if any packets reach the interface
>at all when running esqltest?

there is some stuff that reaches it :-
[...snip...]
which seems to be referring to checking the hostnames?
hmmail2.uk1.bibliotech.net is the client (running fedora 6) and
dbpmuk2.uk1.bibliotech.net is the db server

>Can you do "CREATE TABLE dbd_ix_esqltest (Col01 INTEGER NOT NULL);"
>from dbaccess on the server in the stores database as the appropriate
>user?

yes


This is a key issue (connecting with DB-Access on the server machine). The
error 107 (discussed in previous emails in this thread) has me a bit
puzzled. Does Fedora Core 6 have an error value (from errno.h) for 107? If
so, does the associated message drop any hints? Taken at face value, it
appears that someone has the database locked in exclusive mode (though I'd
like to think the error would say that more clearly). Did the process
(session) that created the database complete yet? Classically, you get
exclusive access when you create a database, up until you terminate the
session that created the DB.

When you connect using DB-Access, you are using the same server name and
sqlhosts values; you aren't suddenly switching to shared memory connections
or anything like that?

You're using CSDK 2.90.UC2; that's good. Close enough to the most recent
version that it is unlikely to be the cause of the trouble.

You seem to be connecting to IDS as either root or informix - frankly, you
should do neither. Treat them both with extreme caution - they are just
about equally powerful with respect to IDS. I never do things like building
DBD::Informix as either informix or root; I'd find (or create) another user
to do the work as. If I actually needed to install DBD::Informix as root,
I'd use the privileges then, but only then.

[Aside: I'm not sure why you feel having DBANSIWARN set is a good idea.]

--
Jonathan Leffler <jonathan.leffler@xxxxxxxxx> #include <disclaimer.h>
Guardian of DBD::Informix - v2005.02 - http://dbi.perl.org
"I don't suffer from insanity - I enjoy every minute of it."

Relevant Pages

  • Re: Help with first VB application - Data Entry form
    ... I assumed a desktop / winform client application ... time' stamp from the database machine - control machine ... ... problem solved - web server is control system. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Help with first VB application - Data Entry form
    ... I assumed a desktop / winform client application ... time' stamp from the database machine - control machine ... ... problem solved - web server is control system. ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Remobjects v KBM
    ... >> client query components) follow from that. ... Then, connections can be created to say SQL Server, Oracle, Interbase and ... can then be created from the abstract dataset definition in 'customers' to ... implicitly - this makes your code not be database connection specific). ...
    (borland.public.delphi.thirdpartytools.general)
  • Re: Help with first VB application - Data Entry form
    ... stamp from the database machine - control machine ... ... unnecessary data to the client ... ... and when building a database independent UI / Client - Server application, ... JavaScript, for example) and thus, will get the time from the web server, ...
    (microsoft.public.dotnet.languages.vb)
  • Re: Opinions needed about the best "Middleware suite" kbmMW vs. RODA
    ... kbmMW supports cross db in such way that all you need to do in your application is to set one property to switch to ... What one have to concentrate about is minimizing the amount of data moved from the app server to the client. ... C/S setup's usually have a quite active chatter going on between the client and the database, ...
    (borland.public.delphi.thirdpartytools.general)