SQL Anywhere 10.0.1 Documentation Errata
Copyright © 2007, iAnywhere Solutions, Inc.
All rights reserved. All unpublished rights reserved.
Contents
========
This file lists significant factual corrections to the documentation for
SQL Anywhere Studio 10.0.1.
The entries are arranged by book. The book names appear in the Online
Books table of contents. Each entry is described by a location and a
description, as follows:
Location:
chapter-name > section-name > subsection-name
Description:
The text incorrectly states that...
It should state that...
SQL Anywhere 10 - Introduction
==============================
SQL Anywhere 10 - Changes and Upgrading
=======================================
SQL Anywhere 10 - Context-Sensitive Help
========================================
SQL Anywhere 10 - Error Messages
================================
SQL Anywhere Server - Database Administration
=============================================
Location:
SQL Anywhere Server - Database Administration
> Database Administration Utilities
> Language Selection utility (dblang)
Description:
The text incorrectly states that -q is the only option for the dblang
utility.
It should state that the -m and -u options are also supported. When you
specify the -m option, the language code is written to the registry under
HKEY_LOCAL_MACHINE. When you specify the -u option, the language code is
written to the registry under HKEY_CURRENT_USER. If you do not specify -m
or -u, then the language code is written to the registry under
HKEY_CURRENT_USER. You can specify both -m and -u to write the language
code to both locations.
-----------------------------------------------------------------------------
Location:
SQL Anywhere Server - Database Administration
> Database Administration Utilities
> Initialization utility (dbinit)
Description:
The documentation should state that the dbinit -e option is deprecated. It
is recommended that you use the -ea option instead.
-----------------------------------------------------------------------------
Location:
SQL Anywhere Server - Database Administration
> Connecting to a Database
> Working with ODBC data sources
> Creating an ODBC data source on Mac OS X
Description:
The text incorrectly states that the data source name is
SQL Anywhere 10 Demo in step 4 of the procedure "To create an ODBC data
source". It should state that the name of the ODBC data source is Demo10.
The connection parameters table in Step 4 of this procedure is missing the
Driver connection parameter:
Keyword Value
==================================================================
Driver /Applications/SQLAnywhere10/System/lib32/dbodbc10_rbundle
-----------------------------------------------------------------------------
Location:
SQL Anywhere® Server - Database Administration
> Transport-Layer Security
> Encrypting MobiLink client/server communications
> Configuring MobiLink clients to use transport-layer security
> Configuring SQL Anywhere clients to use transport-layer security
Description:
The final two examples are incorrect. The correct examples are as follows:
The following example specifies RSA security and TCP/IP. It must all be
written on one line:
dbmlsync -c "eng=rem1;uid=myuid;pwd=mypwd"
-e "ctp=tcpip;
adr=port=3333;
tls_type=rsa;
trusted_certificates=c:\test\public_cert.crt;
certificate_company=Sybase, Inc.;
certificate_unit=IAS;
certificate_name=MobiLink"
Alternatively, you can specify the CommunicationAddress extended option
using the CREATE SYNCHRONIZATION SUBSCRIPTION or ALTER SYNCHRONIZATION
SUBSCRIPTION statement:
CREATE SYNCHRONIZATION SUBSCRIPTION
TO pub1
FOR user1
ADDRESS 'port=3333;
tls_type=rsa;trusted_certificates=public_cert.crt;
certificate_company=Sybase, Inc.;
certificate_unit=IAS;
certificate_name=MobiLink';
-----------------------------------------------------------------------------
Location:
SQL Anywhere Server - Database Administration
> Database Administration Utilities
> Interactive SQL utility (dbisqlc)
Description:
In the Syntax section, immediately after the dbisqlc syntax, the following
sentence should not appear: "Scan commands but do not execute them. This
is useful for checking long command files for syntax errors."
The same sentence, located in the description of the -x option, is correct.
SQL Anywhere Server - Programming
=================================
Location:
SQL Anywhere Server - Programming
> Deploying Databases and Applications
> Deploying client applications
> Deploying JDBC clients
Description:
The text states that, for dbjodbc10.dll, the Unix shared library name is
libdbjodbc10.so. The text should also state that, for MAC OS X, the shared
library is called libdbjodbc10.jnilib.
SQL Anywhere Server - SQL Reference
===================================
Location:
SQL Anywhere Server - SQL Reference
> Views
> System views in Sybase Central
> SYSTRIGGER system view
Description:
The following two values are also possible for the SYSTRIGGER trigger_time
field,
I - INSTEAD OF (row-level trigger)
K - INSTEAD OF (statement-level trigger)
SQL Anywhere Server - SQL Usage
===============================
Location:
SQL Anywhere® Server - SQL Usage
> Working with Database Objects
> Working with views
> View dependencies
> View status
Description:
The current documentation states: "If you alter t to remove c1, the status
of v1 is set to INVALID when the database server tries to recompile the
view as part of the ALTER operation that drops the column. In this case,
v1 can recompile only after c1 is added back to t, or v1 is changed to no
longer refer to c1."
This incorrectly implies that an ALTER VIEW statement can correct the
problem with the INVALID view. Following are the two ways to resolve an
INVALID view:
1. DROP the view, and then CREATE it without the referenced column. Upon
successful creation of the view, the view is automatically enabled.
2. Restore the referenced object (table, column, etc.) and execute an
ALTER VIEW .. ENABLE to re-enable the view.
MobiLink - Getting Started
==========================
MobiLink - Client Administration
================================
Location:
MobiLink - Client Administration
> MobiLink Client Network Protocol Options
> trusted_certificates
Description:
The UltraLite examples are incorrect. The correct examples are as follows:
On an UltraLite client, the implementation is:
info.stream = "https";
info.stream_parms = TEXT(
"port=9999;
trusted_certificates=\rsaroot.crt;
certificate_name=RSA Server");
On an UltraLite client running Palm OS, the stream and stream_parms can be
set like this:
info.stream = "https";
info.stream_parms = "trusted_certificates=vfs:/rsaroot.crt;port=9999";
MobiLink - Server Administration
================================
MobiLink - Server-Initiated Synchronization
===========================================
QAnywhere
=========
Location:
QAnywhere
> Mobile Web Services
> Compiling and running mobile web service applications
Description:
The following information is missing: Mobile web services are supported
only on JDK 1.5 and higher.
SQL Remote
==========
UltraLite - Database Management and Reference
=============================================
Location:
UltraLite - Database Management and Reference
> UltraLite Utilities Reference
> UltraLite Data Management utility for Palm OS (ULDBUtil)
Description:
The following information is missing from the description: The ULDBUtil
utility is used to back up and/or delete databases from Palm OS devices.
It does this by using a filter; only those databases that meet the filter
requirements are detected. Note that this filter does not detect and list
any UltraLite databases with the following extensions: .bak, .dat, .dba,
.htm, .html, .ini, .jpeg, .jpg, .prc, .pqa, and .tda.
UltraLite - AppForge Programming
================================
UltraLite - C and C++ Programming
=================================
UltraLite - M-Business Anywhere Programming
===========================================
UltraLite - .NET Programming
============================
