|
Hm, I do not understand your question - if you are already successfully connected to the database, why would you need to know the port to connect (except you are connected locally via Shared Memory and want to know how different machines can connect via TCP/IP)? The following tells the server's used TCP/IP addresses and ports: select property('TcpIpAddresses');
For current connections, you can use the builtin sa_conn_info() procedure to check the "ServerPort" column (by default 2638) for connections with ColmmLink = 'TCPIP': call sa_conn_info(); The following might also help to get address and port for the current connection: select PropName, PropDescription, Value
from sa_conn_properties(-1)
where PropName in ('ServerNodeAddress', 'ServerPort');
|
|
If you want to specify the port that the server should listen to, specify "-x tcpip(port=xxxx)" as part of the dbsrv17 command line options. If you specify "-x tcpip" with no port, the server defaults to port 2638 unless 2638 is already in use, and if 2638 is in use, the server listens to an available port 49152 or higher. You have two general work flows:
Kind regards, Ian |
Hi
thanks for your reply. I started using SQL Anywhere for the first time this week having used Oracle for over 5 years. Setting up the listener and the port are two separate tasks in Oracle.
I eventually figured out where to create a listener in SQL Central for an existing database.