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.
Kamlesh Gallani got error 908 (conerr -25580) accessing a synonym on IDS 11.70.FC7 that pointed at db@@Y on a 9.40 server, though it worked with INFORMIXSERVER set to Y. Petr Pomykacek queried the double @@; Kamlesh said it was a typo. Art Kagel advised dropping and recreating the synonym with a single @. No confirmation of the result.
Auto-generated by Claude from the posts below — may be imperfect; read the full thread.
Hi,
I have two types of environments:
1. IBM Informix Dynamic Server Version 11.70.FC7X1 ( Instance X)
2. IBM Informix Dynamic Server Version 9.40.FC9W2XH ( Instance Y)
Now, I have a synonym defined on 'X' like below
create synonym "user".table1 for db@@Y:"user".table1;
When I try to access this synonym from X, I am getting the below error:
908: Attempt to connect to database server (Y, conerr=-25580, oserr=239)
failed.
Error in line 1Near character position 33
But when I export INFORMIXSERVER=Y on X, I am able to access all the tables
including the above.
The sqlhosts settings are correct.
Can somebody please suggest what could be the issues here?
Thanks and Regards,
Kamlesh
Dne 09.04.2015 13:07, KAMLESH GALLANI napsal:
> Hi,
> I have two types of environments:
>
> 1. IBM Informix Dynamic Server Version 11.70.FC7X1 ( Instance X)
> 2. IBM Informix Dynamic Server Version 9.40.FC9W2XH ( Instance Y)
>
> Now, I have a synonym defined on 'X' like below
>
> create synonym "user".table1 for db@@Y:"user".table1;
why two @@. Do you use only one.
>
> When I try to access this synonym from X, I am getting the below error:
>
> 908: Attempt to connect to database server (Y, conerr=-25580,
> oserr=239)
> failed.
> Error in line 1> Near character position 33
>
> But when I export INFORMIXSERVER=Y on X, I am able to access all the
> tables
> including the above.
>
> The sqlhosts settings are correct.
>
> Can somebody please suggest what could be the issues here?
>
> Thanks and Regards,
> Kamlesh
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
--
Petr Pomykacek
tel.: +420 724 795 076
Drop the synonym and redefine it as:
create synonym "user".table1 for db@Y:"user".table1;
Only one "@" sign is required to reference a database in a remote server.
Art
Art S. Kagel, President and Principal Consultant
ASK Database Management
www.askdbmgt.com
Blog: http://informix-myview.blogspot.com/
Disclaimer: Please keep in mind that my own opinions are my own opinions
and do not reflect on the IIUG, nor any other organization with which I am
associated either explicitly, implicitly, or by inference. Neither do
those opinions reflect those of other individuals affiliated with any
entity with which I am affiliated nor those of the entities themselves.
On Thu, Apr 9, 2015 at 7:07 AM, KAMLESH GALLANI <
kamlesh.gallani@cognizant.com> wrote:
> Hi,
> I have two types of environments:
>
> 1. IBM Informix Dynamic Server Version 11.70.FC7X1 ( Instance X)
> 2. IBM Informix Dynamic Server Version 9.40.FC9W2XH ( Instance Y)
>
> Now, I have a synonym defined on 'X' like below
>
> create synonym "user".table1 for db@@Y:"user".table1;
>
> When I try to access this synonym from X, I am getting the below error:
>
> 908: Attempt to connect to database server (Y, conerr=-25580, oserr=239)
> failed.
> Error in line 1> Near character position 33
>
> But when I export INFORMIXSERVER=Y on X, I am able to access all the tables
> including the above.
>
> The sqlhosts settings are correct.
>
> Can somebody please suggest what could be the issues here?
>
> Thanks and Regards,
> Kamlesh
>
>
>
>
*******************************************************************************
> Forum Note: Use "Reply" to post a response in the discussion forum.
>
>
--001a1141b53ee8a5a3051349dd2c
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.