SQL Anywhere database - could client/server page size mismatch cause trouble?

Author

could client/server page size mismatch cause trouble?

Jason Boardman

2005-12-15, 8:23 pm

[ servers: RH9 9.0.2.3169 / clients: WIN32 9.0.0.1108 ]

Just a thought,
In my two locations I have two dbsrv9 servers, identical in every way
except for page size, one is 4096 the other 16384 (there is no good
reason for this, i was experimenting with a larger page size and i plan
to switch back to 4096 for the other after seeng Breck's constant posts
about it being *plenty* big). In each location the WIN32 ODBC client
has the startline: dbclient -x tcpip -p 4096 (or 16384). In some rare
occasions, we have people go between locations with portable computers-
and in these cases you have someone with a dbclient starline of :
dbclient -x tcpip -p 4096, hooking up to a dbsrv9 that has a page size
of 16384 and vice versa. On the surface we've never had any problems,
could this cause underlying problems? Or are the clients smart enough
to readjust when necessary?

Jason Boardman

Chris Keating(iAnywhere Solutions)

2005-12-15, 8:23 pm

DBCLIENT??? DBClient is a pre-ASA6 piece of software. The functionality
of dbclient is now directly part of the ASA client software. This
startline hopefully is being completely ignored as it should not be used.

--

Chris Keating
Sybase Adaptive Server Anywhere Professional Version 8

********************
********************
********************
*****************
Sign up today for your copy of the SQL Anywhere Studio 9 Developer Edition
and try out the market-leading database for mobile, embedded and small to
medium sized business environments for free!

http://www.ianywhere.com/promos/deved/index.html

********************
********************
********************
*****************

iAnywhere Solutions http://www.iAnywhere.com

** Please only post to the newsgroup

** Whitepapers can be found at http://www.iAnywhere.com/developer
** EBFs can be found at http://downloads.sybase.com/swx/sdmain.stm
** Use Case Express to report bugs http://case-express.sybase.com

********************
********************
********************
*****************

Greg Fenton

2005-12-15, 8:24 pm

Jason Boardman wrote:
> [ servers: RH9 9.0.2.3169 / clients: WIN32 9.0.0.1108 ]
>
> dbclient -x tcpip -p 4096, hooking up to a dbsrv9 that has a page size
> of 16384 and vice versa.

Why are you using "dbclient" in a 9.x setup?
Or, what is "dbclient"?

The "dbclient.exe" program that was necessary for client/server
communications went away in v6. The only reason I know about it is from
helping customers get away from it when moving to versions that are less
than 10 years old. ;-)

greg.fenton

Jason Boardman

2005-12-15, 8:24 pm

oh good! i hope it is being ignored - you see i've been using sybase
a long time and went from version 5.5 directly to 9.0 and basically
had to just follow my nose in configuring the new ODBC specs. in the
ODBC adminstrator:Databas
e Tab of my db:I had this text in the Start
line field: "dbclient -x tcpip -p 16384". i guess it was ignored, as i
just removed it and i can still connect just fine. ha! so i guess the
big answer is, page size is not given to the client at all. that does
make more sense, i wonder why it was an option back in 5.5?

still figuring out this strange new world,
jason boardman

Chris Keating(iAnywhere Solutions) wrote:
> DBCLIENT??? DBClient is a pre-ASA6 piece of software. The functionality
> of dbclient is now directly part of the ASA client software. This
> startline hopefully is being completely ignored as it should not be used.
>
>

Jason Boardman

2005-12-15, 8:24 pm

ha! yes, i guess in software-years i'm starting to look like a
senior citizen. but hey, if it ain't broke...

jason

Greg Fenton wrote:
> communications went away in v6. The only reason I know about it is from
> helping customers get away from it when moving to versions that are less
> than 10 years old. ;-)
>
> greg.fenton

Breck Carter [TeamSybase]

2005-12-15, 8:24 pm

On 15 Dec 2005 11:45:00 -0800, Jason Boardman
< nospam_jasonboardman
_@_gmail_._com> wrote:

>after seeng Breck's constant posts

lol!

Breck Of Constant Sorrow

--
SQL Anywhere Studio 9 Developer's Guide
Buy the book: http://www.amazon.com/exec/obidos/A...7/risingroad-20
bcarter@risingroad.com
RisingRoad SQL Anywhere and MobiLink Professional Services
www.risingroad.com

Reg Domaratzki $iAnywhere Solutions$

2005-12-15, 8:24 pm

The -p switch on dbclient defined the size of the packet that was being sent
on the wire and had nothing to do with the page size of the database.

--
Reg Domaratzki, Sybase iAnywhere Solutions
Sybase Certified Professional - Sybase ASA Developer Version 8
Please reply only to the newsgroup

iAnywhere Developer Community : http://www.ianywhere.com/developer
iAnywhere Documentation : http://www.ianywhere.com/developer/product_manuals
ASA Patches and EBFs : http://downloads.sybase.com/swx/sdmain.stm
-> Choose SQL Anywhere Studio
-> Set filter to "Display ALL platforms IN ALL MONTHS"

"Jason Boardman" < nospam_jasonboardman
_@_gmail_._com> wrote in message
news:43a1d0ca$1@foru
ms-1-dub...[color=darkred]
> oh good! i hope it is being ignored - you see i've been using sybase
> a long time and went from version 5.5 directly to 9.0 and basically
> had to just follow my nose in configuring the new ODBC specs. in the
> ODBC adminstrator:Databas
e Tab of my db:I had this text in the Start
> line field: "dbclient -x tcpip -p 16384". i guess it was ignored, as i
> just removed it and i can still connect just fine. ha! so i guess the
> big answer is, page size is not given to the client at all. that does
> make more sense, i wonder why it was an option back in 5.5?
>
> still figuring out this strange new world,
> jason boardman
>
> Chris Keating(iAnywhere Solutions) wrote:
used.[color=darkred]

Sponsored Links