nbkd72e
asked on
Sybase ct_connect error
I just installed ASE 15.0.2 on Linux, and created an "interfaces" file with two server entries in it:
CHI_IRPTRACKER_PRD
query tcp ether 171.188.69.123 50000
master tcp ether 171.188.69.123 50000
CHI_IRPTRACKER_DEV
query tcp ether 171.188.119.39 50000
master tcp ether 171.188.119.39 50000
However, when I try to run isql with the following command, it gave me the error:
ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.
The "isql" command I was using:
isql -S CHI_IRPTRACKER_DEV -U trackerUpdate -P sybase -I "/opt/sybase/interfaces"
Sybase is installed in directory "/opt/sybase", and I have two env. variables defined:
SYBASE=/opt/sybase
SYBASE_OCS=OCS-15_0
What could have caused this problem? Is there a debug flag to show more detailed information for either "isql" or the "ct" library?
Thanks
CHI_IRPTRACKER_PRD
query tcp ether 171.188.69.123 50000
master tcp ether 171.188.69.123 50000
CHI_IRPTRACKER_DEV
query tcp ether 171.188.119.39 50000
master tcp ether 171.188.119.39 50000
However, when I try to run isql with the following command, it gave me the error:
ct_connect(): directory service layer: internal directory control layer error: Requested server name not found.
The "isql" command I was using:
isql -S CHI_IRPTRACKER_DEV -U trackerUpdate -P sybase -I "/opt/sybase/interfaces"
Sybase is installed in directory "/opt/sybase", and I have two env. variables defined:
SYBASE=/opt/sybase
SYBASE_OCS=OCS-15_0
What could have caused this problem? Is there a debug flag to show more detailed information for either "isql" or the "ct" library?
Thanks
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I do have the whole ASE package installed, for the reason you mentioned.
After executing "SYBASE.sh", run isql still gave me the same error.
Is there a way to turn on some debug or trace information of the open client or "ct" library?
After executing "SYBASE.sh", run isql still gave me the same error.
Is there a way to turn on some debug or trace information of the open client or "ct" library?
ASKER CERTIFIED SOLUTION
membership
This solution is only available to members.
To access this solution, you must be a member of Experts Exchange.
ASKER
I fixed the problem, even though not sure what caused the problem exactly.
I just manually typed a separate copy of the interfaces file with vi, and it worked. Not sure what was wrong with the first one, as I also opened it with vi but didn't see anything wrong.
Thanks again. I appreciate your help.
I just manually typed a separate copy of the interfaces file with vi, and it worked. Not sure what was wrong with the first one, as I also opened it with vi but didn't see anything wrong.
Thanks again. I appreciate your help.
If you created the file on Windows and them FTPed it to Linux, you will have CR/LF line terminators when you really only want LF terminators. That confuses a lot of Linux programs. There is a utility, DOS2UNIX that strips the CRs for you.
Just a thought.
Bill
Just a thought.
Bill
ASKER
I thought about that, and opened the file with vi but didn't find any ^M which used to be the culprit.
ASKER
I don't see ENV.sh in "/opt/sybase" and I am using bash shell. Those two ASE servers defined in the interfaces file are running on separate Solaris machines and out of my control. I don't have ASE configured on the Linux and only want to be able to run isql to connect to those remote ASEs.
I am also confused by the ct error message. Does it mean the ct library is having trouble to find the definition of server "CHI_IRPTRACKER_DEV", or it is having trouble to connect to that server?