SAP SQL Anywhere Supported Platforms and Engineering Support Status

February 1, 2013, 7:59 am

≫ Next: Send ddl commands to remote clients change schemas mobilink 16.0

≪ Previous: SQL Anywhere 17 - A More Worldly sa_validate() procedure

IMPORTANT: The information in this document is subject to change. Please read any notes pertaining to a specific operating system for more details. The ability for the SQL Anywhere engineering team to address issues on operating systems that are no longer supported by the O/S vendor may be limited.

The tables below summarize the platforms supported by SAP SQL Anywhere. The following information is available:

SQL Anywhere for PC Platforms

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
Windows 7	x86 and x64
Windows 8.x	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2003 R2 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2	x64

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #1691 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2 EBF #1691 or higher required	x64
Windows CE/Mobile Version	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #3797 or higher required for Windows 8 EBF #3994 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #3797 or higher required	x64
Windows Server 2012 R2 EBF #3994 or higher required	x64
Windows CE/Mobile Version	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows CE/Mobile Version	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Windows Version	Chipset
2000 (see Operating Systems Note #2)	x86
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7 Tested with EBF #2324	x86 and x64
Windows 8 EBF #2878 or higher required	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2 Tested with EBF #2324	x64
Windows Server 2012 EBF #2878 or higher required	x64
Windows CE/Mobile Version	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x EBF #2376 or higher required	ARMv4i

SQL Anywhere for Linux, Unix and OS X Platforms

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset 64-bit server + 32-bit and 64-bit client support
Coming soon!
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
Coming soon!
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
Coming soon!
OS X Version	Chipset
Coming soon!

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86, x64 and ARM
Solaris Version	Chipset 64-bit server + 32-bit and 64-bit client support
10 Java graphical administrative tools supported for SPARC, but not for x64	SPARC and x64
11	SPARC and x64
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
11i v2	IA64 on Itanium 2
11i v3	IA64 on Itanium 2
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
6.1	POWER
7.1	POWER
OS X Version	Chipset
10.8	x64

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version Click here for list of required Solaris patches	Chipset 64-bit server + 32-bit and 64-bit client support
9	SPARC
10 Java graphical administrative tools supported for SPARC, but not for x64	SPARC and x64
11 Solaris SPARC tested with EBF #3574 and requires JRE 6 Update 31 (JRE 1.6.0_31) available here. Instructions on updating the SQL Anywhere JRE are available here: http://scn.sap.com/docs/DOC-41203. Solaris x64 tested with EBF #3523	SPARC and x64
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
11i v2	IA64 on Itanium 2
11i v3	IA64 on Itanium 2
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
5.3	POWER
6.1	POWER
7.1 EBF #3469 or higher required	POWER
OS X Version	Chipset
10.5	x64
10.6	x64
10.7 EBF #3577 or higher required	x64

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version Click here for list of required Solaris patches	Chipset 64-bit server + 32-bit and 64-bit client support
9	SPARC
10 Java graphical administrative tools supported for SPARC, but not for x64	SPARC and x64
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
11i v2	IA64 on Itanium 2
11i v3	IA64 on Itanium 2
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
5.3	POWER
6.1	POWER
OS X Version	Chipset
10.5	x64
10.6	x64

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version Click here for list of required Solaris patches	Chipset 64-bit server + 32-bit and 64-bit client support
8	SPARC
9	SPARC
10 Java graphical administrative tools supported for SPARC, but not for x64	SPARC and x64
11 Tested with EBF #2753	SPARC and x64
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
11i v2	IA64 on Itanium 2
11i v3	IA64 on Itanium 2
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
5.3 TL07 or higher	POWER
6.1	POWER
7.1 EBF #2637 or higher required	POWER
OS X Version	Chipset
10.5	x64
10.6 EBF #2449 or higher required	x64

MobiLink Synchronization for PC Platforms

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
Windows 7	x86 and x64
Windows 8.x	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2003 R2 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2	x64

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #1691 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2 EBF #1691 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #3797 or higher required for Windows 8 EBF #3994 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #3797 or higher required	x64
Windows Server 2012 R2 EBF #3994 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Windows Version	Chipset
2000 (see Operating Systems Note #2)	x86
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7 Tested with EBF #2324	x86 and x64
Windows 8 EBF #2878 or higher required	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2 Tested with EBF #2324	x64
Windows Server 2012 EBF #2878 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x EBF #2376 or higher required	ARMv4i

MobiLink Synchronization for Linux, Unix and OS X Platforms

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset
Coming soon!
AIX Version	Chipset
Coming soon!
OS X Version	Chipset
Coming soon!

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64 ARM (MobiLink Client only)
Solaris Version	Chipset
10	SPARC
11	SPARC
AIX Version	Chipset
6.1	POWER
7.1	POWER
OS X Version	Chipset
10.8	x64

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset
9	SPARC
10	SPARC
11 Solaris SPARC tested with EBF #3574 and requires JRE 6 Update 31 (JRE 1.6.0_31) available here. Instructions on updating the SQL Anywhere JRE are available here: http://scn.sap.com/docs/DOC-41203.	SPARC
AIX Version	Chipset
5.3	POWER
6.1	POWER
7.1 EBF #3469 or higher required	POWER
OS X Version	Chipset
10.5	x64
10.6	x64
10.7 EBF #3577 or higher required	x64

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset
9	SPARC
10	SPARC
AIX Version	Chipset
5.3	POWER
6.1	POWER
OS X Version	Chipset
10.5	x64
10.6	x64

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset
8	SPARC
9	SPARC
10	SPARC
11 Tested with EBF #2753	SPARC
AIX Version	Chipset
5.3	POWER
6.1	POWER
7.1 EBF #2637 or higher required	POWER
OS X Version	Chipset
10.5	x64
10.6 EBF #2449 or higher required	x64

QAnywhere Client for PC Platforms

SQL Anywhere 16.0 and higher does not include QAnywhere.

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #3797 or higher required for Windows 8 EBF #3994 or higher required for Windows 8.1	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #3797 or higher required	x64
Windows Server 2012 R2 EBF #3994 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Windows Version	Chipset
2000 (see Operating Systems Note #2)	x86
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7 Tested with EBF #2324	x86 and x64
Windows 8 EBF #2878 or higher required	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2 Tested with EBF #2324	x64
Windows Server 2012 EBF #2878 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i

UltraLite

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
Windows 7	x86 and x64
Windows 8.x	x86 and x64
Windows 10	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2	x64
Windows CE/Mobile/Phone Version	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Windows Phone 8.1	ARM x86 for emulator only
Android Version	Chipset
4.1 or later	ARM v7 x86, x86_64
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
Current version
Linux Version	Chipset
Click here for details.	x64
OS X Version	Chipset
10.9+	x86_64

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #1691 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows RT EBF #1716 or higher required	ARMv7, x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2 EBF #1691 or higher required	x64
Windows CE/Mobile/Phone Version	Chipset
Pocket PC 2003 Encrypted MobiLink communications (RSA, FIPS) and M-Business Anywhere are not supported	ARM
Windows CE 4.x	ARM
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Windows Phone 8 EBF #1716 or higher required	ARM x86 for emulator only
Android Version	Chipset
2.2 or later	ARM v7
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
5 +	ARMv7s, ARM64, i386, x86_64
BlackBerry Version	Chipset
4.1 and later, but not BlackBerry 10	ARM
J2SE Version	Chipset
1.7	n/a
Linux Version	Chipset
Click here for details.	x64
OS X Version	Chipset
10.8 +	x64

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8 EBF #3797 or higher required	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #3797 or higher required	x64
Windows Server 2012 R2 EBF #3994 or higher required
Windows CE/Mobile Version	Chipset
Pocket PC 2003 EBF #3484 or higher required FIPS certification is not supported	ARM
Windows CE 4.x EBF #3484 or higher required	ARM
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Android Version	Chipset
1.5 or later	ARM
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
5+	ARMv7s, ARM64, i386, x86_64
BlackBerry Version	Chipset
4.1 or later	ARM
J2SE Version	Chipset
1.5	n/a
Linux Version	Chipset
Click here for details.	x86
OS X Version	Chipset
10.8 +	x64

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows CE/Mobile Version	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Android Version	Chipset
Not supported	n/a
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
3 or later	ARMv6, ARMv7 i386
BlackBerry Version	Chipset
4.1 or later	ARM
J2SE Version	Chipset
1.5	n/a
Linux Version	Chipset
Kernels 2.6.10_mvl401-pc_target and 2.6.13	x86

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8 EBF #2878 or higher required	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #2878 or higher required	x64
Windows CE/Mobile Version	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Android Version	Chipset
1.5 or later	ARM
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
Not supported	n/a
BlackBerry Version	Chipset
4.1 or later	ARM
J2SE Version	Chipset
1.5	n/a
Linux Version	Chipset
Kernels 2.6.10_mvl401-pc_target and 2.6.13	x86
Palm OS Version	Chipset
4.1 or 5.0	68K

Engineering Support Status for SAP SQL Anywhere

This section describes which version of SAP SQL Anywhere are actively supported by engineering, which versions have limited engineering support, and which versions are no longer supported by engineering.

Product	Version	Status (see table below for definition)
SQL Anywhere	17.0	Active
SQL Anywhere	16.0	Active
SQL Anywhere	12.0.1	Active
SQL Anywhere	12.0.0	Limited
SQL Anywhere	5.x, 6.x, 7.x, 8.x, 9.x, 10.x, 11.x	Archived
Watcom SQL	All	Archived

The following table describes the active, limited, and archived status in the above tables.

Active	Most bugs are fixed EBFs (Express Bug Fixes) are issued regularly
Limited	Only serious bugs are fixed EBFs are issued only for serious bugs
Archived	No bugs are fixed No EBFs are issued

Mainstream Maintenance

The following table lists the dates when SQL Anywhere versions will reach the end of mainstream maintenance.

SQL Anywhere Version	End of Mainstream Maintenance
17.x	August 30, 2022
16.x	December 31, 2018
12.x	December 31, 2016
11.x	May 31, 2014
10.x	January 25, 2012
9.x	January 31, 2010

Operating Systems Notes

1 Windows XP support ended April 8, 2014 as documented by Microsoft here: http://www.microsoft.com/en-us/windows/enterprise/end-of-support.aspx.

2 Windows 2000 support ended July 13, 2010 as documented by Microsoft here: https://support.microsoft.com/en-ca/lifecycle?C2=1131.

3 Windows Server 2003 and Windows Server 2003 R2 support ended July 14, 2015 as documented by Microsoft here: https://technet.microsoft.com/library/cc706993.

↧

Send ddl commands to remote clients change schemas mobilink 16.0

September 17, 2015, 3:29 pm

Latest and popular articles on SAP ERP

≫ Next: How to disallow read/write client files from the client?

≪ Previous: SAP SQL Anywhere Supported Platforms and Engineering Support Status

We need to send create tables and alter tables to all the remote clients in ASA 16.0. We need to do this thru mobilink. But i need to send via an script not syabse central gui. anyone know how to do it or whee i can find an example? I already read about remote task also but didnt find if we can send the change thru script and not sybase central.

Thanks

↧

How to disallow read/write client files from the client?

September 16, 2015, 12:57 pm

Latest and popular articles on SAP ERP

≫ Next: Sybase ADO .Net Provider Error Read Access on sysuserperm

≪ Previous: Send ddl commands to remote clients change schemas mobilink 16.0

Hi all,

I've been asked to determine if the client (be it dbisql, ODBC/SQL Anywhere driver, etc) can disallow the reading/writing of client files. I know this is normally controlled by the IQ / SQL Anywhere servers but if a bad guy was able to gain control of the db server or place a proxy inbetween the client and the server, the bad guy could potentially read/write files on the clients.

http://dcx.sybase.com/1200/en/dbusage/client-side-blobs.html

So... is it possible for the client application to disallow read/write of client files?

jason

↧

Sybase ADO .Net Provider Error Read Access on sysuserperm

September 18, 2015, 3:30 am

Latest and popular articles on SAP ERP

≫ Next: SAP SQL Anywhere 12.0.1 Components by Platform

≪ Previous: How to disallow read/write client files from the client?

Hello,

database user without dba right couldn`t create a datareader via SACommand.

The result is an exception from method _ExcuteReader.

The user needs read Access to sysuserperm!

It looks like a new join on sysuserperm instead of sysuserperms.

Provider before this fix works fine.

================(Build #2147 - Engineering Case #785764)================

When using the .NET GetSchemaTable() method for a query on a table whose

name was not unique, an exception could have occurred in the provider. This

problem has been fixed.

For example, suppose the following query was executed against the table

“employees” owned by DBA, and there also exists a table “Employees” owned

by the user GROUPO.

SACommand cmd = new SACommand("SELECT * FROM DBA.employees", conn);

SADataReader reader = cmd.ExecuteReader();

DataTable schema = reader.GetSchemaTable();

An exception was raised in the GetSchemaTable call. When the tables have

the same letter case, then an exception would not have occurred but the wrong

schema information could have been returned.

best regards

Jörg

↧

SAP SQL Anywhere 12.0.1 Components by Platform

February 6, 2013, 1:08 pm

Latest and popular articles on SAP ERP

≫ Next: Recommended ODBC Drivers for 17.0.0 MobiLink

≪ Previous: Sybase ADO .Net Provider Error Read Access on sysuserperm

The following tables list components that are available across each platform supported by SAP SQL Anywhere. Note that, with a few exceptions, components that are available in all supported platforms are not listed. For ease of reading, the platforms are grouped by operating system vendor, operating system name and processor architecture.

Information about support for a specific operating system version is located at SAP SQL Anywhere Supported Platforms and Engineering Support Status.

The following tables are available:

Databases
- SQL Anywhere
- UltraLite
Synchronization, Messaging and Replication
Administration Tools
Documentation

Databases

SQL Anywhere

Note: SQL Anywhere 12 database servers support connections from client applications using software from version 6.0.0 or later. Version 5 and earlier clients cannot connect to a version 12 database server.

Components	Microsoft Windows			Linux		Sun Solaris		Apple Mac OS X		IBM AIX³¹	HP-UX
Components	x86	x64	Mobile	x86	x64	SPARC	x64	x86	x64	PPC	IA64
Personal database server	X	X		X	X	X²⁷	X	X		X¹⁹	X²⁶
Network database server	X	X	X	X	X	X²⁷	X	X		X¹⁹	X²⁶
Remote data access	X	X		X	X	X	X	X
External stored procedures	X	X²		X	X	X	X	X		X	X
Dynamic cache sizing	X	X	X	X	X	X	X	X		X	X
C++ development tools	X			X	X	X	X	X		X	X
5.0 Compatibility DLLs	X
International Resource Deployment Kit	X	X
Accessibility enablement	X
Samples	X	X	X	X	X	X	X	X		X	X
Sun JRE 1.6.0	X	X		X		X
RSA Encrypted Client-Server Communications	X	X	X	X	X	X	X	X	X	X	X
Java in the database	X	X		X	X	X	X	X		X	X
Kerberos clients ³²	X			X		X	X	X		X	X
Components	Microsoft Windows			Linux		Sun Solaris		Apple Mac OS X		IBM AIX³¹	HP-UX
Components	x86	x64	Mobile	x86	x64	SPARC	x64	x86	x64	PPC	IA64
Interfaces
ODBC ³	X	X	X	X	X²³	X²³	X²³	X	X	X²³	X²³
OLE DB	X	X	X
ADO.NET	X	X	X
Embedded SQL	X	X	X	X	X²³	X²³	X²³	X	X	X²³	X²³
Open Client	X	X		X		X²³		X		X²³
iAnywhere JDBC ⁵	X	X		X	X²³	X²³	X	X	X	X²³	X²³
jConnect	X	X		X	X²³	X²³	X	X		X²³	X²³
PHP	X			X
Perl DBD	X	X		X	X	X	X	X		X	X
Database tools	X	X	X	X	X²³	X²³	X²³	X		X²³	X²³
Database utilities
Histogram (dbhist)	X	X
Language (dblang)	X	X
Service creation (dbsvc)	X	X		X	X
All other utilities	X	X		X	X	X	X	X		X	X
Components	Microsoft Windows			Linux		Sun Solaris		Apple Mac OS X		IBM AIX³¹	HP-UX
Components	x86	x64	Mobile	x86	x64	SPARC	x64	x86	x64	PPC	IA64
Separately licensed components
ECC Encrypted Client-Server Communications	X	X		X	X	X	X			X	X
FIPS Approved Encrypted Client-Server Communications	X	X		X	X
High availability	X	X		X	X	X	X	X		X	X
Read-only scale-out	X	X		X	X	X	X	X		X	X

UltraLite

Components	Microsoft Windows			RIM	Google	Apple
Components	x86/x64	Mobile	PPC 2003 ²⁰	BlackBerry	Android	iOS	Mac OS X	Java ME/SE	Linux x86 ²⁴
UltraLite databases	X	X	X			X	X		X
UltraLite engine	X	X	X						X
UltraLiteJ	X			X³³	X			X
Runtime APIs
UL embedded SQL	X⁹	X	X				X		X
UL C++ component	X⁹	X	X			X	X		X
UL for M-Business Anywhere	X⁹	X¹²
UltraLite.NET	X⁹	X¹⁰	X¹⁰
Synchronization
TCP/IP	X	X	X			X	X		X
HTTP or HTTPS	X	X	X³⁵	X	X	X	X	X	X
ActiveSync ⁸		X¹⁴	X¹⁴
RSA Encrypted MobiLink Communications	X	X	X³⁵		X	X	X		X
Separately licensed components
ECC Encrypted MobiLink Communications	X	X							X
FIPS Approved Encrypted MobiLink Communications	X	X

Synchronization, Messaging and Replication

MobiLink

Components	Microsoft Windows			Linux		Sun Solaris		Apple Mac OS X		IBM AIX³¹	HP-UX
Components	x86	x64	Mobile	x86	x64	SPARC	x64	x86	x64	PPC	IA64
MobiLink Server
MobiLink synchronization server	X	X¹⁵		X	X¹⁵	X^27,34			X	X¹⁹
.NET synchronization logic	X	X¹⁵
Java synchronization logic	X	X¹⁵		X	X¹⁵	X			X	X¹⁸
Notifier ²⁸	X	X¹⁵		X	X¹⁵	X			X	X¹⁸
RSA Encrypted MobiLink Communications	X	X¹⁵		X	X¹⁵	X			X	X
Samples
Samples	X	X		X	X	X			X
Relay Server
Relay Server	X	X		X	X
MobiLink Monitor
MobiLink monitor	X	X		X	X	X			X
MobiLink Client
MobiLink client for SQL Anywhere	X	X	X	X	X	X		X
Listener ²⁹	X	X⁴		X
MobiLink ActiveSync provider ²²	X
RSA Encrypted MobiLink Communications	X	X	X	X	X	X		X	X
Separately licensed components
ECC Encrypted MobiLink Communications	X	X¹⁵	X	X	X¹⁵	X				X
FIPS Approved Encrypted MobiLink Communications	X	X¹⁵	X	X	X¹⁵

For a list of platforms that can run the Relay Server and a list operating systems that it was tested on, please refer to this document.

The MobiLink server communicates with the consolidated databases through an ODBC driver. The ODBC driver may not be available for some consolidated databases on some platforms. The consolidated database and MobiLink server are not required to run on the same platform. Provided the consolidated database is running on a supported platform as specified by the database vendor, and the MobiLink server is communicating with the consolidated database using a supported ODBC driver, this is considered a supported MobiLink server configuration. The following table lists the platforms that can run the MobiLink server for supported consolidated databases.

For more details about the ODBC drivers, please refer to the document Recommended ODBC Drivers for MobiLink.

Consolidated databases	Microsoft Windows			Linux		Sun Solaris		Apple Mac OS X		IBM AIX³¹	HP-UX
Consolidated databases	x86	x64	Mobile	x86	x64	SPARC	x64	x86	x64	PPC	IA64
SAP SQL Anywhere 11 and 12	X	X¹⁵		X	X¹⁵	X			X	X
SAP Adaptive Server Enterprise 15.0 and 15.5	X	X¹⁵		X	X¹⁵
SAP IQ 15.2		X¹⁵			X¹⁵
Oracle 10g and 11g	X	X¹⁵		X	X¹⁵	X				X
Microsoft SQL Server 2005 and 2008	X	X¹⁵
IBM DB2 UDB LUW 9.5 and 9.7	X	X¹⁵		X	X¹⁵
MySQL 5.1	X	X¹⁵		X	X¹⁵

QAnywhere²¹

Components	Microsoft Windows			Linux		Sun Solaris		Apple Mac OS X		IBM AIX³¹	HP-UX
Components	x86	x64	Mobile	x86	x64	SPARC	x64	x86	x64	PPC	IA64
MobiLink synchronization server with Messaging enabled	X	X¹⁵		X	X¹⁵	X²⁷			X	X^{18, 19}
Agent	X		X
.NET API	X		X
C++ API	X		X
Java API	X		X²⁵
Samples (client)	X		X

SQL Remote for SQL Anywhere

Components	Microsoft Windows			Linux		Sun Solaris		Apple Mac OS X		IBM AIX³¹	HP-UX
Components	x86	x64	Mobile	x86	x64	SPARC	x64	x86	x64	PPC	IA64
SQL Anywhere Message Agent (dbremote)	X	X	X	X		X⁴		X	X⁴
SQL Anywhere extraction utility (dbxtract)	X	X		X		X⁴		X	X⁴
File sharing message system	X	X	X	X		X⁴		X	X⁴
FTP message system ¹⁷	X	X	X	X		X⁴		X	X⁴
SMTP/POP message system ¹⁷	X	X	X	X		X⁴		X	X⁴
SA encoding (dbencod)	X	X		X		X⁴		X	X⁴

Administration Tools

Components	Microsoft Windows			Linux		Sun Solaris		Apple Mac OS X		IBM AIX³¹	HP-UX
Components	x86	x64	Mobile	x86	x64	SPARC	x64	x86	x64	PPC	IA64
Administration Tools
Sybase Central	X	X⁶		X	X⁶	X			X
Interactive SQL	X	X⁶		X	X⁶	X	X⁷		X	X⁷	X⁷
Database network server connections monitor (dbconsole) ³⁰	X	X⁶		X	X⁶	X			X
Database and synchronization server monitor (Web-based SQL Anywhere Monitor) ¹	X	X		X	X
PowerDesigner	X
InfoMaker	X

Compatibility with existing Sybase Central software

Full support - The SQL Anywhere plug-in for Sybase Central fully supports any database created by version 10 or later software running on a version 10 or later server. For example, version 10 databases running on version 10, 11, or 12 servers; version 11 databases running on version 11 or 12 database servers; and version 12 databases running on a version 12 database server.
Unload/reload-only support - For databases created by version 5, 6, 7, 8, or 9 software running on a version 6, 7, 8, or 9 database server, you can connect to the database from the SQL Anywhere plug-in temporarily to do one of the following tasks:
- Unload the database into a reload file.
- Unload and reload the database into a new version 12 database.
- Unload and reload the database into an existing version 12 database.

The files for the database being unloaded must be located on the local computer.

No support - There is no support in the SQL Anywhere plug-in for databases created by version 4 or earlier software running on a version 5 or earlier server.

Documentation

The complete SQL Anywhere documentation is available in four formats:

DocCommentXchange DocCommentXchange is a community for accessing and discussing SQL Anywhere documentation on the web. To access the documentation, go to http://dcx.sybase.com.
HTML Help On Windows platforms, the HTML Help contains the complete SQL Anywhere documentation, including the books and the context-sensitive help for SQL Anywhere tools. To access the documentation, choose Start » Programs » SQL Anywhere » Documentation » HTML Help (English).
Eclipse On Unix platforms, the complete Help is provided in Eclipse format. To access the documentation, run sadoc from the bin32 or bin64 directory of your SQL Anywhere installation.
PDF The complete set of SQL Anywhere books is provided as a set of Portable Document Format (PDF) files. You must have a PDF reader to view information.

To access the PDF documentation on Windows operating systems, choose Start » Programs » SQL Anywhere » Documentation » PDF (English).

To access the PDF documentation on Unix operating systems, use a web browser to open /documentation/en/pdf/index.html under the SQL Anywhere installation directory.

Footnotes

¹ The SQL Anywhere Monitor can be installed under Windows and Linux. The Web-based interface can be accessed on any platform with a JavaScript-enabled browser and the latest version of Adobe Flash Player.

² The older interface to external stored procedures is available only in 32-bit software.

³ ODBC driver manager may not be available. May have to link directly to ODBC driver.

⁴ 32-bit software.

⁵ Requires JRE 1.4 or higher on Itanium chips. Requires JRE 1.3 or higher on other chips.

⁶ 32-bit JRE.

⁷ Does not include certain features, compared to the admin tools provided on other operating systems.

⁸ Requires Microsoft ActiveSync 3.1 or higher.

⁹ 64-bit development requires the 32-bit utilities. Connecting to an UltraLite database from a 64-bit machine requires the 32-bit versions of Interactive SQL and Sybase Central.

¹⁰ Requires .NET Compact Framework version 2.0 or 3.5.

¹¹ Requires SQL Anywhere 11.0.1 build #2255 or higher.

¹² Requires Windows Mobile 5 or later.

¹³ Requires Palm OS 5.

¹⁴ Not supported for M-Business Anywhere.

¹⁵ Only 64-bit MobiLink server components are supported on 64-bit operating systems.

¹⁷ For all systems other than the file sharing system, you must have purchased and installed the appropriate message system software for SQL Remote to function over this system. SQL Remote does not include the underlying message system software.

¹⁸ Set LIBPATH to include the directory containing an installed JRE.

¹⁹ AIX 5.3 TL07 or higher required for IPv6 support. Only 64-bit software is supported.

²⁰ Pocket PC 2003 support requires EBF #3484 or later.

²¹ QAnywhere does not support MySQL.

²² Requires Microsoft ActiveSync 3.5 or higher.

²³ 32-bit and 64-bit clients.

²⁴ Tested on the following platforms:

MontaVista Linux 4.0.1 (Linux version 2.6.10_mvl401-pc_target (gcc version 3.4.3 (MontaVista 3.4.3-25.0.70.0501961 2005-12-17)))
SUSE Linux 10.0 (Linux version 2.6.13 (gcc version 4.0.2))

²⁵ Requires IBM J9 Java virtual machine.

²⁶ Requires HP Transport Optional Upgrade Release (TOUR) 3.1 or higher, available from http://software.hp.com.

²⁷ Requires the following patches (or superseding ones). For Solaris 8: 109322-02, 108434-22, 108435-22, 111721-04. For Solaris 9: 111711-16, 111712-16, 111722-05. Please note that although we list patches for the specific issues that we encounter, it is not an exhaustive list and we recommend that you always install the OS patches suggested by the OS vendor. Only 64-bit software is supported.

²⁸ Requires JRE 1.4.1 or higher

²⁹ For a list of operating systems that the Listener was tested on, please refer to this document.

³⁰ For Windows CE, Solaris x64, AIX, HP-UX, and Linux Itanium: On these platforms you can use the connection, database, and server properties to obtain information or you can monitor your server from a computer running an operating system that supports the SQL Anywhere Console (such as Windows XP/200x, Mac OS X, or Linux).

³¹ AIX 5.3 requires the IY79612 fix. Please note that although we list patches for the specific issues that we encounter, it is not an exhaustive list and we recommend that you always install the OS patches suggested by the OS vendor.

³² A list of Kerberos clients tested with SQL Anywhere is available here: http://www.sybase.com/detail?id=1096369.

³³ BlackBerry OS 4.1 or higher. BlackBerry OS 7 support requires EBF #3531 or later.

³⁴ 64-bit Solaris SPARC only.

³⁵ RSA TLS and HTTPS for Pocket PC 2003 requires EBF #3584 or later.

↧

Recommended ODBC Drivers for 17.0.0 MobiLink

September 21, 2015, 9:01 am

Latest and popular articles on SAP ERP

≫ Next: ODBC Driver for SQL Anywhere 11 very slow

≪ Previous: SAP SQL Anywhere 12.0.1 Components by Platform

Recommended ODBC Drivers for 17.0.0 MobiLink

The MobiLink server connects to several types of consolidated database using the ODBC 3.5 standard. For some supported consolidated database types you should use the SAP SQL Anywhere ODBC driver for that type of database. For others we recommend drivers supplied by the database vendors. The SAP SQL Anywhere ODBC drivers and the MobiLink server are included in the SAP SQL Anywhere 17 product. When SAP does not provide an ODBC driver, then you must use one provided by another vendor. ODBC drivers from other vendors may not support some optional ODBC functionality that the MobiLink server requires.

Recommended Drivers

As a result of our testing, we recommend the following ODBC drivers for use with version 17.0.0 of the MobiLink server.

If you are having problems with an older version of MobiLink, you should consider upgrading to a newer version. Older versions may no longer be actively supported. For more information, see SAP SQL Anywhere Supported Platforms and Engineering Support Status.

The following sections list the recommended ODBC driver for different types of consolidated database. In some cases, alternative drivers are also listed. Click on one of the consolidated DBMS types below to see recommended driver information for using MobiLink with that type of DBMS:

For detailed supported consolidated databases, please refer to MobiLink Consolidated Database Support .

SAP SQL Anywhere (SQLA) 16.0 and 17.0

SAP SQL Anywhere (SQLA) 16.0

Driver	SAP SQL Anywhere 16.0
Version	16.0.x
Status	Recommended for use with MobiLink
Client s/w	None
OS	Windows	7, 8, Server 2003, Server 2008, Server 2008 R2, Server 2012, and Server 2012 R2
	Linux	Redhat Enterprise Linux 5, 6, and 7 SuSE Enterprise Linux 12 Supported where the kernel/glibc versions are within the ranges specified on the SAP SQL Anywhere Supported Linux Platforms.
	Solaris	10, 11
	AIX	6.1, 7.1
	MAC OS X	10.8 (Intel)
Pros	All tests passed
Cons	None
Notes	None
Permission requirements	The MONITOR system privilege is required in order to invoke the locking/blocking detection logic.

SAP SQL Anywhere (SQLA) 17.0.0

Driver	SAP SQL Anywhere 17.0.0
Version	17.0.0
Status	Recommended for use with MobiLink
Client s/w	None
OS	Windows	7, 8, Server 2003, Server 2008, Server 2008 R2, Server 2012, and Server 2012 R2
	Linux	Redhat Enterprise Linux 5, 6, and 7 SuSE Enterprise Linux 12 Supported where the kernel/glibc versions are within the ranges specified on the SQL Anywhere Supported Linux Platforms.
	Solaris	10, 11
	AIX	6.1, 7.1
	MAC OS X	10.8 (Intel)
Pros	All tests passed
Cons	None
Notes	None
Permission requirements	The MONITOR system privilege is required in order to invoke the locking/blocking detection logic.

SAP Adaptive Server Enterprise 15.7 and 16.0

SAP Adaptive Server Enterprise 15.7

Driver	SAP Adaptive Server Enterprise ODBC driver
Version	16.00.00.05 on Windows (x86 and x64) and Linux (x86 and x64) - This driver is available from the SAP Adaptive Server Enterprise SDK 16.0 PL05.
Status	Recommended for use with MobiLink
Client s/w	None
OS	Windows	7 and Server 2008 R2
	Linux	Redhat Enterprise Linux 5, 6, and 7 SuSE Enterprise 12
Pros	All tests passed
Cons	On Linux, if UseCursor=1, the synchronization tables can't be dropped after synchronization.
Notes	Always set UseCursor to 0 (zero) on Linux. Always set ServerInitiatedTransactions to 0 (zero). Set AnsiNull to 1, if the "where clauses" in any of the upload and download scripts contain the clause "column_name = NULL". On Linux, you need to set SYBASE environment variable to the directory where you install the ASE SDK 16.0 PL05, otherwise, you will get the error, "Could not load code page for requested charset". On Linux, SAP provides two 64-bit ASE ODBC drivers, libsybdrvodb-sqllen4.so and libsybdrvodb-sqllen8.so. The former defines SQLLEN (an ODBC data type) as a 32-bit integer and the latter defines SQLLEN as a 64-bit integer. The 64-bit MobiLink server on Linux assumes SQLLEN is a 64-bit integer. Therefore, the ASE ODBC driver, libsybdrvodb-sqllen8.so should always be used, when a DSN is configurated for the 64-bit MobiLink server to use. By default, the ASE ODBC driver from SDK 16.0 PL05 will trim all blank padding in upload and download strings. If you do not want the driver to trim blank padding, add the following connection parameter to the MobiLink server connection string: stripblanks=0 The connection string of the MobiLink server will look like the following: -c "dsn=...;...;stripblanks=0"
Permission requirements	Select permission on MASTER..SYSTRANSACTIONS and MASTER..SYSPROCESSES. The user ID also needs to have the dtm_tm_role role, if the MobiLink server command line option -cs is used.

SAP Adaptive Server Enterprise 16.0

Driver	SAP Adaptive Server Enterprise ODBC driver
Version	16.00.00.05 on Windows (x86 and x64) and Linux (x86 and x64) - This driver is available from the SAP Adaptive Server Enterprise SDK 16.0 PL05.
Status	Recommended for use with MobiLink
Client s/w	None
OS	Windows	7 and Server 2008 R2
	Linux	Redhat Enterprise Linux 5, 6, and 7 SuSE Enterprise 12
Pros	All tests passed
Cons	On Linux, if UseCursor=1, the synchronization tables can't be dropped after synchronization.
Notes	Always set UseCursor to 0 (zero) on Linux. Always set ServerInitiatedTransactions to 0 (zero). Set AnsiNull to 1, if the "where clauses" in any of the upload and download scripts contain the clause "column_name = NULL". On Linux, you need to set SYBASE environment variable to the directory where you install the ASE SDK 16.0 PL05, otherwise, you will get the error, "Could not load code page for requested charset". On Linux, SAP provides two 64-bit ASE ODBC drivers, libsybdrvodb-sqllen4.so and libsybdrvodb-sqllen8.so. The former defines SQLLEN (an ODBC data type) as a 32-bit integer and the latter defines SQLLEN as a 64-bit integer. The 64-bit MobiLink server on Linux assumes SQLLEN is a 64-bit integer. Therefore, the ASE ODBC driver, libsybdrvodb-sqllen8.so should always be used, when a DSN is configurated for the 64-bit MobiLink server to use. By default, the ASE ODBC driver from SDK 16.0 PL05 will trim all blank padding in upload and download strings. If you do not want the driver to trim blank padding, add the following connection parameter to the MobiLink server connection string: stripblanks=0 The connection string of the MobiLink server will look like the following: -c "dsn=...;...;stripblanks=0" When the "enable functionality group" configuration parameter is enabled on the ASE 15.7 server, the MobiLink server will use the "select ... for update" feature to lock remote IDs to prevent redundant syncs for the same remote ID simultaneously. If for some reason, this feature needs to be disabled, all the MobiLink servers currently connected to the ASE server need to be restarted. Otherwise, the MobiLink servers will fail all the synchronization requests.
Permission requirements	Select permission on MASTER..SYSTRANSACTIONS and MASTER..SYSPROCESSES. The user ID also needs to have the dtm_tm_role role, if the MobiLink server command line option -cs is used.

SAP IQ 15.4 and 16.0

SAP IQ 15.4

Driver	SAP IQ ODBC driver
Version	12.00.01.3019 on Windows (x64) and 12.00.01.3761 on Linux (x64) - Both drivers can be installed from the SAP IQ 15.4 ESD #2.
Status	Recommended for use with MobiLink
Client s/w	None
OS	Windows	7, Server 2003, Server 2008, and Server 2008 R2
	Linux	Redhat Enterprise Linux 5, 6, and 7 SuSE Enterprise 12
Pros	All tests passed
Cons	None
Notes	The SAP IQ 15.4 server binaries must be from SAP IQ 15.4 ESD #1 or up; Only a 64-bit MobiLink server is supported on Windows and Linux for consolidated databases running on a SAP IQ 15.4 server; If an upload contains any data that modifies any sync tables that were defined on the IQ store and if the MobiLink server is running with more than one concurrent database worker threads or the MobiLink server is currently running in a server farm, all the uploads must be serialized, because SAP IQ 15 server allows only a single connection to modify a given table on the IQ store at any given time. This requirement can be achieved, if the begin_upload connection script is written to include or to use the following SQL statement: LOCK TABLE table_name IN WRITE MODE WAIT time_string where table_name is the name of a table that is defined on the IQ store and the time_string gives the maximum time period to lock the table. The table can be as simple as the one defined as: CREATE TABLE coordinate_upload ( c1 INTEGER ) It is not required to have any data in this table. If any of the other MobiLink server transactions is required to modify any IQ tables, all of these transaction must be serialized. The same logic mentioned above can be used. This technique is considered more efficient than having the MobiLink server retry on each transaction automatically and users will get better performance.
Permission requirements	Permission to EXECUTE on SP_IQTRANSACTION - required by MobiLink server to use snapshot isolation for download.

SAP IQ 16.0

Driver	SAP IQ ODBC driver
Version	16.00.00.428 on Windows (x64) and 16.00.0000 on Linux (x64) - Both drivers can be installed from the SAP IQ 16.0 GA release.
Status	Recommended for use with MobiLink
Client s/w	None
OS	Windows	7, Server 2003, Server 2008, and Server 2008 R2
	Linux	Redhat Enterprise Linux 5, 6, and 7 SuSE Enterprise 12
Pros	All tests passed
Cons	None
Notes	Only a 64-bit MobiLink server is supported on Windows and Linux for consolidated databases running on a SAP IQ 16.0 server; Using the Row Level Versioning (RLV) feature introduced in SAP IQ 16.0 will greatly increase the throughput for upload and dramatically improves the upload performance, if there are no BLOB columns and foreign keys used in any of the upload tables, because the RLV enabled tables created on the RLV store would be allowed to be accessed concurrently by multiple connections. However, the RLV feature is limited to tables without BLOB and foreign key columns. If any of the sync tables that will be included in the upload streams contains BLOB and/or foreign key columns, the upload phase must be serialized, because SAP IQ 16.0 server does not allow more than one connection to modify a given table concurrently. This requirement can be achieved, if the begin_upload connection script is written to include or to use the following SQL statement: LOCK TABLE table_name IN WRITE MODE WAIT time_string where table_name is the name of a table that is defined on the IQ store and the time_string gives the maximum time period to lock the table. The table can be as simple as the one defined as: CREATE TABLE coordinate_upload ( c1 INTEGER ) It is not required to have any data in this table. If any of the other MobiLink server transactions is required to modify any IQ tables, all of these transaction must be serialized. The same logic mentioned above can be used. This technique is considered more efficient than having the MobiLink server retry on each transaction automatically and users will get better performance.
Permission requirements	The EXECUTE permission on SP_IQTRANSACTION is required by MobiLink server to use snapshot isolation for download. The MONITOR system privilege is required in order to invoke the locking/blocking detection logic.

Oracle 11g and 12.1

Oracle 11g

Driver	SQL Anywhere 17 - Oracle ODBC Driver
Version	17.00.00
Status	Recommended for use with MobiLink
Client s/w	Oracle 11g client
OS	Windows	7, Server 2008, Server 2008 R2, and Server 2012
	Linux	Redhat Enterprise Linux 5, 6, and 7
	Solaris	10, 11
	AIX	6.1, 7.1
Pros	All tests passed
Cons	None
Notes	Before using this driver, you must install Oracle 11g client. To load this driver, you must set Oracle client libraries in your LD_LIBRARY_PATH (Linux, Solaris) or LIBPATH (AIX). TNS server name on Windows DSN setting and ServerName in Linux and Unix .odbc.ini are Oracle TNS service name defined in $ORACLE_HOME/network/admin/tnsnames.ora. The default setting of "Procedure return results or uses VARRAY parameters" on Windows or ProcResults on Linux and Unix is 'No'. If you are using a stored procedure that returns a REF CURSOR, the REF CURSOR parameter (either OUT or IN OUT) must be defined as the last parameter in the parameter list of the stored procedure.
Permission requirements	Permission to EXECUTE on SYS.DBMS_UTILITY - required by MobiLink to determine if the database is running on an Oracle RAC. Permission to SELECT from SYS.GV_$TRANSACTION - required by MobiLink server to do TIMESTAMP based downloads. Permission to SELECT from SYS.V_$SESSION - required by MobiLink server to determine the SID and SERIAL# values of the current session. Permission to SELECT from DBA_OBJECTS, SYS.GV_$LOCK and SYS.GV_$SESSION - required by MobiLink server locking/blocking detection logic.

Oracle 12.1

Driver	SQL Anywhere 17 - Oracle ODBC Driver
Version	17.00.00
Status	Recommended for use with MobiLink
Client s/w	Oracle 12.1 client, version 12.1.0.1.0 Warning: There is a behavior change in the Oracle OCI library, versions 12.1.0.2.0 andup for stored procedure calls with INOUT parameters. This behavior change can cause data corruption with current versions of MobiLink server. Therefore, in order to avoid data corruption, any Oracle OCI library versions greater than or equal to 12.1.0.2.0 should not be used with the MobiLink server until further notice.
OS	Windows	7, Server 2008, Server 2008 R2, Server 2012, and Server 2012 R2
	Linux	Redhat Enterprise Linux 5, 6, and 7
	Solaris	11
	AIX	7.1
Pros	All tests passed
Cons	None
Notes	Before using this driver, you must install Oracle 12.1 client. To load this driver, you must set Oracle client libraries in your LD_LIBRARY_PATH (Linux, Solaris) or LIBPATH (AIX). TNS server name on Windows DSN setting and ServerName in Linux and Unix .odbc.ini are Oracle TNS service name defined in $ORACLE_HOME/network/admin/tnsnames.ora The default setting of "Procedure return results or uses VARRAY parameters" on Windows or ProcResults on Linux and Unix is 'No'. Result sets can now be returned by stored procedures through the Oracle implicit result set regardless of the setting for the "Procedure return results or uses VARRAY parameters" parameter. If you are using a stored procedure that returns a REF CURSOR, the REF CURSOR parameter (either OUT or IN OUT) must be defined as the last parameter in the parameter list of the stored procedure.
Permission requirements	Permission to EXECUTE on SYS.DBMS_UTILITY - required by MobiLink to determine if the database is running on an Oracle RAC. Permission to SELECT from SYS.GV_$TRANSACTION - required by MobiLink server to do TIMESTAMP based downloads. Permission to SELECT from SYS.V_$SESSION - required by MobiLink server to determine the SID and SERIAL# values of the current session. Permission to SELECT from DBA_OBJECTS, SYS.GV_$LOCK and SYS.GV_$SESSION - required by MobiLink server locking/blocking detection logic.

Microsoft SQL Server 2012 and 2014

Important:

With any version of SQL Server, you should specify "SET NOCOUNT ON" as the first statement in all stored procedures or SQL batches executed via ODBC. Without this option, a "number of rows affected" message is sent to MobiLink for each statement executed. If you are doing a relatively large number of inserts, updates, and select into statements, these messages can fill network buffers resulting in data being lost without any indication that it is being lost!

Microsoft SQL Server 2012

Driver	Microsoft SQL Native Client ODBC Driver
Version	2011.110.xxxx.xx
Status	Recommended for use with MobiLink
Client s/w	None
OS	7, Server 2003, Server 2008, Server 2008 R2, and Server 2012
Pros	All tests passed
Cons	None
Notes	Be sure to put "SET NOCOUNT ON" at the start of all stored procedures and batches that are executed via ODBC.
Permission requirements	Permission to VIEW SERVER STATE. Permission to SELECT from SYS.DATABASES. Permission to SELECT from SYS.DM_TRAN_LOCKS, SYS.PARTITIONS, SYS.SYSPROCESSES.

Microsoft SQL Server 2014

Driver	Microsoft SQL Native Client ODBC Driver
Version	2011.110.xxxx.xx
Status	Recommended for use with MobiLink
Client s/w	None
OS	7, Server 2003, Server 2008, Server 2008 R2, and Server 2012
Pros	All tests passed
Cons	None
Notes	Be sure to put "SET NOCOUNT ON" at the start of all stored procedures and batches that are executed via ODBC. SQL Server allows users to control transaction durability at the database and transaction levels. The durability can be set to be full durability or delayed durability. In order to maintain data consistency, the MobiLink server requires its transactions with full durability. So the database option delayed durability should never be setting to FORCED.
Permission requirements	Permission to VIEW SERVER STATE. Permission to SELECT from SYS.DATABASES. Permission to SELECT from SYS.DM_TRAN_LOCKS, SYS.PARTITIONS, SYS.SYSPROCESSES.

IBM DB2 9.7 and 10.5

Important:

DB2 AS/400 is not supported.
Any DB2 Java stored procedures used in MobiLink synchronization should always immediately set autocommit to OFF, for example by using getConnection().setAutoCommit(false).

IBM DB2 9.7

Driver	IBM DB2 ODBC Driver
Version	9.07.300.291 on Windows (x32 and x64) and 9.07.0003 on Linux (x64) - These drivers can be retrieved from DB2 9.7 FixPack3.
Status	Recommended for use with MobiLink
Client s/w	DB2 UDB Client 9.7
OS	Windows	7, Server 2003, and Server 2008 R2
	Linux	Redhat Enterprise Linux 5, 6, and 7
Pros	All tests passed
Cons	None
Notes	The ODBC driver version must be 9.0.7.xxxx. Older versions of the IBM DB2 ODBC driver should not be use for the MobiLink server to talk to a DB2 9.7 database, because it can cause data inconsistency. If you are using timestamp-based download and if any of the download_cursor and/or download_delete_cursor scripts are implemented in stored procedure calls, either the DB2 consolidated database server must run with the configuration parameter, ConcurrentAccessResolution being set to 2 (Wait for outcome), or executing the following SQL command CALL SET_ROUTINE_OPTS(GET_ROUTINE_OPTS() \|\| 'CONCURRENTACCESSRESOLUTION WAIT FOR OUTCOME' before creating the stored procedures for download_cursor and/or download_delete_cursor scripts is required. Then the DB2 database server will block the download cursors if there are any uncommitted operations that have modified the download cursor results. Without doing so, new data may not be downloaded to the remote databases and data inconsistency may occur. When Oracle compatibility features are enabled, DB2 supports some Oracle data types, such as, DATE, VARCHAR2, and NUMBER. These data types will behave the same as those in an Oracle database. For detailed data type mapping of these compatible data types between DB2 and SQL Anywhere/UltraLite, please see the MobiLink referencechapter in the MobiLink Server Administration manual. On Linux, you need to run 'source db2profile' to export DB2 environment variables. db2profile is in the home directory under your DB2 installation. Two database configuration parameters LOCKLIST and APPLHEAPSZ need to be changed for high load testing. Set LOCKLIST to 500 and APPLHEAPSZ to 1024.
Permission requirements	Permission to SELECT from SYSIBMADM.LOCKWAITS, SNAPSHOT_APPL_INFO - required by the MobiLink server locking/blocking detection logic.

IBM DB2 10.5

Driver	IBM DB2 ODBC Driver
Version	10.05.200.xxx on Windows and 10.05.0000 on Linux
Status	Recommended for use with MobiLink
Client s/w	DB2 UDB Client 10.5
OS	Windows	7, Server 2003, Server 2008 R2, and Server 2012
	Linux	Redhat Enterprise Linux 5, 6, and 7 SuSE Enterprise Linux 12
Pros	All tests passed
Cons	None
Notes	IBM has introduced a column store in its DB2 10.5 release and now supports both column and row stores in 10.5 databases. However, there are a few restrictions for tables created with a column store and one of these restrictions is Queries cannot be requested to be blocked by any uncommitted transactions for tables created with a column store. This restriction would prevent the MobiLink server from providing a timestamp based synchronization for any tables with a column store in order to maintain data consistency. Therefore, any tables involved in synchronization with MobiLink must be created with a row store, if the sync logic requires timestamp based downloads. For sync logic with a snapshot based download, sync tables can be created either with a column store or a row store, but the MobiLink server needs to be started with command line option hwp- (that will inform the MobiLink server to skip requesting the blocking behavior for generating a download for any client), otherwise, the DB2 10.5 database server would complain with the following error: SQL1667N The operation failed because the operation is not supported with the typeof the specified table. Specified table: sync_table_name. Table type: "ORGANIZE BY COLUMN". Operation: "CUR_COMMIT DISABLED". SQLSTATE=42858 when the MobiLink server was trying to generate a download for the client. If you are using timestamp-based download and if any of the download_cursor and/or download_delete_cursor scripts are implemented in stored procedure calls, either the DB2 consolidated database server must run with the configuration parameter, ConcurrentAccessResolution being set to 2 (Wait for outcome), or executing the following SQL command: CALL SET_ROUTINE_OPTS(GET_ROUTINE_OPTS() \|\| 'CONCURRENTACCESSRESOLUTION WAIT FOR OUTCOME' before creating the stored procedures for download_cursor and/or download_delete_cursor scripts is required. Then the DB2 database server will block the download cursors if there are any uncommitted operations that have modified the download cursor results. Without doing so, new data may not be downloaded to the remote databases and data inconsistency may occur. When Oracle compatibility features are enabled, DB2 supports some Oracle data types, such as DATE, VARCHAR2, and NUMBER. These data types will behave the same as those in an Oracle database. For detailed data type mapping of these compatible data types between DB2 and SQL Anywhere/UltraLite, please see the MobiLink referencechapter in the MobiLink Server Administration manual. On Linux, you need to run 'source db2profile' to export DB2 environment variables. db2profile is in the home directory under your DB2 installation. Furthermore, you need to use the 64-bit IBM DB2 ODBC driver, libdb2o.so. Two database configuration parameters LOCKLIST and APPLHEAPSZ need to be changed for high load testing. Set LOCKLIST to 500 and APPLHEAPSZ to 1024.
Permission requirements	Permission to SELECT from SYSIBMADM.MON_LOCKWAITS, SNAPSHOT_APPL_INFO - required by the MobiLink server locking/blocking detection logic.

MySQL 5.5.16 and 5.6.20

MySQL 5.5.16

Driver	MySQL ODBC 5.3 UNICODE driver
Version	5.03.04.00 (Win32 and 64) and 05.03.0004 (Linux x64).
Status	Recommended for use with MobiLink
Client s/w	None
OS	Windows	7, Server 2003, Server 2008, Server 2008 R2, and Server 2012
	Linux	Redhat Enterprise Linux 5, 6, and 7 SuSE Enterprise Linux 12
Pros	All tests passed
Cons	None
Notes	Storage Engine: MySQL offers a set of storage engines in a MySQL server and somestorage engines are ACID compliant and some are not. The MobiLink server requires an ACID compliant storage engine, such as InnoDB, Falcon. Please make sure the default storage engine is ACID compliant. If the default storage engine is not ACID compliant, please make sure all the MobiLink server system tables are created using an ACID compliant storage engine. Stored Procedures: The MySQL ODBC driver does not support inout or out parameters forstored procedure calls. Therefore, all procedures that need inout parameters must be written as functions that can return an out value. The MobiLink server events that require inout parameters, such asauthenticate_user, handle_error, modify_user must be implemented as functions and run using a select statement, like SELECT function_name( ?, ?, ?, ... ) and not { CALL function_name( ?, ?, ?, ... ) } Then the MobiLink server will catch the return value properly. If the MobiLink server scripts use named parameters, the parameterswill not be changed after execution of the script. User-defined named parameters, e.g. {ml u.my_var} are thus not supported. Cursor Scripts: The upload_fetch, download_cursor, or download_delete_cursor event maybe written as a select statement and the MobiLink server uses the read-committed isolation level to execute the select statement. However, with the read-committed isolation, the MySQL ODBC driver may allow the MobiLink server to read uncommitted operations (inserts, updates and deletes). Then with this behavior, synchronization data would not be consistent between the consolidated and remote databases. This problem has been reported to MySQL. To work around this problem, all the select statements for the upload_fetch,download_cursor, and download_delete_cursor events must contain a "lock in share mode" clause. For instance, a download_cursor script should be written as: SELECT col1, col2, ..., coln FROM a_sync_table WHERE last_modified > ? ... LOCK IN SHARE MODE if it is a select statement. With the "lock in share mode" clause, the select statement will be blocked by any uncommitted operations made by the other connections on the same table and then upload updates and download data will be consistent in the consolidated and remote databases. Linux Platforms: There are two ways to specify an ODBC configuration file on Linux a) Place the file ODBC.INI (the file name must be in upper case) or symbolic link, ODBC.INI in the home directory of the current user; b) Create an environment variable, ODBCINI and setup this environment variable by pointing it to the real ODBC configuration file. The MySQL ODBC 5.3 UNICODE driver The MySQL 5.3 Unicode ODBC driver does not contain any ANSI functions, if its wide function exists, but the SQLA ODBC driver manager on Linux requires both sets of the ODBC APIs. To work around this problem, a new DSN property named OnlyWideEntries is introduced on Linux and this property can be set to Yes or No, and the default setting is No. OnlyWideEntries must be set to Yes on Linux, if the MySQL ODBC driver is used. Sample DSN for MySQL on UNIX A sample DSN for MySQL on UNIX can be: [a_mysql_dsn] Driver=full_path/libmyodbc5.so server=host_name uid=user_name pwd=user_password database=database_name OnlyWideEntries=Yes

MySQL 5.6.20

Driver	MySQL ODBC 5.3 UNICODE driver
Version	5.03.04.00 (Win32 and 64) and 05.03.0004 (Linux x64).
Status	Recommended for use with MobiLink
Client s/w	None
OS	Windows	7, Server 2003, Server 2008, and Server 2008 R2
	Linux	Redhat Enterprise Linux 5, 6, and 7 SuSE Enterprise Linux 12
Pros	All tests passed
Cons	None
Notes	Storage Engine: MySQL offers a set of storage engines in a MySQL server and somestorage engines are ACID compliant and some are not. The MobiLink server requires an ACID compliant storage engine, such as InnoDB and Falcon. Please make sure the default storage engine is ACID compliant. If the default storage engine is not ACID compliant, please make sure all the MobiLink server system tables are created using an ACID compliant storage engine. Stored Procedures: MySQL now supports INOUT parameters in stored procedures. Therefore, output parameters for synchronization scripts that are written in stored procedure calls can be retrieved through INOUT parameters or returned by a result set. Fractional Part of Second: MySQL 5.6.20 server supports a fractional part of a second. The number of digits in the fractional part can be a value between 0 and 6. The MySQL server will round the fractional second into its nearest integer that can be stored into the column properly. For instance, if a timestamp column was defined as timestamp(3), the server will round 4.1234 seconds to 4.123 seconds, and 4.1235 seconds to 4.124 before storing the value into the table. In order to keep data consistency for a timestamp based download, the MobiLink server will automatically subtract one second from the next_last_download_timestamp generated in the prepare_for_download transaction before sending it to the client, if there is no user-defined generate_next_last_download_timestamp connection script. Cursor Scripts: The upload_fetch, download_cursor, or download_delete_cursor event may be written as a select statement and the MobiLink server uses the read-committed isolation level to execute the select statement. However, with the read-committed isolation, the MySQL ODBC driver may allow the MobiLink server to read uncommitted operations (inserts, updates and deletes). With this behavior, synchronization data would not be consistent between the consolidated and remote databases. This problem has been reported to MySQL. To work around this problem, all the select statements for the upload_fetch, download_cursor, and download_delete_cursor events must contain a "lock in share mode" clause. For instance, a download_cursor script should be written as: SELECT col1, col2, ..., coln FROM a_sync_table WHERE last_modified > ? ... LOCK IN SHARE MODE if it is a select statement. With the "lock in share mode" clause, the select statement will be blocked by any uncommitted operations made by the other connections on the same table and then upload updates and download data will be consistent in the consolidated and remote databases. Linux Platforms: There are two ways to specify an ODBC configuration file on Linux a) Place the file ODBC.INI (the file name must be in upper case) or symbolic link, ODBC.INI in the home directory of the current user; b) Create an environment variable, ODBCINI and set this environment variable by pointing it to the real ODBC configuration file. The MySQL ODBC 5.3 UNICODE driver The MySQL 5.3 Unicode ODBC driver does not contain any ANSI functions, if its wide function exists, but the SQLA ODBC driver manager on Linux requires both sets of the ODBC APIs. To work around this problem, a new DSN property named OnlyWideEntries is introduced on Linux and this property can be set to Yes or No, and the default setting is No. OnlyWideEntries must be set to Yes on Linux, if the MySQL ODBC driver is used. Sample DSN for MySQL on UNIX A sample DSN for MySQL on UNIX can be: [a_mysql_dsn] Driver=full_path/libmyodbc5.so server=host_name uid=user_name pwd=user_password database=database_name OnlyWideEntries=Yes

↧

ODBC Driver for SQL Anywhere 11 very slow

September 23, 2015, 5:16 am

Latest and popular articles on SAP ERP

≫ Next: How to Connect to Sql Anywhere 12 Remotely

≪ Previous: Recommended ODBC Drivers for 17.0.0 MobiLink

Hi,

we are using SQL Anywhere 11.

If we connect via ODBC to the database than the process of communication Need very much time.

Very easy SQL-Query's need more than 15 seconds to deliver results.

By using the native protocoll instead of ODBC, the results are delivered in less than 3 seconds.

Does ODBC-Driver have a bug?

Best regards,

Kevin

↧

How to Connect to Sql Anywhere 12 Remotely

September 23, 2015, 10:32 am

Latest and popular articles on SAP ERP

≫ Next: SQL Anywhere 17 - In Memory Database Validation

≪ Previous: ODBC Driver for SQL Anywhere 11 very slow

I'm pretty new to Database Management/Networking and I've been tasked with remotely hooking into a Sql Anywhere 12 database so that my app can interact with another app's data.

The DBA of the other app has opened a public port for me and has given me the IP and port to connect to. I am working on a Mac and have tried to install the ODBC driver for Sql Anywhere. I really have no idea what I'm doing and hoped that someone here could help me to get this setup.

My questions basically revolve around, at an abstract level, how does connecting to this database over a port work? Do I need to setup an ODBC client on my local machine that talks to the database via the open port? If so, how do I do that on a mac.

Second, my app is built on Node.js and I see that there is a module for working with databases over ODBC https://github.com/wankdanker/node-odbc If this is available, do I still need to set up a Sybase Sql Anywhere client on my local machine? Or does this node module replace it?

As you can tell, I'm very lost. I'm totally on the application development side of things and don't do much with hooking into databases, etc... Any help you can provide would be much appreciated!

Message was edited by: Nick Elson

↧

SQL Anywhere 17 - In Memory Database Validation

September 24, 2015, 9:09 pm

Latest and popular articles on SAP ERP

≫ Next: Limit rows send to consolidate db from remote db with mobilink

≪ Previous: How to Connect to Sql Anywhere 12 Remotely

As part of the backup and recovery plan, along with periodically testing the recovery process, it is considered a best practice to validate the backup database after a successful backup. This is the best way to ensure that your production database is valid, and that the backup is clean and will actually be recoverable should you need it.

Unfortunately, starting a backup database on a server would cause (at a minimum) a checkpoint to occur, advancing the expected starting offset for the log file associated with the backup database. This meant that should you ever have to use that backup database for recovery, you would not be able to apply any log files from your production database to it because expected log offsets would no longer match.

In order to ensure that the backup is valid, and that it can still be used for recovery, you have to start the backup database in “read-only” mode (using the server –r option or the FOR READ ONLY clause of the START DATABASE statement) to ensure no changes are made to the database/log. This works well in most, but not all cases. If your backup was started and there were open transactions in the database (which is common), the backup database has to go through recovery when it starts (to either complete or rollback those transactions and ensure an ACID compliant database), which means you cannot use read-only mode for validation.

In these cases, you have to make a copy of the backup database, start it up and let the database recover, and then do the validation. Obviously this adds a lot of overhead to the backup plan, in both time and disk space.

For version 17, we have addressed this by adding a new in-memory mode called "in-memory validation" or IMV, which is intended to allow backups to be validated without making a separate copy of the database and log files. Unlike the other in-memory modes for SQL Anywhere (in-memory checkpoint-only mode (-im c) and in-memory never-write mode (-im nw )), which are separately licensed, In-memory validation mode is included with all versions of SQL Anywhere: it is not a separately licensed component.

In-memory validation mode is enabled by specifying the "-im validation" switch (or "-im v" for short) on the server command line:

dbsrv17.exe –im v foo.db

The server in-memory validation mode has the following behaviours:

Database files and log files are never modified on disk
All modifications are maintained in the database server's cache and therefore the server may run out of cache (ie. memory) if the checkpoint log, redo log and/or undo logs modify a large enough number of database pages.
The server will create & use a temp file to alleviate cache pressure where it can.
In-memory modifications (DML, DDL, etc) can only be made by the recovery tasks (ie. for applying the checkpoint log, redo log(s) and undo log(s)).
All non-recovery operations such as those from client connections, user-defined events, etc are read-only (similar to the server read only (-r) mode).
Databases will not be shut down after recovery when a flag such as -a, -ad, or -f is specified.
The server will ignore the "-r" (read-only) command line option(s) and ignore the FOR READ ONLY clause on START DATABASE statements.
A backup of a database running on a server in IMV mode will generate a backup identical to the original, unmodified database file that was started on the IMV server.

Updates to DBValid/DBValidate()

In addition to the behaviour changes in the server, the dbvalid command line tool now supports a new "-im <mode>" switch to allow control over the in-memory mode of the server but only for servers that are autostarted. Valid modes include: none, v, c, nw. The default mode is v.

When a mode other than 'none' is used (including the default 'v' mode), dbvalid appends the "-im <mode>" switch the StartLine connection parameter, if provided. Otherwise, StartLine is set to "dbeng16 -im <mode>". If StartLine already contains a "-im <mode>" command line switch, the server will respect the first one (ie, the one from the connection string, not the one appended by dbvalid). When –im 'none' is specified, StartLine is neither set nor modified.

The dbtools library DBValidate(…) method has also been updated to support the new in memory mode option.

↧

Limit rows send to consolidate db from remote db with mobilink

September 25, 2015, 10:21 am

Latest and popular articles on SAP ERP

≫ Next: SQL FOR CRYSTAL REPORTS

≪ Previous: SQL Anywhere 17 - In Memory Database Validation

I need to limit the rows that send the remote database to the consolidate database with mobilink 16.

I have a case that only need to send the rows for a table that only exists in another table to the consolidate database.

Also after the syncronization need to delete those rows in the remote database.

My consolidate DB and Remote DB is ASA 16. I use for the syncronization mobilink 16.

Anyone have an idea how to resolve this case?

Thanks for any help.

↧

SQL FOR CRYSTAL REPORTS

September 25, 2015, 7:04 am

Latest and popular articles on SAP ERP

≫ Next: SQL Anywhere 16: TLS handshake failed, error code 20

≪ Previous: Limit rows send to consolidate db from remote db with mobilink

This the the SQL Query for which I keep receive the error qty completed is ambigious. I only want the report to pull the information from jobs that are still not completed.

SELECT "job_hdr"."order-no", "job_hdr"."name", "job_routing"."oper-no", "job_routing"."work-ctr", "job_routing"."start-date", "job_routing"."end-date", "job_routing"."QtyToMfg", "job_routing"."QtyCompleted", "job_hdr"."req-date"

FROM "E100LIVE"."PUB"."job-routing" "job_routing" INNER JOIN "E100LIVE"."PUB"."job-hdr" "job_hdr" ON ("job_routing"."company"="job_hdr"."company") AND ("job_routing"."order-no"="job_hdr"."order-no")

WHERE "qtycompleted"= "0.00"

ORDER BY "job_hdr"."name"

↧

SQL Anywhere 16: TLS handshake failed, error code 20

September 25, 2015, 3:03 pm

Latest and popular articles on SAP ERP

≫ Next: Where can I download the jconn4.jar for SQLA 16

≪ Previous: SQL FOR CRYSTAL REPORTS

I'm testing TLS connections on SQL Anywhere 16.0.0.2158 and am getting a TLS handshake failed, error code 20 error message. I've read the following documents with no help:

http://dcx.sap.com/index.html#sa160/en/dbadmin/tls-j22-s-5729723.html

and

http://dcx.sap.com/index.html#sa160/en/dbadmin/gencert-ml-ref1.html

and

http://dcx.sap.com/index.html#sa160/en/dbadmin/ml-tls-s-6232604.html

here is the client log

Fri Sep 25 2015 14:52:03

14:52:03 Attempting to connect using:

UID=ficsro;PWD=********;DBN=fics;ServerName=billytest;CON=SQL_DBC_4c382e5200;ENC='TLS(tls_type=rsa;fips=n;trusted_certificate=C:\ssl\public.pem)';LOG=c:\ssl\ssl.log;LINKS='tcpip(HOST=web1)';CPOOL=NO

14:52:03 Attempting to connect to a running server...

14:52:03 Attempting TCPIP connection (address 192.168.4.112:2638 found in sasrv.ini cache)

14:52:03 Looking for server with name billytest

14:52:03 Trying to find server at cached address 192.168.4.112:2638 without broadcasting

14:52:03 Found database server billytest on TCPIP link

14:52:03 Connected using client address 192.168.5.150:52913

14:52:03 Connected to server over TCPIP

14:52:03 Connected to SQL Anywhere Server version 16.0.0.2158

14:52:03 Application information:

14:52:03 IP=192.168.5.150;HOST=staging11;OSUSER=estatuswebsvc;OS='Windows 2012R2 Build 9200 ';EXE=C:\ColdFusion11\estatuswebsvc\bin\coldfusion.exe;PID=0xab4;THREAD=0xaec;VERSION=16.0.0.2158;API=iAnywhereJDBC;TIMEZONEADJUSTMENT=-300

14:52:03 Connected to the server, attempting to connect to a running database...

14:52:03 The TLS handshake failed, error code 20

14:52:03 Communication function SQLPresSyncPoint code 8

14:52:03 unknown error 0

14:52:03 Client disconnected

14:52:03 Disconnected from server

here are the server startup options which startup just fine:

-c 128M

-ec none,simple,TLS(identity=c:\db\identity.pem;identity_password=fics)

-n billytest

-x tcpip

c:\db\fics.db

here is the test certificate info:

C:\Program Files\SQL Anywhere 16\Bin64>createcert -t rsa

SQL Anywhere X.509 Certificate Generator Version 16.0.0.2158

Warning: The certificate will not be compatible with older versions

of the software including version 12.0.1 prior to build 3994 and version 16.0

prior to build 1691. Use the -3des switch if you require compatibility.

Enter RSA key length (512-16384): 2048

Generating key pair...

Country Code: US

State/Province: TX

Locality: ADDISON

Organization: FICS,INC

Organizational Unit: FICS

Common Name: web1

Enter file path of signer's certificate:

Certificate will be a self-signed root

Serial number [generate GUID]:

Generated serial number: f3dde00072d04f319b17cd429769b75e

Certificate valid for how many years (1-100): 99

Certificate Authority (Y/N) [N]:

1. Digital Signature

2. Nonrepudiation

3. Key Encipherment

4. Data Encipherment

5. Key Agreement

6. Certificate Signing

7. CRL Signing

8. Encipher Only

9. Decipher Only

Key Usage [1,3,4,5]: 3,4,5

Enter file path to save certificate: c:\db\public.pem

Enter file path to save private key: c:\db\private.pem

Enter password to protect private key: fics

Enter file path to save identity: c:\db\identity.pem

↧

Where can I download the jconn4.jar for SQLA 16

November 17, 2014, 4:45 am

Latest and popular articles on SAP ERP

≫ Next: Download Link for SQL Anywhere 17

≪ Previous: SQL Anywhere 16: TLS handshake failed, error code 20

Hello.

From the SQLA 16 Documentations:

The jConnect JDBC driver

The jConnect driver is available as a separate download at [external link] http://www.sybase.com/products/allproductsa-z/softwaredeveloperkit/jconnect. Documentation for jConnect can also be found on the same page.

To use JDBC from an applet, you must use the jConnect JDBC driver to connect to SQL Anywhere databases.

Is there an updated Link available ?

Kind regards

Thomas

↧

Download Link for SQL Anywhere 17

September 30, 2015, 1:07 am

Latest and popular articles on SAP ERP

≫ Next: SAP SQL Anywhere Supported Platforms and Engineering Support Status

≪ Previous: Where can I download the jconn4.jar for SQLA 16

Hello Team,

Can anyone provide download link for SQL Anywhere 17?

Thanks in advance...

↧

SAP SQL Anywhere Supported Platforms and Engineering Support Status

February 1, 2013, 7:59 am

Latest and popular articles on SAP ERP

≫ Next: SAP SQL Anywhere 12 - Support Packs

≪ Previous: Download Link for SQL Anywhere 17

The tables below summarize the platforms supported by SAP SQL Anywhere. The following information is available:

SQL Anywhere for PC Platforms

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
Windows 7	x86 and x64
Windows 8.x	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2003 R2 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2	x64

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #1691 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2 EBF #1691 or higher required	x64
Windows CE/Mobile Version	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #3797 or higher required for Windows 8 EBF #3994 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #3797 or higher required	x64
Windows Server 2012 R2 EBF #3994 or higher required	x64
Windows CE/Mobile Version	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows CE/Mobile Version	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Windows Version	Chipset
2000 (see Operating Systems Note #2)	x86
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7 Tested with EBF #2324	x86 and x64
Windows 8 EBF #2878 or higher required	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2 Tested with EBF #2324	x64
Windows Server 2012 EBF #2878 or higher required	x64
Windows CE/Mobile Version	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x EBF #2376 or higher required	ARMv4i

SQL Anywhere for Linux, Unix and OS X Platforms

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset 64-bit server + 32-bit and 64-bit client support
10 Java graphical administrative tools supported for SPARC, but not x64	SPARC and x64
11	SPARC and x64
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
11i v2	IA64 on Itanium 2
11i v3	IA64 on Itanium 2
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
6.1	POWER
7.1	POWER
OS X Version	Chipset
10.9	x64
10.10	x64

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86, x64 and ARM
Solaris Version	Chipset 64-bit server + 32-bit and 64-bit client support
10 Java graphical administrative tools supported for SPARC, but not for x64	SPARC and x64
11	SPARC and x64
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
11i v2	IA64 on Itanium 2
11i v3	IA64 on Itanium 2
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
6.1	POWER
7.1	POWER
OS X Version	Chipset
10.8	x64

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version Click here for list of required Solaris patches	Chipset 64-bit server + 32-bit and 64-bit client support
9	SPARC
10 Java graphical administrative tools supported for SPARC, but not for x64	SPARC and x64
11 Solaris SPARC tested with EBF #3574 and requires JRE 6 Update 31 (JRE 1.6.0_31) available here. Instructions on updating the SQL Anywhere JRE are available here: http://scn.sap.com/docs/DOC-41203. Solaris x64 tested with EBF #3523	SPARC and x64
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
11i v2	IA64 on Itanium 2
11i v3	IA64 on Itanium 2
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
5.3	POWER
6.1	POWER
7.1 EBF #3469 or higher required	POWER
OS X Version	Chipset
10.5	x64
10.6	x64
10.7 EBF #3577 or higher required	x64

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version Click here for list of required Solaris patches	Chipset 64-bit server + 32-bit and 64-bit client support
9	SPARC
10 Java graphical administrative tools supported for SPARC, but not for x64	SPARC and x64
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
11i v2	IA64 on Itanium 2
11i v3	IA64 on Itanium 2
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
5.3	POWER
6.1	POWER
OS X Version	Chipset
10.5	x64
10.6	x64

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version Click here for list of required Solaris patches	Chipset 64-bit server + 32-bit and 64-bit client support
8	SPARC
9	SPARC
10 Java graphical administrative tools supported for SPARC, but not for x64	SPARC and x64
11 Tested with EBF #2753	SPARC and x64
HP-UX Version	Chipset 64-bit server + 32-bit and 64-bit client support
11i v2	IA64 on Itanium 2
11i v3	IA64 on Itanium 2
AIX Version	Chipset 64-bit server + 32-bit and 64-bit client support
5.3 TL07 or higher	POWER
6.1	POWER
7.1 EBF #2637 or higher required	POWER
OS X Version	Chipset
10.5	x64
10.6 EBF #2449 or higher required	x64

MobiLink Synchronization for PC Platforms

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
Windows 7	x86 and x64
Windows 8.x	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2003 R2 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2	x64

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #1691 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2 EBF #1691 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #3797 or higher required for Windows 8 EBF #3994 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #3797 or higher required	x64
Windows Server 2012 R2 EBF #3994 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x	ARMv4i

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Windows Version	Chipset
2000 (see Operating Systems Note #2)	x86
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7 Tested with EBF #2324	x86 and x64
Windows 8 EBF #2878 or higher required	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2 Tested with EBF #2324	x64
Windows Server 2012 EBF #2878 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile for Pocket PC and Smartphone	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard	ARMv4i
Windows CE 5.x and 6.x EBF #2376 or higher required	ARMv4i

MobiLink Synchronization for Linux, Unix and OS X Platforms

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset
10	SPARC
11	SPARC
AIX Version	Chipset
6.1	POWER
7.1	POWER
OS X Version	Chipset
10.9	x64
10.10	x64

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64 ARM (MobiLink Client only)
Solaris Version	Chipset
10	SPARC
11	SPARC
AIX Version	Chipset
6.1	POWER
7.1	POWER
OS X Version	Chipset
10.8	x64

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset
9	SPARC
10	SPARC
11 Solaris SPARC tested with EBF #3574 and requires JRE 6 Update 31 (JRE 1.6.0_31) available here. Instructions on updating the SQL Anywhere JRE are available here: http://scn.sap.com/docs/DOC-41203.	SPARC
AIX Version	Chipset
5.3	POWER
6.1	POWER
7.1 EBF #3469 or higher required	POWER
OS X Version	Chipset
10.5	x64
10.6	x64
10.7 EBF #3577 or higher required	x64

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset
9	SPARC
10	SPARC
AIX Version	Chipset
5.3	POWER
6.1	POWER
OS X Version	Chipset
10.5	x64
10.6	x64

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Linux Version	Chipset
Click here for complete details	x86 and x64
Solaris Version	Chipset
8	SPARC
9	SPARC
10	SPARC
11 Tested with EBF #2753	SPARC
AIX Version	Chipset
5.3	POWER
6.1	POWER
7.1 EBF #2637 or higher required	POWER
OS X Version	Chipset
10.5	x64
10.6 EBF #2449 or higher required	x64

QAnywhere Client for PC Platforms

SQL Anywhere 16.0 and higher does not include QAnywhere.

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #3797 or higher required for Windows 8 EBF #3994 or higher required for Windows 8.1	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #3797 or higher required	x64
Windows Server 2012 R2 EBF #3994 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Windows Version	Chipset
2000 (see Operating Systems Note #2)	x86
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7 Tested with EBF #2324	x86 and x64
Windows 8 EBF #2878 or higher required	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2 Tested with EBF #2324	x64
Windows Server 2012 EBF #2878 or higher required	x64
Windows CE/Mobile Version * MobiLink client only *	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i

UltraLite

SQL Anywhere 17.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
Windows 7	x86 and x64
Windows 8.x	x86 and x64
Windows 10	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2	x64
Windows CE/Mobile/Phone Version	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Windows Phone 8.1	ARM x86 for emulator only
Android Version	Chipset
4.1 or later	ARM v7 x86, x86_64
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
Current version
Linux Version	Chipset
Click here for details.	x64
OS X Version	Chipset
10.9+	x86_64

SQL Anywhere 16.0	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8.x EBF #1691 or higher required for Windows 8.1	x86 and x64
Windows 10	x86 and x64
Windows RT EBF #1716 or higher required	ARMv7, x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012	x64
Windows Server 2012 R2 EBF #1691 or higher required	x64
Windows CE/Mobile/Phone Version	Chipset
Pocket PC 2003 Encrypted MobiLink communications (RSA, FIPS) and M-Business Anywhere are not supported	ARM
Windows CE 4.x	ARM
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Windows Phone 8 EBF #1716 or higher required	ARM x86 for emulator only
Android Version	Chipset
2.2 or later	ARM v7
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
5 +	ARMv7s, ARM64, i386, x86_64
BlackBerry Version	Chipset
4.1 and later, but not BlackBerry 10	ARM
J2SE Version	Chipset
1.7	n/a
Linux Version	Chipset
Click here for details.	x64
OS X Version	Chipset
10.8 +	x64

SQL Anywhere 12.0.1	Status (see end of document for definition)
Click here for more details	Active
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8 EBF #3797 or higher required	x86 and x64
Windows 10	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #3797 or higher required	x64
Windows Server 2012 R2 EBF #3994 or higher required
Windows CE/Mobile Version	Chipset
Pocket PC 2003 EBF #3484 or higher required FIPS certification is not supported	ARM
Windows CE 4.x EBF #3484 or higher required	ARM
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Android Version	Chipset
1.5 or later	ARM
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
5+	ARMv7s, ARM64, i386, x86_64
BlackBerry Version	Chipset
4.1 or later	ARM
J2SE Version	Chipset
1.5	n/a
Linux Version	Chipset
Click here for details.	x86
OS X Version	Chipset
10.8 +	x64

SQL Anywhere 12.0.0	Status (see end of document for definition)
	Limited
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows CE/Mobile Version	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Android Version	Chipset
Not supported	n/a
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
3 or later	ARMv6, ARMv7 i386
BlackBerry Version	Chipset
4.1 or later	ARM
J2SE Version	Chipset
1.5	n/a
Linux Version	Chipset
Kernels 2.6.10_mvl401-pc_target and 2.6.13	x86

SQL Anywhere 11.0.1	Status (see end of document for definition)
	Archived
Windows Version	Chipset
XP, XP Embedded, XP Tablet PC Edition (see Operating Systems Note #1)	x86 and x64
Vista	x86 and x64
Windows 7	x86 and x64
Windows 8 EBF #2878 or higher required	x86 and x64
Windows Server 2003 (see Operating Systems Note #3)	x86 and x64
Windows Server 2008	x86 and x64
Windows Server 2008 R2	x64
Windows Server 2012 EBF #2878 or higher required	x64
Windows CE/Mobile Version	Chipset
Windows Mobile 5 for Pocket PC and Smartphone (Windows CE 5.0)	ARMv4i
Windows Mobile 6.x Classic, Professional and Standard (Windows CE 5.x)	ARMv4i
Windows CE 6.0	ARMv4i
Android Version	Chipset
1.5 or later	ARM
iOS Version Support includes iPhone, iPad and iPod Touch	Chipset
Not supported	n/a
BlackBerry Version	Chipset
4.1 or later	ARM
J2SE Version	Chipset
1.5	n/a
Linux Version	Chipset
Kernels 2.6.10_mvl401-pc_target and 2.6.13	x86
Palm OS Version	Chipset
4.1 or 5.0	68K

Engineering Support Status for SAP SQL Anywhere

Product	Version	Status (see table below for definition)
SQL Anywhere	17.0	Active
SQL Anywhere	16.0	Active
SQL Anywhere	12.0.1	Active
SQL Anywhere	12.0.0	Limited
SQL Anywhere	5.x, 6.x, 7.x, 8.x, 9.x, 10.x, 11.x	Archived
Watcom SQL	All	Archived

The following table describes the active, limited, and archived status in the above tables.

Active	Most bugs are fixed EBFs (Express Bug Fixes) are issued regularly
Limited	Only serious bugs are fixed EBFs are issued only for serious bugs
Archived	No bugs are fixed No EBFs are issued

Mainstream Maintenance

The following table lists the dates when SQL Anywhere versions will reach the end of mainstream maintenance.

SQL Anywhere Version	End of Mainstream Maintenance
17.x	August 30, 2022
16.x	December 31, 2018
12.x	December 31, 2016
11.x	May 31, 2014
10.x	January 25, 2012
9.x	January 31, 2010

Operating Systems Notes

1 Windows XP support ended April 8, 2014 as documented by Microsoft here: http://www.microsoft.com/en-us/windows/enterprise/end-of-support.aspx.

2 Windows 2000 support ended July 13, 2010 as documented by Microsoft here: https://support.microsoft.com/en-ca/lifecycle?C2=1131.

3 Windows Server 2003 and Windows Server 2003 R2 support ended July 14, 2015 as documented by Microsoft here: https://technet.microsoft.com/library/cc706993.

↧

SAP SQL Anywhere 12 - Support Packs

May 29, 2015, 1:04 am

Latest and popular articles on SAP ERP

≫ Next: Returning a column data-type for just one column in table

≪ Previous: SAP SQL Anywhere Supported Platforms and Engineering Support Status

Hello,

An old sybase customer has SQL anywhere 12 developer edition is looking for Support Packs however he does not have access to the SAP Support Portal as he does not have a maintenance contract with SAP.

He would like to know if there is a place other than the Support Portal where he can download the latest support pack for SQL anywhere 12, more especially version 12.0.1 built 4216.

Could you help?

Regards,

Lyzlinn

↧

Returning a column data-type for just one column in table

October 1, 2015, 7:49 am

Latest and popular articles on SAP ERP

≫ Next: mobilink 16 error ODBC: [Sybase][ODBC Driver]Syntax error or access violation (ODBC State = 42000, Native error code = 0)

≪ Previous: SAP SQL Anywhere 12 - Support Packs

I know there is a way of returning all the metadata for a table including all the column types, but we have a slightly oddball situation where for one table depending upon the DB one column could either be a varchar or integer, therefore we need to validate a data-entry form to ensure strings are not entered where the data-type is integer

Is there any way, via SQL, to check the data-type just for a particular column?

Thanks

↧

mobilink 16 error ODBC: [Sybase][ODBC Driver]Syntax error or access violation (ODBC State = 42000, Native error code = 0)

October 1, 2015, 4:16 pm

Latest and popular articles on SAP ERP

≫ Next: -1117 Mobilink Error

≪ Previous: Returning a column data-type for just one column in table

I use the scripted sync in mobilink 16.0 .. my consolidate and remote databases is ASA 16.0 also

But when i try to sincronize with one table i have thos error

-10002] Consolidated database server or ODBC error: ODBC: [Sybase][ODBC Driver]Syntax error or access violation (ODBC State = 42000, Native error code = 0)
[-10058] Unable to open upload_insert

Already review the table schema in the store procedures and scripts of mobilink and dont have any error. If i run the store procedure run fine without errors.

Anyone have experience with this kind of error?

Also in the publications have anothers tables that dont have any error when sinc with dbmlsync.

this is he scripts in the:

Create Procedure tbl_LogTarjeta_inserted ()

result (
Cod_tienda varchar (10),
ID_Caja varchar (15),
transaccion integer,
Cod_Autorizador integer ,
fechaTransaccion timestamp ,
Tipo varchar (15),
trackEnvio long varchar ,
fechaRespuesta timestamp ,
trackRespuesta long varchar
)
begin
select
Cod_tienda,
ID_Caja,
transaccion,
Cod_Autorizador,
fechaTransaccion,
Tipo,
trackEnvio,
fechaRespuesta,
trackRespuesta
from tbl_LogTarjeta a
where exists (select 1 from Tbl_TrxTrasladable b where a.ID_Caja = b.ID_Caja and a.Transaccion = b.Transaccion )
end

table tbl_LogTarjeta

(

Cod_tienda,
ID_Caja,
transaccion,
Cod_Autorizador,
fechaTransaccion,
Tipo,
trackEnvio,
fechaRespuesta,
trackRespuesta

)

using (

procedure tbl_LogTarjeta_inserted for upload insert )

CALL ml_add_table_script ( 'default','tbl_LogTarjeta','upload_insert',
'INSERT INTO tbl_LogTarjeta (Cod_tienda,ID_Caja,transaccion,Cod_Autorizador,fechaTransaccion,Tipo,trackEnvio,fechaRespuesta,trackRespuesta)
Values ( { ml r.Cod_tienda}, { ml r.ID_Caja}, { ml r.transaccion}, { ml r.Cod_Autorizador}, { ml r.fechaTransaccion},{ ml r.Tipo},{ ml r.fechaRespuesta})' )

The message that is in the ml server is:
I. 2015-10-01 16:45:44. <13> PHASE: send_download: 0
I. 2015-10-01 16:45:44. <13> PHASE: wait_for_download_ack: 0
I. 2015-10-01 16:45:44. <13> PHASE: get_db_worker_for_download_ack: 0
I. 2015-10-01 16:45:44. <13> PHASE: connect_for_download_ack: 0
I. 2015-10-01 16:45:44. <13> PHASE: nonblocking_download_ack: 0
I. 2015-10-01 16:47:03. <14> Request from "Dbmlsync 16.0.2158" for: remote ID: bd6dee9f-9eff-474a-978a-6cbd5ec94ea0, user name: dba, version: default
I. 2015-10-01 16:47:03. <14> Synchronization connection with connection ID 'SPID 17' has been established
I. 2015-10-01 16:47:03. <14> ODBC isolation set to: Read Committed
I. 2015-10-01 16:47:03. <14> COMMIT Transaction: Begin connection
I. 2015-10-01 16:47:03. <14> The current synchronization is using a connection with connection ID 'SPID 17'
I. 2015-10-01 16:47:03. <14> COMMIT Transaction: Begin synchronization
E. 2015-10-01 16:47:03. <14> [-10002] Consolidated database server or ODBC error: ODBC: [Sybase][ODBC Driver]Syntax error or access violation (ODBC State = 42000, Native error code = 0)
E. 2015-10-01 16:47:03. <14> [-10058] Unable to open upload_insert
I. 2015-10-01 16:47:03. <14> Error Context:
I. 2015-10-01 16:47:03. <14> Remote ID: bd6dee9f-9eff-474a-978a-6cbd5ec94ea0
I. 2015-10-01 16:47:03. <14> User Name: dba
I. 2015-10-01 16:47:03. <14> Modified User Name: dba
I. 2015-10-01 16:47:03. <14> Transaction: Upload
I. 2015-10-01 16:47:03. <14> Table Name: tbl_LogTarjeta
I. 2015-10-01 16:47:03. <14> Script Version: default
I. 2015-10-01 16:47:03. <14> Script: INSERT INTO tbl_LogTarjeta (Cod_tienda,ID_Caja,transaccion,Cod_Autorizador,fechaTransaccion,Tipo,trackEnvio,fechaRespuesta,trackRespuesta)
Values ( { ml r.Cod_tienda}, { ml r.ID_Caja}, { ml r.transaccion}, { ml r.Cod_Autorizador}, { ml r.fechaTransaccion},{ ml r.Tipo},{ ml r.fechaRespuesta})
I. 2015-10-01 16:47:03. <14> End of Error Context
I. 2015-10-01 16:47:03. <14> ROLLBACK Transaction: Upload
I. 2015-10-01 16:47:03. <14> COMMIT Transaction: End synchronization
I. 2015-10-01 16:47:03. <14> COMMIT Transaction: End connection
I. 2015-10-01 16:47:03. <14> Synchronization connection with connection ID 'SPID 17' has been disconnected
I. 2015-10-01 16:47:03. <14> Synchronization failed
I. 2015-10-01 16:47:03. <14> PHASE: sync_request: 688
I. 2015-10-01 16:47:03. <14> PHASE: receive_upload: 15
I. 2015-10-01 16:47:03. <14> PHASE: get_db_worker: 0
I. 2015-10-01 16:47:03. <14> PHASE: connect: 16
I. 2015-10-01 16:47:03. <14> PHASE: authenticate_user: 0
I. 2015-10-01 16:47:03. <14> PHASE: begin_sync: 0
I. 2015-10-01 16:47:03. <14> PHASE: apply_upload: 31
I. 2015-10-01 16:47:03. <14> PHASE: prepare_for_download: 0
I. 2015-10-01 16:47:03. <14> PHASE: fetch_download: 0
I. 2015-10-01 16:47:03. <14> PHASE: end_sync: 110
I. 2015-10-01 16:47:03. <14> PHASE: send_download: 0
I. 2015-10-01 16:47:03. <14> PHASE: wait_for_download_ack: 0
I. 2015-10-01 16:47:03. <14> PHASE: get_db_worker_for_download_ack: 0
I. 2015-10-01 16:47:03. <14> PHASE: connect_for_download_ack: 0
I. 2015-10-01 16:47:03. <14> PHASE: nonblocking_download_ack: 0

Thanks for any comments or help

↧

-1117 Mobilink Error

October 6, 2015, 3:35 pm

Latest and popular articles on SAP ERP

≫ Next: Mobilink Error 10012

≪ Previous: mobilink 16 error ODBC: [Sybase][ODBC Driver]Syntax error or access violation (ODBC State = 42000, Native error code = 0)

Hi ,

We have large data to be downloaded from SQL server to iOS via Mobilink. Table has 5 columns out of which 3 of varchar(2000).

I am getting -1117 Error while downloading this table (during Sync). This error says that exceeded db page size.

How to increase this DB page size. Is it from Mobilink server side or iOS side?

Please suggest me to solve this problem.

Thanks,

Suman Kumar

↧

Mobilink Error 10012

October 8, 2015, 9:24 am

Latest and popular articles on SAP ERP

≫ Next: Assertion failed: 200505

≪ Previous: -1117 Mobilink Error

I get the following error when we have sporadic connection / sync issues.

I am able to fix this by resetting the value in the consolidated database to remote database value or below (usually make it 0) then it will finish syncing.

My problem is I may be missing some data at that point, but my only other fix is to reload the whole database

I have tried everything to trap for this event, I would like to be able to insert some logging so we can notify our support team when this happens.

It does not look like the handle_error event is even firing...

W. <18> [10012] The consolidated and remote databases disagree on when the last synchronization took place, the progress offsets are 99 in the consolidated database and 83 in the remote database. The remote is being asked to send a new upload that starts at the last known synchronization point

E. <18> [-10035] Download failed with client error -794

I have tried the following events

handle_error / handle_odbc_error events

{CALL ps_error_insert({ml s.action_code}, {ml s.error_code}, {ml s.error_message}, {ml s.username}, {ml s.table} )}

These events only seems to fire when I have an odbc / sql error .

I thought that this would fire for all errors...

end_synchronization event

Insert into SyncStatus(RemoteID,UserID,SyncStatus,ScriptVersion)

Values({ml s.remote_id},{ml s.username},{ml s.synchronization_ok},{ml s.script_version})

This event seems to only fire when i have a successful sync.

Where do i put this trap ?

Thanks

Jay

↧

SQL Anywhere for PC Platforms

SQL Anywhere for Linux, Unix and OS X Platforms

MobiLink Synchronization for PC Platforms

MobiLink Synchronization for Linux, Unix and OS X Platforms

QAnywhere Client for PC Platforms

UltraLite

Engineering Support Status for SAP SQL Anywhere

Mainstream Maintenance

Operating Systems Notes

Databases

SQL Anywhere

UltraLite

Synchronization, Messaging and Replication

MobiLink

QAnywhere21

SQL Remote for SQL Anywhere

Administration Tools

Compatibility with existing Sybase Central software

Documentation

Footnotes

Recommended ODBC Drivers for 17.0.0 MobiLink

Recommended Drivers

SAP SQL Anywhere (SQLA) 16.0 and 17.0

SAP SQL Anywhere (SQLA) 16.0

SAP SQL Anywhere (SQLA) 17.0.0

SAP Adaptive Server Enterprise 15.7 and 16.0

SAP Adaptive Server Enterprise 15.7

SAP Adaptive Server Enterprise 16.0

SAP IQ 15.4 and 16.0

SAP IQ 15.4

SAP IQ 16.0

Oracle 11g and 12.1

Oracle 11g

Oracle 12.1

Microsoft SQL Server 2012 and 2014

Microsoft SQL Server 2012

Microsoft SQL Server 2014

IBM DB2 9.7 and 10.5

IBM DB2 9.7

IBM DB2 10.5

MySQL 5.5.16 and 5.6.20

MySQL 5.5.16

MySQL 5.6.20

Updates to DBValid/DBValidate()

The jConnect JDBC driver

SQL Anywhere for PC Platforms

SQL Anywhere for Linux, Unix and OS X Platforms

MobiLink Synchronization for PC Platforms

MobiLink Synchronization for Linux, Unix and OS X Platforms

QAnywhere Client for PC Platforms

UltraLite

Engineering Support Status for SAP SQL Anywhere

Mainstream Maintenance

Operating Systems Notes

QAnywhere²¹