Sybase NNTP forums - End Of Life (EOL)

The NNTP forums from Sybase - forums.sybase.com - are now closed.

All new questions should be directed to the appropriate forum at the SAP Community Network (SCN).

Individual products have links to the respective forums on SCN, or you can go to SCN and search for your product in the search box (upper right corner) to find your specific developer center.

-sa problem

5 posts in General Discussion Last posting was on 2008-07-14 14:31:33.0Z
Dwayne Posted on 2008-07-11 14:58:22.0Z
Sender: 65e3.487773c0.1804289383@sybase.com
From: Dwayne
Newsgroups: ianywhere.public.general
Subject: -sa problem
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <4877750e.662a.1681692777@sybase.com>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 11 Jul 2008 07:58:22 -0700
X-Trace: forums-1-dub 1215788302 10.22.241.41 (11 Jul 2008 07:58:22 -0700)
X-Original-Trace: 11 Jul 2008 07:58:22 -0700, 10.22.241.41
Lines: 16
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6963
Article PK: 5188

I have a database server (sql anywhere 10.1) with a primary
server name and several alternate server names.

From the documentation if you specify an alternate server
name then the database file associated with that server
should be the only one able to be connected to however this
is not the case. I had a client using SQL Anywhere 9 client
specify a the alternate server name with no database name
and no file get connected to the incorrect database file.

The server is running EBF 3716.

Prior to loading this latest EBF my sql anywhere 9 clients
were unable to connect at all. Now this one connected but
gained access to a database file they should not have been
able to access.


"Nick Elson" < Posted on 2008-07-11 15:26:13.0Z
From: "Nick Elson" <@@@nick@@@.@@@elson@sybase@@@.@@@com@@@>
Newsgroups: ianywhere.public.general
References: <4877750e.662a.1681692777@sybase.com>
Subject: Re: -sa problem
Lines: 38
X-Priority: 3
X-MSMail-Priority: Normal
X-Newsreader: Microsoft Outlook Express 6.00.2900.2869
X-RFC2646: Format=Flowed; Original
X-MimeOLE: Produced By Microsoft MimeOLE V6.00.2900.2962
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <48777b95$1@forums-1-dub>
Date: 11 Jul 2008 08:26:13 -0700
X-Trace: forums-1-dub 1215789973 10.22.241.152 (11 Jul 2008 08:26:13 -0700)
X-Original-Trace: 11 Jul 2008 08:26:13 -0700, vip152.sybase.com
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6964
Article PK: 5189

Do you mean the -sn switch?

Can you show the V10 database server cmdline?
As well as your V9 connection string?

There is only ever 1 server name so I suspect you
are speaking about database aliases when you say
you have several [...] server names. If you are
talking about multiple -sn switches, that is a
database mirroring function.

If I am correct in my understanding, the V9 client
libraries are not expected to know how to handle
the database mirroring, and so your are likely
just getting connected to the default database;
ie.database #1 in your call to sa_db_info( [1] );

<Dwayne> wrote in message news:4877750e.662a.1681692777@sybase.com...
>I have a database server (sql anywhere 10.1) with a primary
> server name and several alternate server names.
>
> From the documentation if you specify an alternate server
> name then the database file associated with that server
> should be the only one able to be connected to however this
> is not the case. I had a client using SQL Anywhere 9 client
> specify a the alternate server name with no database name
> and no file get connected to the incorrect database file.
>
> The server is running EBF 3716.
>
> Prior to loading this latest EBF my sql anywhere 9 clients
> were unable to connect at all. Now this one connected but
> gained access to a database file they should not have been
> able to access.


David Fishburn Posted on 2008-07-11 15:43:13.0Z
Newsgroups: ianywhere.public.general
Subject: Re: -sa problem
From: David Fishburn <fishburn_spam_off@ianywhere.com>
References: <4877750e.662a.1681692777@sybase.com>
Organization: iAnywhere Solutions
Message-ID: <Xns9AD87739B70C5fishburnsybasecom@10.22.241.106>
User-Agent: Xnews/2005.10.18
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Date: 11 Jul 2008 08:43:13 -0700
X-Trace: forums-1-dub 1215790993 10.22.241.152 (11 Jul 2008 08:43:13 -0700)
X-Original-Trace: 11 Jul 2008 08:43:13 -0700, vip152.sybase.com
Lines: 34
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6965
Article PK: 5190

Dwayne wrote in news:4877750e.662a.1681692777@sybase.com
of ianywhere.public.general:

Not sure I followed all of that.

10.0.1.3716

So, can you show:
1. The command line used to start the SQL Anywhere server
2. The command line used to connect DBISQL to the server

What you were expecting and what you were not.

--
David Fishburn
Certified ASA Developer Version 8
iAnywhere Solutions - Sybase
Professional Services
Please only post to the newsgroup
Please ALWAYS include version and MORE importantly BUILD number with
EACH post (dbeng10 -v).

EBFs and Maintenance Releases
http://downloads.sybase.com/

Developer Community / Whitepapers
http://www.ianywhere.com/developer

Case-Express - to report bugs
http://case-express.sybase.com

CodeXchange - Free samples
http://ianywhere.codexchange.sybase.com/servlets/ProjectDocumentList


Dwayne Posted on 2008-07-14 11:06:16.0Z
Sender: 7508.487b2ec4.1804289383@sybase.com
From: Dwayne
Newsgroups: ianywhere.public.general
Subject: Re: -sa problem
X-Mailer: WebNews to Mail Gateway v1.1t
Message-ID: <487b3328.76dc.1681692777@sybase.com>
References: <Xns9AD87739B70C5fishburnsybasecom@10.22.241.106>
NNTP-Posting-Host: 10.22.241.41
X-Original-NNTP-Posting-Host: 10.22.241.41
Date: 14 Jul 2008 04:06:16 -0700
X-Trace: forums-1-dub 1216033576 10.22.241.41 (14 Jul 2008 04:06:16 -0700)
X-Original-Trace: 14 Jul 2008 04:06:16 -0700, 10.22.241.41
Lines: 49
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6969
Article PK: 5195

