9.0.1 to 9.0.2 question

Currently an application running on an older Symbol device
with CF 1.x that was built using a 9.0.1.xxxx build is
synchronizing with a consolidated db of the same 9.0.1.xxxx
build.

I am porting the handheld application to an intermec device
and will need to build using the .NET CF 2.0. In order to do
this I need to move to a 9.0.2.xxxx SQL anywhere build.

I'd like to leave the consolidated db alone, since there is
an amount of time that I will have a mixture of old
(9.0.1.xxxx) and new devices(9.0.2.xxxx) clients
synchronizing with it.

My question is, can I do this, and if not what will I need
to change to make it work.
0
Phil
3/5/2010 2:45:48 PM
sybase.sqlanywhere.mobilink 5254 articles. 0 followers. Follow

5 Replies
805 Views

Similar Articles

[PageSpeed] 16
Get it on Google Play
Get it on Apple App Store

Phil,

If you want to use 9.0.2 MobiLink clients, then you will need to upgrade the MobiLink server to 
9.0.2. This will require you at minimum to update the MobiLink system tables in the 9.0.1 database 
to use the 9.0.2 MobiLink system tables. This is done by running the 9.0.1 upgrade script that is 
provided with the 9.0.2 SQL Anywhere install. The upgrade script can be found in the 
%ASANY9%\MobiLink\upgrade\9.0.1 folder in the 9.0.2 SQL Anywhere install.

If you are upgrading the 9.0.1 to use the 9.0.2 MobiLink system tables, it might be beneficial to 
upgrade the entire database to 9.0.2.

-- 
Joshua Savill
Sybase Inc. - Product Manager


Phil. wrote:
> Currently an application running on an older Symbol device
> with CF 1.x that was built using a 9.0.1.xxxx build is
> synchronizing with a consolidated db of the same 9.0.1.xxxx
> build.
> 
> I am porting the handheld application to an intermec device
> and will need to build using the .NET CF 2.0. In order to do
> this I need to move to a 9.0.2.xxxx SQL anywhere build.
> 
> I'd like to leave the consolidated db alone, since there is
> an amount of time that I will have a mixture of old
> (9.0.1.xxxx) and new devices(9.0.2.xxxx) clients
> synchronizing with it.
> 
> My question is, can I do this, and if not what will I need
> to change to make it work.
0
Josh
3/8/2010 3:49:20 PM
The biggest issue with this approach is the newer-client
connecting to the older-server.  We always recommend
the server to be equal or newer than the the clients;
which is typical, tested and more normal for migrations.
The bottom line is that servers support clients and 
new servers will know about any backwards requirements;
but not so the other way around.

So we would recommend upgrading the ML server and
consolidated database first.  According the the 9.0.2
readme file 

    %asany9%\Mobilink\upgrade\readme.txt

and the 9.0.2 "What's new in version 9.0.2", "Mobilink
behaviour changes" the biggest changes seem mostly 
isolated to QAnywhere tables and so that upgrade should 
change very little from a operational stand point.

Not to mention all those bug fixes . . . . 

HTH and good luck

"Phil." wrote in message news:4b91191c.28d5.1681692777@sybase.com...
> Currently an application running on an older Symbol device
> with CF 1.x that was built using a 9.0.1.xxxx build is
> synchronizing with a consolidated db of the same 9.0.1.xxxx
> build.
> 
> I am porting the handheld application to an intermec device
> and will need to build using the .NET CF 2.0. In order to do
> this I need to move to a 9.0.2.xxxx SQL anywhere build.
> 
> I'd like to leave the consolidated db alone, since there is
> an amount of time that I will have a mixture of old
> (9.0.1.xxxx) and new devices(9.0.2.xxxx) clients
> synchronizing with it.
> 
> My question is, can I do this, and if not what will I need
> to change to make it work.
0
Nick
3/8/2010 3:51:06 PM
So If I were to upgrade the consolidated db to 9.0.2 then
both the old, 9.0.1 clients and the new, 9.0.2 clients could
connect to mobilink with their respective versions of
dbmlsync?

Please verify that I am hearing you correctly.


