cancel
Showing results for 
Search instead for 
Did you mean: 

Have I installed mobilink service 17 correctly?

Former Member
1,687

Hi,

I've installed sql anywhere 17 next to version 12 today and allthough I've tried to follow the steps in the guidelines, I've noticed that not everything is specified:

for example the mobilink server upgrade: http://dcx.sap.com/sqla170/en/html/8158e2de6ce2101497ebcfc6ec1e3286.html

Once I install version 17, I still see the mobilink service pointing to the version 12 executable. So what I decided to do, is to modify this and point to version 17. When I start the service it seems to be working and I can synchronize, but there are a few strange things I'm noticing:

  1. When synchronising the remote server shows a message as following: "Subscription 'OneOfMySubscriptions' - Not Synchronizing - Log offset 0031853831 - Last download time xxxxxxx .... " => nevertheless The sync ends successfully and when I change something in the remote databas, this change ends up in the consolidated database.
  2. I have used the upgrade script as pointed out in the following link: http://dcx.sap.com/sqla170/en/html/8157b77b6ce210149751c22e34065b07.html , but first I tried to upgrade via Sybase central, (by clicking Check Mobilink System Setup) and here I got the following error: invalid sql data type -25

Thank you for your feedback !

Former Member

There is usually more context around that error.

See what happens when you run the correct upgrade script using dbisql (or your DBMS-specific interactive sql utility). For upgrading from 12.0.1 you will need to find the script that matches your DBMS from this location

%sqlany17%\\mobilink\\upgrade\\12.0.1\\upgrade_<DBMS>.sql
where you replace the correct string for your <DBMS>

If you were running with 12.0.0 make sure to use the 12.0.0 directory.

And if that also fails with that error again do note the line throwing that.

Former Member
0 Kudos

Hi,

Thanks for your reply Nick. That's what I did. I ran the upgrade script for 12.0.1 directly in toad for oracle and it ran succesfully without any problems. Are you suggesting that I should try to click "Check Mobilink System Setup" again now?

Former Member

You shouldn't get an error unless you were accidentally using an older/mismatched Sybase Central (version 12 for example).

One thing that may matter is the ODBC driver you are using. Version 16 is only tested with the iAnywhere Solutions 16 ODBC driver for Oracle with an OCI client installation matching the Oracle se... Do read over the Notes and Permissions settings.

When I google search for

      invalid sql data type "-25"

I get plenty of hits about Oracle's ODBC driver not supporting BigInts which would indicate you may be using an older and unsupported ODBC driver.

Former Member
0 Kudos

Thanks for the tip, I'll take a look at the driver. Can this error pose a problem in regular usage? since I've been able to run the upgrade script succesfully and have been able to synchronize data...

Former Member

If it is correct that Blobs lie at the root of this error, then there will likely be an issue if you have long binary columns or binary columns that are bigger than Oracle default buffer size.

There is always a chance that other problems might arise, given there has been no testing with that driver. For instance multiple different drivers [from Oracle and 3rd parties] we have historically seen issues with both long binary and long varchar data and some crashing issues.

Former Member
0 Kudos

Unfortunately no luck. The ODBC driver that was being used was "iAnywhere Solutions 12 - Oracle" (MobiConn12), I added a new one based on "SQL Anywhere 17 - Oracle" (MobiConn17), now not only do I keep getting the same error but also can't sync anymore. Parameters: -c "dsn=MobiConn17" -v -o C:\\Log\\Mobilink\\mls.txt -os 10m -cn 5 -zu+ -w 100 -ds 0 , getting a Consolidated database server or ODBC error : ODBC: [SAP][SQL Anywhere - Oracle][Oracle]ORA-06553: PLS-306: wrong number or types of arguments in call to 'DOWNLOAD_DELETE_CURSOR_NND'

Breck_Carter
Participant
0 Kudos

> ODBC: [SAP][SQL Anywhere - Oracle][Oracle]ORA-06553: PLS-306: wrong number or types of arguments in call to 'DOWNLOAD_DELETE_CURSOR_NND'

Turn on verbose diagnostic logging mlsrv17 -v+ and then post the text before and after that error message.

Accepted Solutions (0)

Answers (0)