Example Server Configuration
-x tcpip(port=2644) -n DBSERVER
"e:\data\DB1.db" -sn alias1
"e:\data\DB2.db" -sn alias2
"e:\data\DB3.db" -sn alias3
"e:\data\DB4.db" -sn alias4
"e:\data\DB5.db" -sn alias5
"e:\data\DB6.db" -sn alias6
"e:\data\DB7.db" -sn alias7
"e:\data\DB8.db" -sn alias8
"e:\data\DB9.db" -sn alias9
"e:\data\DB10.db" -sn alias10

Version 9 dbisqlc.exe connection parameters
User ID & Password supplied of course
Data Source Name: ODBCAlias6

ODBC Administrator
System Data Source
Name: ODBCAlias6
Driver: Adaptive Server Anywhere 9

ODBC Configuration for ODBCAlias6 - if a field is
unspecified then it is whatever the default came up as.
ODBC Tab:
Data Source Name: ODBCAlias6

Database Tab
Server Name: alias6

Network Tab:
TCP/IP checked
TCP/IP Parameters: HOST=199.199.179.79;PORT=2644
Shared Memory Unchecked

Trying to connect to alias6 which would be the file
"e:\data\DB6.db" and instead end up connecting to the file
"e:\data\DB1.db"

I would have thought even though -sa is specifying an
"alias" server name that it would function like any other
server name.

When using an ODBC entry with like the one above with an
Adaptive Server Anywhere 10 driver everything works as
expected.

I just figured this was a bug. Prior to the latest EBF I
was not even able to get connected with a version 9 driver.


Graeme Perrow Posted on 2008-07-14 14:31:33.0Z
From: Graeme Perrow <ReplyToNewsgroupOnly-gperrowNO@SPAMianywhere.PLEASEcom>
Reply-To: ReplyToNewsgroupOnly-gperrowNO@SPAMianywhere.PLEASEcom
Organization: Sybase iAnywhere
User-Agent: Thunderbird 2.0.0.14 (Windows/20080421)
MIME-Version: 1.0
Newsgroups: ianywhere.public.general
Subject: Re: -sa problem
References: <Xns9AD87739B70C5fishburnsybasecom@10.22.241.106> <487b3328.76dc.1681692777@sybase.com>
In-Reply-To: <487b3328.76dc.1681692777@sybase.com>
Content-Type: text/plain; charset=ISO-8859-1; format=flowed
Content-Transfer-Encoding: 7bit
NNTP-Posting-Host: vip152.sybase.com
X-Original-NNTP-Posting-Host: vip152.sybase.com
Message-ID: <487b6345$1@forums-1-dub>
Date: 14 Jul 2008 07:31:33 -0700
X-Trace: forums-1-dub 1216045893 10.22.241.152 (14 Jul 2008 07:31:33 -0700)
X-Original-Trace: 14 Jul 2008 07:31:33 -0700, vip152.sybase.com
Lines: 68
X-Authenticated-User: techsupp
Path: forums-1-dub!not-for-mail
Xref: forums-1-dub ianywhere.public.general:6970
Article PK: 5194

What version of the *client* software are you running? If you are
running 9.0.2 prior to build 2532, 9.0.1 prior to build 1951 or 9.0.0
prior to build 1388, you will see this problem. Install the latest EBF
on the client machines and you should see the behaviour you expect.

Any version of 10.x should work as expected.

Graeme Perrow
Senior Software Developer
gperrow _at_ ianywhere _dot_ com
Sybase iAnywhere

SQL Anywhere Developer Community
http://www.sybase.com/developer/library/sql-anywhere-techcorner
SQL Anywhere Blog Center
http://www.sybase.com/sqlanyblogs

Dwayne wrote:
> Example Server Configuration
> -x tcpip(port=2644) -n DBSERVER
> "e:\data\DB1.db" -sn alias1
> "e:\data\DB2.db" -sn alias2
> "e:\data\DB3.db" -sn alias3
> "e:\data\DB4.db" -sn alias4
> "e:\data\DB5.db" -sn alias5
> "e:\data\DB6.db" -sn alias6
> "e:\data\DB7.db" -sn alias7
> "e:\data\DB8.db" -sn alias8
> "e:\data\DB9.db" -sn alias9
> "e:\data\DB10.db" -sn alias10
>
> Version 9 dbisqlc.exe connection parameters
> User ID & Password supplied of course
> Data Source Name: ODBCAlias6
>
> ODBC Administrator
> System Data Source
> Name: ODBCAlias6
> Driver: Adaptive Server Anywhere 9
>
> ODBC Configuration for ODBCAlias6 - if a field is
> unspecified then it is whatever the default came up as.
> ODBC Tab:
> Data Source Name: ODBCAlias6
>
> Database Tab
> Server Name: alias6
>
> Network Tab:
> TCP/IP checked
> TCP/IP Parameters: HOST=199.199.179.79;PORT=2644
> Shared Memory Unchecked
>
> Trying to connect to alias6 which would be the file
> "e:\data\DB6.db" and instead end up connecting to the file
> "e:\data\DB1.db"
>
> I would have thought even though -sa is specifying an
> "alias" server name that it would function like any other
> server name.
>
> When using an ODBC entry with like the one above with an
> Adaptive Server Anywhere 10 driver everything works as
> expected.
>
> I just figured this was a bug. Prior to the latest EBF I
> was not even able to get connected with a version 9 driver.