> The biggest issue with this approach is the newer-client
> connecting to the older-server.  We always recommend
> the server to be equal or newer than the the clients;
> which is typical, tested and more normal for migrations.
> The bottom line is that servers support clients and
> new servers will know about any backwards requirements;
> but not so the other way around.
>
> So we would recommend upgrading the ML server and
> consolidated database first.  According the the 9.0.2
> readme file
>
>     %asany9%\Mobilink\upgrade\readme.txt
>
> and the 9.0.2 "What's new in version 9.0.2", "Mobilink
> behaviour changes" the biggest changes seem mostly
> isolated to QAnywhere tables and so that upgrade should
> change very little from a operational stand point.
>
> Not to mention all those bug fixes . . . .
>
> HTH and good luck
>
> "Phil." wrote in message
> > news:4b91191c.28d5.1681692777@sybase.com... Currently an
> > application running on an older Symbol device with CF
> > 1.x that was built using a 9.0.1.xxxx build is
> synchronizing with a consolidated db of the same
> > 9.0.1.xxxx build.
> >
> > I am porting the handheld application to an intermec
> > device and will need to build using the .NET CF 2.0. In
> > order to do this I need to move to a 9.0.2.xxxx SQL
> > anywhere build.
> > I'd like to leave the consolidated db alone, since there
> > is an amount of time that I will have a mixture of old
> > (9.0.1.xxxx) and new devices(9.0.2.xxxx) clients
> > synchronizing with it.
> >
> > My question is, can I do this, and if not what will I
> > need to change to make it work.
0
Phil
3/8/2010 3:57:58 PM
Both the 9.0.1 and 9.0.2 MobiLink clients (dbmlsync) can connect to the 9.0.2 MobiLink server. It's 
recommended that 9.0.1 and 9.0.2 client synchronize using different script versions.

-- 
Joshua Savill
Sybase Inc. - Product Manager


Phil. wrote:
> So If I were to upgrade the consolidated db to 9.0.2 then
> both the old, 9.0.1 clients and the new, 9.0.2 clients could
> connect to mobilink with their respective versions of
> dbmlsync?
> 
> Please verify that I am hearing you correctly.
> 
> 
>> The biggest issue with this approach is the newer-client
>> connecting to the older-server.  We always recommend
>> the server to be equal or newer than the the clients;
>> which is typical, tested and more normal for migrations.
>> The bottom line is that servers support clients and
>> new servers will know about any backwards requirements;
>> but not so the other way around.
>>
>> So we would recommend upgrading the ML server and
>> consolidated database first.  According the the 9.0.2
>> readme file
>>
>>     %asany9%\Mobilink\upgrade\readme.txt
>>
>> and the 9.0.2 "What's new in version 9.0.2", "Mobilink
>> behaviour changes" the biggest changes seem mostly
>> isolated to QAnywhere tables and so that upgrade should
>> change very little from a operational stand point.
>>
>> Not to mention all those bug fixes . . . .
>>
>> HTH and good luck
>>
>> "Phil." wrote in message
>>> news:4b91191c.28d5.1681692777@sybase.com... Currently an
>>> application running on an older Symbol device with CF
>>> 1.x that was built using a 9.0.1.xxxx build is
>> synchronizing with a consolidated db of the same
>>> 9.0.1.xxxx build.
>>>
>>> I am porting the handheld application to an intermec
>>> device and will need to build using the .NET CF 2.0. In
>>> order to do this I need to move to a 9.0.2.xxxx SQL
>>> anywhere build.
>>> I'd like to leave the consolidated db alone, since there
>>> is an amount of time that I will have a mixture of old
>>> (9.0.1.xxxx) and new devices(9.0.2.xxxx) clients
>>> synchronizing with it.
>>>
>>> My question is, can I do this, and if not what will I
>>> need to change to make it work.
0
Josh
3/8/2010 4:03:44 PM
Basically correct.  The upgrade is to the consolidate and
the ML server both.


