Translating with DrWatson… this can take a few seconds the first time.
This is a genuine, complex translation. DrWatson protects commands, error codes, and log output while naturally translating the surrounding text. It’s translated once and saved.
After migrating from SCO/Informix 7 to Red Hat with IDS 10, the poster installed ISQL in a separate directory and found dbaccess worked fine while ISQL failed with "930/908: cannot connect to the database server", even when specifying database@servername. Suggestions about shared-memory connections and 32/64-bit mismatches didn't apply. Art Kagel pointed out that the ISQL installation has its own etc/sqlhosts, which must contain the server entry (or INFORMIXSQLHOSTS must point to the main sqlhosts). The ISQL sqlhosts file was indeed wrong, and fixing it resolved the problem.
Auto-generated by DrWatson from the posts below — may be imperfect; read the full thread.
is it the "query language" isql that is not working or is it a form or
a report? if it is a form or a report is the form or report "hard
coding" a different server name in the database statement?
is there a Connections option in ISQL that lists the various servers
listed in your sql hosts file?
Can you connect to your server that way before trying to connect to the
database?
andrew.burridge@gmail.com wrote:
> Hey guys, I'm looking for a little help with regards to an ISQL
> installation.
>
> We're currently migrating from SCO open server and informix 7.x to a
> Red Hat Enterprise 4 server with IDS 10. Under the initial
> installation, we simply installed IDS and ported over our database
> tables. We could access things fine through dbaccess, but discovered
> that we needed to install ISQL for extra functionality.
>
> Given the installation order for Informix, we uninstalled IDS (copying
> over the onconfig and sqlhosts files), the installed ISQL to
> $INFORMIXDIR. We then re-installed IDS, copied back the sqlhosts and
> onconfig files and tested.
>
> The problem is that we can still access the tables etc through
> dbaccess, but when trying to connect with isql, we get an error
> message:
>
> "930: cannot connect to the database server (<servername>)"
>
> Now the servername is correct for the entry in the sqlhosts file, so
> it's trying to access the correct server by the looks of things. Even
> when I try to force isql to connect to a specific database at launch
> through 'isql database@servername', I get the same problem.
>
> The thing that baffles me is that I can still connect through dbaccess.
> I would have thought that if the config files were setup incorrectly
> then both isql and dbaccess would have a problem. The only thing that
> I can think of is that because the databases and tables were copied
> over originally before isql was installed that it is something to do
> with that.
>
> I'd appreciate any suggestions.
>
> Thanks,
>
> Andy
Hi,
It's pretty much everything regarding isql that isn't working...
When I go to query language, it attempts to connect to the server to
find a list of databases, but fails with the error:
"908: Attempt to connect to the database server () failed."
This is actually a different error code from the one I received
originally when I had isql in the same directory as IDS, although it's
still exhibiting the same behaviour.
Similarly, there should be a list of forms and reports for me to select
when I go into isql. When I go to either of these menus and choose
'run' to try and select one, there are none available.
As far as I can see, there is no option within isql to force a
connection to a server. I've tried forcing it at launch through the
command isql meridian@linux_test (our main db and server), but this
fails with the error:
"908: Attempt to connect to the database server (linux_test) failed."
Everything appears to point to an incorrectly configured sqlhosts or
hosts/services files. But the fact that I can connect to everything
fine through the dbaccess tool from IDS surely means that these are ok?
I assume you are connecting to a server called linux_test and you are
using a shared memory connection?
there is no mix up here with a 32bit and 64 bit product (FC tool and a
UC engine or vice versa?)
otherwise it sounds like it may be time to contact your support provider
Hi,
Yeah, you're correct in your assumptions. Both versions are UC, so
there shouldn't be a conflict.
Trust me to come up with a crazy problem! Thanks for all your help
anyway.
Andy
↪ replying to andrew.burridge@gmail.com
Art S. Kagel — — source: Usenet: comp.databases.informix
andrew.burridge@gmail.com wrote:
> Hi,
>
> It's pretty much everything regarding isql that isn't working...
>
> When I go to query language, it attempts to connect to the server to
> find a list of databases, but fails with the error:
>
> "908: Attempt to connect to the database server () failed."
OK, you're actually making progress. Is there a copy of
/usr/informix/etc/sqlhosts in /infmx-extras/isql/etc that includes the
$INFORMIXSERVER (or the @servername you are trying to use)? If not is
INFORMIXSQLHOSTS set to /usr/informix/etc/sqlhosts (or other sqlhosts file
containing the server definition)? If neither is true, that's the problem.
Your session cannot see the servername in the sqlhosts file.
Art S. Kagel
Hi Art,
You've got it! I knew it would be something simple, the sqlhosts file
in my /infmx-extras/isql/etc directory was set up incorrectly.
Thanks a lot.
And thanks to everyone who posted on here too, I was in a proper muddle
with all the config files and everything, so it was all really helpful.
Thanks,
Andy
We use strictly necessary cookies to make this site work. With your
consent we’d also use optional cookies for analytics and marketing. You can accept all,
reject all, or choose. Read our Cookie Policy.