|
Home > Archive > SQL Anywhere database > June 2005 > double dbsrv9 start on Mac OSX
You are viewing an archived Text-only version of the thread.
To view this thread in it's original format and/or if you want to reply to
this thread please [click here]
| Author |
double dbsrv9 start on Mac OSX
|
|
| Alex La Greca 2005-06-22, 9:23 am |
| For some reasons we need to start a second ASA engine on a
Mac OSX machine.
Since that default port (2638) is already used by the first
engine we would like to use another port from the dbsrv9
start shell, but:
- if we do not specify any port it is unable to start;
- if we specify -x tcpip(serverport=262
9) like on DOS it
fails too;
- if we specify -x " tcpip(serverport=262
9)" like on some
Unix it fails too.
Is there any other way to start a second engine on Mac OSX
??
Thanks in advance for the answer
Alex La Greca
| |
| Graeme Perrow 2005-06-22, 9:23 am |
| Alex La Greca wrote:
> For some reasons we need to start a second ASA engine on a
> Mac OSX machine.
> Since that default port (2638) is already used by the first
> engine we would like to use another port from the dbsrv9
> start shell, but:
> - if we do not specify any port it is unable to start;
> - if we specify -x tcpip(serverport=262
9) like on DOS it
> fails too;
> - if we specify -x " tcpip(serverport=262
9)" like on some
> Unix it fails too.
The first one fails because we are trying to listen on the same UDP port
twice. Most operating systems allow that, but Mac OS X does not. The
second one fails because the '(' and ')' are being interpreted by the
shell (sh, bash, csh, etc.) rather than being passed to ASA. However,
the third case should work. Describe what you mean by "fails" in the
third case -- add "-z -o server.out" to the server start line and then
post the contents of server.out.
--
Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
iAnywhere Solutions Inc.
A Sybase company
Whitepapers, TechDocs, bug fixes are all available through the iAnywhere
Developer Community at http://www.ianywhere.com/developer/
| |
| Graeme Perrow 2005-06-23, 7:23 am |
| Alex La Greca wrote:
> Thanks for the answer.
> We started engine with this command:
> "dbsrv9 -z -o 1_server.out -x 'tcpip(ServerPort=26
29)' -n
> el2colonna -gd all -ud /Colonna/EasyLex2.db -n el2colonna"
> and attached You will find the server.out file.
> The strange behaviour seems to be in these lines:
> "Starting TCP listener on IP address 0.0.0.0:2629"
> "Starting UDP listener on IP address 0.0.0.0:2629"
> meaning that it understands the right port but not the right
> IP addr.
> We tried also to use this option in the start shell
> 'tcpip(HOST=192.168.168. 43;ServerPort=2629)'
> but nothing changed.
> We discovered also that on the first engine we have a
> similar behaviour, in the server.out :
> "Starting TCP listener on IP address 0.0.0.0:2638"
> "Starting UDP listener on IP address 0.0.0.0:2638"
> but from Sybase central we are able to find it, maybe
> because of
> the broadcast search; the second engine instead is
> unreachable.
Everything is working correctly. 0.0.0.0 is a special IP address -- when
an application listens on that address, it means "accept any packets
sent to this machine". If a machine has more than one IP address, this
allows the server to listen for packets destined for either one, as well
as broadcast packets destined for all machines on the network.
From the same client machine (the one where you're trying to run Sybase
Central), try:
dbping -d -c " uid=dba;pwd=sql;eng=
el2colonna;links=tcp
ip(port=2629)"
That should display something like
Adaptive Server Anywhere Server Ping Utility Version 9.0.1.1753
Connected to ASA 9.0.1.1753 server "el2colonna" and database
"el2colonna" at address <IP address>.
Ping database successful.
If that works, I find the easiest way to connect from then on is to
modify the dbping command to be a dbdsn command:
dbdsn -w el2colonna -c
" uid=dba;pwd=sql;eng=
el2colonna;links=tcp
ip(port=2629)"
And then specify DSN=el2colonna when you want to connect to that server.
--
Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
iAnywhere Solutions Inc.
A Sybase company
Whitepapers, TechDocs, bug fixes are all available through the iAnywhere
Developer Community at http://www.ianywhere.com/developer/
|
|
|
|
|