"Phil." wrote in message news:4b951e86.5b60.1681692777@sybase.com...
> So If I were to upgrade the consolidated db to 9.0.2 then
> both the old, 9.0.1 clients and the new, 9.0.2 clients could
> connect to mobilink with their respective versions of
> dbmlsync?
> 
> Please verify that I am hearing you correctly.
> 
> 
>> The biggest issue with this approach is the newer-client
>> connecting to the older-server.  We always recommend
>> the server to be equal or newer than the the clients;
>> which is typical, tested and more normal for migrations.
>> The bottom line is that servers support clients and
>> new servers will know about any backwards requirements;
>> but not so the other way around.
>>
>> So we would recommend upgrading the ML server and
>> consolidated database first.  According the the 9.0.2
>> readme file
>>
>>     %asany9%\Mobilink\upgrade\readme.txt
>>
>> and the 9.0.2 "What's new in version 9.0.2", "Mobilink
>> behaviour changes" the biggest changes seem mostly
>> isolated to QAnywhere tables and so that upgrade should
>> change very little from a operational stand point.
>>
>> Not to mention all those bug fixes . . . .
>>
>> HTH and good luck
>>
>> "Phil." wrote in message
>> > news:4b91191c.28d5.1681692777@sybase.com... Currently an
>> > application running on an older Symbol device with CF
>> > 1.x that was built using a 9.0.1.xxxx build is
>> synchronizing with a consolidated db of the same
>> > 9.0.1.xxxx build.
>> >
>> > I am porting the handheld application to an intermec
>> > device and will need to build using the .NET CF 2.0. In
>> > order to do this I need to move to a 9.0.2.xxxx SQL
>> > anywhere build.
>> > I'd like to leave the consolidated db alone, since there
>> > is an amount of time that I will have a mixture of old
>> > (9.0.1.xxxx) and new devices(9.0.2.xxxx) clients
>> > synchronizing with it.
>> >
>> > My question is, can I do this, and if not what will I
>> > need to change to make it work.
0
Nick
3/8/2010 4:10:44 PM
Reply:

Similar Artilces:

9.0.0, 9.0.1, 9.0.2
My shop is moving to PB9 and is about to deploy with 9.0.0 build 5507. How stable is this runtime environment? I assume 9.0.1 and 9.0.2 are better, but that isn't always the case. I'd like to convince folks here that going out with a .0 release is a bit risky, but I haven't found any issues with 9.0.0 yet that require us to go with 9.0.1 or 9.0.2. Should I feel comfortable that 9.0.0 is fine, or are there solid reasons to go with 9.0.1 or 9.0.2 that I haven't found yet? I'd go with the 9.0.1 release - the latest EBF. I haven't personally taken 9.0.2 for ...

Swedish Firefox 0.9, 0.9.1, 0.9.2
Hi, PLEASE NOTE: The Swedish l10n page has moved to http://www.mozilla.se/ This has been previously posted on this list and to mlp-staff, with no reply or update of the mlp status pages. Thus, i repeat: Please update your links! The Swedish (sv-SE) l10n group has releasted language packs and localized builds for Windows and Linux of the Firefox 0.9 versions. Due to the security issues, Windows version prior to 0.9.2 have been removed. These language packs are considered stable and tested. Firefox 0.9.2 pack: http://www.mozilla.se/paket/firefox-0.9.2-svSE.xpi Firefox 0....

EASY QUESTION! Upgrading 9.0.0 to 9.0.2 question
Here's a quick and easy one for you: I am upgrading SQL Anywhere (on redhat 9) from version 9.0.0.1120 to 9.0.2 using the maintenence release, plus the express bug fix to bring me to build 3169. My question: although the server resides on linux, our clients access it via Win98. What do I need to download and install to update the client / isql / sql central on Win98? Please post to newsgroup. Thanks! Jason Boardman Jason, Provided you have already installed the ASA 9.0.0 Network database client components (ISQL and Sybase Central) on the Windows 98 machine, it is n...

Firefox 1.5.0.9, Firefox 2.0.0.1 and Thunderbird 1.5.0.9 Security & Stability Updates
As part of Mozilla Corporation�s ongoing stability and security update process, Firefox 1.5.0.9, Firefox 2.0.0.1 and Thunderbird 1.5.0.9 are now available for Windows, Mac, and Linux for free download from getfirefox.com (http://www.getfirefox.com) & getthunderbird.com (http://www.getthunderbird.com). We strongly recommend that all Firefox users upgrade to this latest release. This update is available immediately in 41 languages including Spanish, Japanese, Arabic, Hungarian and more. Note: Firefox 1.5.0.x will be maintained with security and stability updates until Apr...

Firefox 1.5.0.9, Firefox 2.0.0.1 and Thunderbird 1.5.0.9 Security & Stability Updates
As part of Mozilla Corporation�s ongoing stability and security update process, Firefox 1.5.0.9, Firefox 2.0.0.1 and Thunderbird 1.5.0.9 are now available for Windows, Mac, and Linux for free download from getfirefox.com (http://www.getfirefox.com) & getthunderbird.com (http://www.getthunderbird.com). We strongly recommend that all Firefox users upgrade to this latest release. This update is available immediately in 41 languages including Spanish, Japanese, Arabic, Hungarian and more. Note: Firefox 1.5.0.x will be maintained with security and stability updates until Apr...

Upgrading 9.0.0 to 9.0.1
Hi, We're looking to upgrade the following setup to ASA/Mobilink 9.0.1: ASE 12.5.2 cons under RedHat AS3 ASA 9.0.0.1252 remotes under Windows Mobile 2003 Mobilink 9.0.0.1252 under RedHatAS3 I've read through the 9.0.1 upgrade documention: What's New in SQL Anywhere Studio --Upading Software and Databases ----Upgrading MobiLink Some things are still unclear to me: 2. After having upgraded our ASE cons via the provided sql script, must we run only 9.0.1 Mobilink servers against it? To facilitate the rollout, we considering running the original 9.0.0 Mobili...

Make error: DBD-Oracle-1.14 , DBI-1.39, Oracle rdbms 9.2.0.0.0 , solaris 9
------=_NextPart_000_0025_01C3BE5A.4F6A0C70 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: 7bit Hi, When I make DBD-Oracle 1.14 , Makefile.PL generates a Makefile with "-o build" in the compiler string before blib/arch/auto/DBD/Oracle/Oracle.so and prevents Oracle.so from being built correctly. demo_rdbms.mk appears to be to supplying this: Attempting to discover Oracle OCI build rules^M gcc -B/usr/ccs/bin/ -c DBD_ORA_OBJ.c^M by executing: (make -f /export/home/oracle/ora9idbms/rdbms/demo/demo_rdbms.mk bu ild ECHODO=echo EC...

Bug 378409
Bug 378409 - Update ChatZilla version from 0.9.75.1 to 0.9.78.1 for SM 1.1.2. https://bugzilla.mozilla.org/show_bug.cgi?id=378409 has been Released into the Wild, Wild World Wide Web (...WWWWW. 378409.Bug.Bugzilla.Mozilla.Org/Print :). Thank you, Eddie Maddox Eddie-MacG3 schrieb: > Bug 378409 - Update ChatZilla version from 0.9.75.1 to 0.9.78.1 for SM > 1.1.2. > https://bugzilla.mozilla.org/show_bug.cgi?id=378409 > has been Released into the Wild, Wild World Wide Web (...WWWWW. > 378409.Bug.Bugzilla.Mozilla.Org/Print :). Sorry, this won't be done. No new ...

question : upgrade from ASA 9.0.1 build 1975 to ASA 9.0.2 build 2551
This is a multi-part message in MIME format. ------=_NextPart_000_004A_01C51418.8836CAB0 Content-Type: text/plain; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable When upgrading from ASA 9.0.1 to ASA 9.0.2 is it critical that the = database be unloaded and reloaded or can just the software be updated? Thanks, Dave ------=_NextPart_000_004A_01C51418.8836CAB0 Content-Type: text/html; charset="iso-8859-1" Content-Transfer-Encoding: quoted-printable <!DOCTYPE HTML PUBLIC "-//W3C//DTD HTML 4.0 Transitional//EN"> <HTML...

Upgrade 9.0.1 to 9.0.2
Using 9.0.1 developer's edition, is there any way to upgrade to 9.0.2, or do we need to uninstall 9.0.1 and install 9.0.2? Thanks Wayne MRs can be applied to EVAL and Developer editions. Maintenance releases (MR) and EBFs can be found at 1. Go to http://downloads.sybase.com 2. Logon to mySybase 3. From the product families list, select SQL Anywhere Studio 4. Locate desired MR or EBF. NOTE: 1) You may need to expand the Timeframe dropdown and click GO! to locate older MRs and EBFs. 2) EBFs can only be applied to the appropriate MR. If the EBF is for a later MR...

Upgrading from 9.0.0 to 9.0.2
We are planning to upgrade from 9.0.0 to 9.0.2. The documentation states that we just need to run dbupgrad and then archive the transaction log and start a new one if we do some replication. Is it as easy as this? I can just rename the transaction log and then delete it. Could you share your experience if you have done this already? We are concerned that we will have problems with synchronization when we do this upgrade. Rey Valera wrote in news:45b896ef.3028.1681692777@sybase.com of sybase.public.sqlanywhere.mobilink: RV> We are planning to upgrade from 9.0.0 to 9.0.2. ...

Upgrade from 9.0.1 to 9.0.2
I'm currently up to SQL Anywhere 9.0.1.2085. I want to get to the latest release since I'm playing with Mobilink right now but I can't seem to be able to upgrade to the latest EBF of 9.0.2 from 9.0.1. The iAnywhere update website states: "There are no updates to iAnywhere's SQL Anywhere 9.0.1.2085, for WIN32 at this time." I can see one more EBF for 9.0.1 on Sybase' EBF web site. Does this require purchasing an upgrade to 9.0.2? Thanks in advance, Bob Bob wrote: > > Does this require purchasing an upgrade to 9.0.2? > ...

Upgrade from 9.0.0 to 9.0.1
Hi, i am new with Sybase, so any help is welcome. I have SQL Anyware Studio v.9.0.0 installed and it works, but I need a Lithuanian Collation (it is announced to be available in 9.0.1), so I applied a patch from 9.0.0. to 9.0.1. After this upgrade (and after ALL other available EBFs sequentialy) I cannot connect to my database (Sybase Central loads correctly). Here is a message after I try to load a db using Tools\Connection profiles\Connect... +-----------------+ | Stack Trace | ...

upgrade 9.0.0 to 9.0.1
Ok , I give up, Im at a loss as to why Im having the problems upgrading. I took a clean install of 9.0.0 and ran the upgrade script to go from 9.0.0 to 9.0.1 , I then take the lastest ebf to upgrad 9.0.1 to 9.0.1.1912. Once this is done if I try and create a database I get the following error: [Sybase][ODBC Driver][Adaptive Server Anywhere]Unable to start database server Error code=-80 SQL state=08001 Connection parameters: User=DBA Password=*** ENG=asdfa START=dbeng9 -c 10M -gp 2048 DBN=utility_db I have also tried these same steps on another mac...

Web resources about - 9.0.1 to 9.0.2 question - sybase.sqlanywhere.mobilink

German question - Wikipedia, the free encyclopedia
"Kleindeutschland" redirects here. For the neighborhood in New York City, see Little Germany, Manhattan . 1820 map of Central Europe showing ...

Questions over qualifications of man who recommended giant WA jarrah be cut down
The felling of ancient &quot;king jarrah&quot; in Perth's south last week, which has horrified nature-lovers, was assessed by someone without ...

Question of the Day: Bring back the Brougham?
Filed under: Design/Style Brougham became a commonly used name for a luxed-up option package starting in the 1960s, peaked in the 1970s, and ...

Derek Zoolander has hilarious answers for Vogue’s ‘73 Questions’
If there’s a guy who knows his fashion (or at least he thinks he does), that’s Derek Zoolander. In fact, he practically doesn’t know anything ...

41 of the trickiest questions Google will ask you in a job interview
Google has a reputation for asking difficult brain-teaser questions that challenge how you act under pressure. Most of them require you to think ...

Derek Zoolander answers Vogue’s ’73 Questions’: funny or forced?
For anyone unfamiliar with Vogue’s 73 Questions series, an “interviewer” off camera follows a celebrity around their home/place of employ, asking ...

Podtoid? Oh, yeah, it's recording....ask us questions!
You know what was missing in Podtoid 319: Kangaroo Hotdish ? Questions. Questions from ya'll. Or y'all. Or voi . Man do I want to answer some ...

8 Questions We Have After Watching That Insanely Epic 'Suicide Squad' Trailer
Who is the villain? Where is Harley's accent? Are we all going to love The Joker?

Want To Do Great Things? Get Selfish, and Ask Stupid Questions
If you're feeling a little stuck in your career or your life, try this...

Tennis stars question gambling ads amid match-fixing claims
Tennis stars question gambling ads amid match-fixing claims

Resources last updated: 1/21/2016 3:45:13 PM