Hi.

I've created a .Net 3.5 DLL which is called by a stored procedure using CLR in a trigger.

Inside one of the functions I've got an update-statement against the same table as the trigger which calls the CLR code.

That update results in a SAExeption:

30.04.2014 14:19:55 (ConnID. 89) - W747lnr=4000996, Error: Feature 'nested external environment calls' not implemented

iAnywhere.Data.SQLAnywhere.SAException: Feature 'nested external environment calls' not implemented

   at iAnywhere.Data.SQLAnywhere.SACommand.ExecuteReader()

   at CLRKalkyle.Exts.Execute(SAConnection conn, String sql, Object[] args)

   at CLRKalkyle.CalculusFunctions.DivInnfrakt(SAConnection conn, Pallet palle, Decimal totkvant)

   at CLRKalkyle.CalculusFunctions.GetInnfrakt(SAConnection conn, Int32 klientnr, String uttakstype, Int32 uttaksnr, Int32 w722lnr)

   at CLRKalkyle.Exts.DivKalkyle(SAConnection conn, Int32 klientnr, String uttakstype, Int32 uttaksnr, Int32 w722lnr, Int32 w747lnr)

   at CLRKalkyle.CLRKalkyle.GenKalkyle(Int32 klientnr, Int32 w747lnr)

I'm using SAServerSideConnection without transaction (the CLR is called per row in the database).

Is it possible to run the update in a new thread, or perhaps a new connection?

Or do I have to run the update after all the other code is finished?

Hope you understand my problem.

Regards,

Bjarne Anker

I'm trying to get to the SQL Anywhere EBFs and keep getting the following on the link I used to follow:

--swdFC.doProcess: action perform exception: EcdDataException: EcdDataException: BaseProdList.getMigrationStatus got Exception: null

Have they now moved them to a SAP URL or is there a problem with the site?

Thanks

I am used to dealing with SA 12 and when it would start, it would display the number of physical processors and the logical processors (cores).  It would then state how many physical processors it will use based on the license and then start worker threads for every logical processor found within the physical processors it would use.  In other words, if we have a 2 chip license and a computer with 2 quad core processors, it would say it sees 2 physical processors, 8 logical processors and I could tell through process explorer that is basically started 8 worker threads.  If it used only one of the processors, it would have fewer threads.  I am also basing this in discussions I've had in the past with Sybase support analysts.

Here's a snippet of what I see with SA 12:

Processors detected: 2 (containing 24 logical processors)

Maximum number of physical processors the server will use: 2

With SA 16, I noticed when I installed it, it asked the number of cores licensed.  This used to be the number of processors with SA 12.

This has me concerned how the new version does things.

Here's a snippet from SA 16:

Processors detected: 2 (containing 24 logical processors)

Maximum number of processors the server will use: 2 physical processor(s), 2 core(s)

I just want to make sure I understand what the engine is going to do as far as worker threads goes because this has been an issue in the past with customers and how they setup their servers.

All SAP SQL Anywhere Support Packages (SPs) are available for download in the SAP Service Marketplace (SMP).  Please note that you must be an SAP customer or partner with an active support plan to access the SMP.  For information on how to register your S-user ID, visit the SAP Service Marketplace FAQs.

Step 1: Log in to SMP

1. Open a web browser and navigate to the SMP web page: https://websmp101.sap-ag.de/public/home.
2. Click on the link "SAP Support Portal" and log in using your SMP user ID and password.

Note: If you do not have a user name or password, you can click on the "Register" link at the top right below the sitemap.

Step 2: Locate the SAP SQL Anywhere SPs

1. You are now in the Support Portal Home page.  On the top navigation bar, click the link "Software Downloads".

2. On the left navigation bar, click the links "Support Packages and Patches" and "A - Z Index".  The index appears in the main panel and click on the letter "S" to look for SAP SQL Anywhere.

Note: There are many ways to search for SAP SQL Anywhere.  This guide uses the index, but you can use the text search capability of SMP.

3. All SAP products beginning with the letter S appear in the main panel.  Scroll down to see "SAP SQL Anywhere" and click on its link.

Step 3: Download SPs for your version of SAP SQL Anywhere

1. Click on the link for your version of SAP SQL Anywhere.

2. Click on the link for your operating system.

3. Scroll down to the bottom of the page to see the list of available SPs for that platform and click on the appropriate SP object to begin the download process.  Alternatively, you can use the SMP Download Basket.

Once the SP downloads successfully, extract it and execute its installation program.

You may archive or delete the SP object after the installation completes successfully.

I originally posted this a few years ago to help people configure their Java applications to use the iAnywhere JDBC driver, which was replaced by the SQL Anywhere JDBC driver in SQL Anywhere version 12.  I am reposting it here with a few minor updates, since I still refer to it occasionally and I think it is still useful.

I have heard from customers that connecting to SQL Anywhereover JDBC can be difficult at times.  In my investigations of this, I have found that this is almost always due to confusion over the classname to use to register the JDBC driver, and the URL's to use to actually connect to the database.  In stepping back, I can see how people might easily get confused based on the history of the JDBC driver.  Here is my attempt to clarify things by following the history of the driver, starting with SQL Anywhere version 9.

Before I go into detail on the history of the SQL Anywhere JDBC driver, here is a table which explains classpath settings, jar files required, driver name URLs and sample connection URLs.

1. Adaptive Server Anywhere version 9.0 (aka SQL Anywhere 9.0)
   In version 9, SQL Anywhere supported JDBC 2.0 using an iAnywhere generic JDBC-ODBC bridge driver (similar to but different from the Sun JDBC/ODBC driver).  The jar file is jodbc.jar, and resides in the %ASA90%\java directory.  To use the iAnywhere JDBC driver, you need to include the jar in your classpath.  Then, you need to register it in your java app using the following code:

    

   DriverManager.registerDriver(    (Driver)Class.forName( "ianywhere.ml.jdbcodbc.IDriver" ).newInstance() );

    

   Since the iAnywhere JDBC/ODBC driver is a bridge driver, to connect to your SQL Anywhere database, you need to specify a "DRIVER=" parameter along with the rest of your connect string.  For example:

    

   Connection con = DriverManager.getConnection(    "jdbc:odbc:Driver=Adaptive Server Anywhere 9.0;UID=DBA;PWD=sql;eng=demo" );

    

   or, you could use an ODBC data source like this:

    

   Connection con = DriverManager.getConnection(    "jdbc:odbc:DSN= Adaptive Server Anywhere 9.0 Sample" );

    

2. SQL Anywhere 10.0.0
   In version 10, we added support for JDBC 3.0.  To use the version 10 iAnywhere JDBC/ODBC bridge driver, you need to again include %SQLANY10%\java\jodbc.jar in your classpath.  However, the class name for driver registration is slightly different:

    

   DriverManager.registerDriver(    (Driver)Class.forName( "ianywhere.ml.jdbcodbc.jdbc3.IDriver" ).newInstance() );

   Once registered, the connection URL was the same as in verison 9, above.

    

3. SQL Anywhere 10.0.1
   After version 10 was released, we noticed that in some customer issues involving JDBC, the iAnywhere driver was not always being loaded when it was supposed to be, particularly when the Sun JDBC/ODBC bridge driver was present.  It turns out that our use of "jdbc:odbc" in the connection URL was not sufficient to guarantee that the iAnywhere driver would be used during a connection.  If the Sun bridge were present, it could be picked up and used instead, which lead to all sorts of unexpected behaviour. To resolve this problem, the 10.0.1 maintenance release introduced a new URL header for the iAnywhere driver, "jdbc:ianywhere".  From this point forward, the URL to register the driver was the same as with v10, but the correct URL to use when connecting to the database was as follows:

    

   Connection con = DriverManager.getConnection(    "jdbc:ianywhere:Driver=SQL Anywhere 10;DSN= SQL Anywhere 10 Sample" );

   The "jdbc:ianywhere" portion of the connection string was actually back-ported to a 9.0.1 ebf, so if you are running one of the later 9.0.1 or 9.0.2 ebfs, the above connection URL will work for you as well.

    

4. SQL Anywhere version 11.0.0
   In SQL Anywhere version 11, there was no change in classname for the driver or URL for the connection string, but we did update to a newer version of the JDK. This meant we had to drop the JDBC 2.0 driver, because JDK 1.4 and newer no longer supported it.  To make things easier for our customers, we kept the JDBC 2.0 class names in the version 10 JDBC 3.0 jar.  They simply pointed to the JDBC 3.0 equivalents.

    

5. SQL Anywhere 11.0.1
   In SQL Anywhere version 11.0.1, a new SQL Anywhere JDBC driver was introduced.  No longer a generic iAnywhere JDBC driver, it is a JDBC driver specific to SQL Anywhere.  This was done to make it easier (ie. less confusing) for people to use JDBC with SQL Anywhere.  With the new driver, there is no need to install ODBC on the system.  This wasn't a problem for Windows, but our Linux and Unix customers often had problems with this.  As an added bonus, the performance of the driver was improved slightly because we no longer have to go through the ODBC driver manager. This change involved adding 2 new files to the SQL Anywhere installation:  sajdbc.jar and dbjdbc11.dll. To use the new driver, you need to include %SQLANY11%\java\sajdbc.jar in your classpath.  Then, the driver registration is as follows:

    

   DriverManager.registerDriver(   (Driver) Class.forName( "sybase.jdbc.sqlanywhere.IDriver" ).newInstance() );

   Then, to connect, you use the following URL:

    

   Connection con = DriverManager.getConnection(    "jdbc:sqlanywhere:uid=DBA;pwd=sql;eng=demo" );
6. SQL Anywhere 12/16
   SQL Anywhere 12 deprecated the use of the iAnywhere JDBC/ODBC bridge driver in favor of the new SQLAnywhere driver.  In addition, SQL Anywhere 12 will support JDBC 4.0 (which requires JDK 1.6 or newer). To continue to use the JDBC 3.0, users do not have to make any changes from previous versions.  However, to use the JDBC 4.0 support, the new driver name is "sybase.jdbc4.sqlanywhere.IDriver", and requires that %SQLANY12%\java\sajdbc4.jar be in your classpath. However, there is no need to call DriverManager.registerDriver(...) to register the driver before using it anymore.  Sun has implemented automatic driver registration so that applications just need to make sure that sajdbc4.jar is in the classpath (and dbjdbc12.dll is in the path), and use the "jdbc:sqlanywhere" URL header to connect.  So, to connect with SQL Anywhere 12 and JDBC 4.0, all you need is something like the following line of code:

    

   Connection con = DriverManager.getConnection(    "jdbc:sqlanywhere:uid=DBA;pwd=sql;eng=demo" );

That concludes our history lesson. Confused yet?

I want to transfer data from a SQL Anywhere database to a Microsoft SQL Server database on a second computer.  The second computer is running Windows Server 2008R2 and the only application installed on it is Microsoft SQL Server 2008.

I believe I could do this if I had on ODBC driver for SQL Anywhere installed on the second computer.

Where can I find an ODBC driver for SQL Anywhere?   I am not sure of the version of SQL Anywhere.   Do the ODBC drivers for SQL Anywhere support multiple version of SQL Anywhere?

Hello,

we have a PowerBuilder application and want to add a feature where the user can run queries to extract spreadsheets/txt files. The required SQL is stored in a text field in the database. With a simple Select I generate a dynamic datawindow and all is good. Some of the queries though are large compound statements and I put these into a file and call dbisql to execute the file, which works very nicely....... In my development environment So far we haven't deployed dbisql with the application. We do put out dear old dbisqlc but that doesn't do the OUTPUT statement we need.

The solution would seem to be to deploy dbisql which is fine. Unfortunately we have some users who will notice and of course they'll be able to login to the database with dbisql using their application login and potentially cause all sorts of havoc. Is there any way we can restrict the people who can use dbisql on our client installations?

Failing that can anyone think of an alternative to execute a series of SQL commands stored in a string that is able to output a text file, all done from within an application (PowerBuilder in our case)?

TIA, Paul

In this post, originally written by Glenn Paulley and posted to sybase.com in August of 2009, Glenn talks about validation of SQL statements against the ANSI/ISO SQL Standard from within SQL Anywhere.  Note also that the flagger has been enhanced to support SQL:2008 in more recent versions of SQL Anywhere.

The flagging of SQL statements is defined in the ANSI/ISO SQL:2008 standard as language features F812 ("basic" flagging) and F813 ("extended" flagging). Flagging is the notion of identifying non-conformance of specific SQL constructions with respect to the ANSI/ISO SQL standard. Here's a simple example using the sample DEMO database with SQL Anywhere:

SELECT SQLFLAGGER( 'SQL:2003/Core', 'SELECT TOP 10 * FROM Customers                                                                                WHERE State IN (''NJ'', ''NC'') AND Country LIKE ''%USA%'' ORDER BY Surname' );

Flagging in SQL Anywhere

SQL Anywhere offers several ways to invoke the SQL Flagger to check a SQL statement, or a batch of SQL statements. They include:

• the SQLFLAGGER()function;
• the SQL_FLAGGER_ERROR_LEVEL and SQL_FLAGGER_WARNING_LEVEL connection options;
• the SA_ANSI_STANDARD_PACKAGES system procedure; and
• flagging capabilities in the SQL preprocessor (SQLPP).

The SQLFLAGGER function

The SQLFLAGGER() function analyzes a single SQL statement, or batch, passed as a string argument, for compliance with a given SQL standard. The statement or batch is parsed, but not executed. The function returns a LONG VARCHAR containing any error messages output by the flagger. The first parameter is the standard/implementation to which the SQL statement is to be compared; SQL Anywhere supports compliance comparisons with SQL:2003 (Core/Package), SQL:1999 (Core/Package), SQL:1992 (Full, Intermediate, Entry) and Ultralite.

At this time, it is unknown if the forthcoming Innsbruck release of SQL Anywhere will offer Flagging support for the current SQL:2008 standard.

The SQL_FLAGGER_ERROR_LEVEL and SQL_FLAGGER_WARNING_LEVEL connection options

The SQL_FLAGGER_ERROR_LEVEL and SQL_FLAGGER_WARNING_LEVEL connection options invoke the SQL Flagger for any statement prepared or executed for the connection. If the statement does not comply with the option setting, which is a specific ANSI standard or UltraLite, the statement either terminates with an error (SQLSTATE 0AW03), or returns a warning (SQLSTATE 01W07), depending upon the option setting. If the statement complies, statement execution proceeds normally.

The SA_ANSI_STANDARD_PACKAGES system procedure

The SA_ANSI_STANDARD_PACKAGES() system procedure analyzes a statement, or batch, for the use of optional packages from the ANSI/ISO SQL:2003 or SQL:1999 international standards. The procedure takes two parameters: the first, a string that identifies the desired standard, and the second is the SQL statement to be analyzed. The result of the procedure is a list of the optional SQL standard packages utilized by the statement. Here is an example:

Flagging in the SQL preprocessor

The SQL preprocessor (SQLPP) has the ability to flag static SQL statements in an embedded SQL application at compile time. This feature can be especially useful when developing an UltraLite application, to verify SQL statements for UltraLite compatibility. Using the flagger with SQLPP simply involves setting additional command line switches when invoking SQLPP.

Hello,

We use SQL Anywhere 11 - dbsrv starts with TLS encryption (-xTCPIP -ec tls(tls_type=rsa;identity=C:\identity.pem;identity_password=pass) ). The client application connects with ODBC and everything works fine.

We tried to migrate to SQL Anywhere 16. After installing version 16 everything works fine - as it was in v.11. But after installing the latest EBF we can't connect to the database. We got TLS handshake failure error.

Dbsrv starts with the same parametrers every time, ODBC doesn't change.

Do you know any solution for that? We cant' find anything online - it's a bit strange. Does anyone use TLS encryption with SQL Anywhere?

TIA,

Patryk

In this post, originally written by Glenn Paulley and posted to sybase.com in August of 2009, Glenn talks about blank padded character strings and how they behave with respect to the LIKE predicate.

In the SQL:2008 standard, fixed-length character string values are blank padded. Blank padding occurs during storage of a fixed-length character string value when its original size is less than the declared width of the column. Blank padding also occurs when fixed-length character strings are compared using any string comparison predicate. For storage, here is the relevant quote from Section 9.2 (Store assignment), General rule 2(b)(iii), that defines the behaviour for storing value V in column T:

If the declared type of T is fixed-length character string with length in characters L and the length in characters M of V is less than L, then the first M characters of T are set to V and the last M characters of T are set to spaces.

SQL Anywhere, however, does not blank-pad fixed-length character strings. In a SQL Anywhere database, every string is stored as if the column is aVARCHARtype. This means that all blanks in a string value (trailing or otherwise) are treated as significant characters; hence the value 'a ' (the character 'a' followed by a blank) is not equivalent to the single-character string 'a'. Inequality comparisons also treat a blank as any other character in the collation.

SQL Anywhere offers the ability to mimic ANSI SQL character-string comparison semantics with the "blank padding" option, which can be specified with either the dbinit utility or the CREATE DATABASE statement. With the blank-padding option enabled, trailing blanks in a string are ignored when being compared. Ignoring trailing blanks has equivalent semantics to blank-padding for equality and inequality ("!=") operations. However, this behaviour is not identical to blank-padding semantics for other comparison operators such as less than ("<")

LIKE Semantics With and Without Blank Padding

The semantics of a LIKE pattern in SQL Anywhere does not change if the database is blank-padded because matching the expression to the pattern involves a character-by-character (or code point by code point, in the case of UTF8 databases) comparison in a left-to-right fashion. No additional blank padding (or truncation) is performed on the value of either expression or pattern during the computation. Therefore, the expression "a1" matches the pattern "a1", but not the patterns "a1 " ("a1" with a trailing blank) or "a1_". These semantic differences occur whenever the expression or the pattern contain trailing spaces, and, as we shall see, also illustrate differences in other relational DBMS products, in virtually all cases due to the retention of legacy behaviour.

LIKE examples

To illustrate - my thanks to John Smirnios for the following analysis - we define a table T consisting of four string columns as follows:

CREATE TABLE T( a CHAR(1), b CHAR(2), c CHAR(3), d VARCHAR(10) );

and into table T we insert two rows, the first row with a single character 'a' in each column, and the second row with the value 'a ' (an 'a' followed by a blank) in each column, as follows:

INSERT INTO T VALUES( 'a',  'a',  'a',  'a' ); 
INSERT INTO T VALUES( 'a ', 'a ', 'a ', 'a ' );

A test of 12 specific test cases across a variety of database systems yielded the following results:

Additional notes:

1. Sybase ASE and Microsoft SQL Server 2005 always strip all trailing blanks from the end of VARCHAR values. In these two systems, it is impossible to store a blank at the end of a VARCHAR string.
2. In Sybase IQ, the predicate "d LIKE 'a[ ]'" returns row 2, even though the predicate "d LIKE 'a '" returns both rows 1 and 2.
3. In Sybase ASE, "d LIKE 'a[ ]'" returns no rows even though the predicate "d LIKE 'a '" returns both rows 1 and 2.

Discussion

SQL Anywhere treats all strings as VARCHAR, even in a blank-padded database. For VARCHAR strings, SQL Anywhere's behaviour matches DB2 and Oracle and the ANSI/ISO SQL standard (test cases 4, 8, and 12).

DB2 and Oracle have identical semantics. Fixed-width character columns are effectively always padded to their maximum length and the string's length is always equal to the maximum width of the column. The end of the string must match the end of the pattern. VARCHAR fields retain any trailing blanks that were inserted by the user; blanks are never added to or stripped from VARCHAR fields.

Sybase ASE appears to strip trailing blanks from the pattern string, but it does not strip 'equivalent to blank' expressions (see note 3). However, ASE will retain a single trailing blank in the case of a pattern ending in '%' followed by one or more blanks; this specific exception is documented in the ASE SQL User's Guide. ASE also effectively strips trailing blanks from the match value and then re-pads CHAR columns with enough blanks to match the pattern (but not enough to exceed the width of the column). For VARCHAR match values, blanks are pre-stripped (see note 1) and blanks are never added to allow a match to occur. A pattern ending with an equivalent-to-blank ('[ ]') will never match a VARCHAR string.

Microsoft SQL Server 2005 does not strip trailing blanks from the pattern. However, like ASE, SQL Server appears to strip trailing blanks from the match value and then re-pad CHAR columns with enough blanks to match the pattern but not enough to exceed the width of the column. Blanks are never appended to a VARCHAR to allow a match to occur.

In another post, I'll attempt to outline the differences in semantics with trailing blanks and empty strings with client-server protocols.

My sincere thanks to my colleague John Smirnios for his thorough analysis of LIKE semantics with SQL Anywhere and these other database management systems.

We have had some of our branches complaining about slowness. I have tried tracing the database and viewed the slow running queries to see if that would help but would like to see the I/O impact of some of the procedures to see if it needs to be tuned more.

Branches are on 11.0.1.2452 (running on Windows)

The SAP SQL Anywhere Database Client includes the following components:

• Full set of available client interfaces, such as ODBC, JDBC, ADO.NET and so on.
• Administration tools such as Sybase Central and Interactive SQL.

Note: During installation you will be prompted to review and accept the SQL Anywhere software license agreement. If you do not accept the License Agreement you can either end the product installation or download a 60-day evaluation edition (subject to a software evaluation license).

Please click on the links below to obtain the appropriate software.

Visit the SAP SQL Anywhere Developer Center for links to valuable technical whitepapers, webcasts, Q&As, demos and other information to help with next steps as you evaluate SAP technology.

Dear Experts

I am installed BO 4.1 Sp3 under AIX 7 and default database sqlanywhere

after stop BOE

1. tomcat

2. BOE

3 database

from BOBJ home /usr/sap/BOD/sap_bobj

using scripts

but when in start database

./sqlanywhere_startup.sh  Flowing error occur

SQL Anywhere start In background ........

DBSPAWN ERROR -80

Unable to start database

Please guide me how to solved this issue

Regards

Hello, all

I know it is possible to log the Mobilink errors and send them by email automatically.

Yet, I cannot find the instructions on how to do it in the help.

Can someone, please, point me to a link where it is all explained?

Thank you

Arcady

I'm having a question according to chip licence (CH) of Sybase Anywhere. It's running

Hostserver: Windows Server 2012 Standard

Virtueller Client: Windows Server 2008R2 Enterprise

and on top of this a Anywhere 16 with the CH licence.

Checking via coreinfo the clients shows this:

[...]

Logical to Physical Processor Map:

*---------------  Physical Processor 0

-*--------------  Physical Processor 1

--*-------------  Physical Processor 2

---*------------  Physical Processor 3

----*-----------  Physical Processor 4

-----*----------  Physical Processor 5

------*---------  Physical Processor 6

-------*--------  Physical Processor 7

--------*-------  Physical Processor 8

---------*------  Physical Processor 9

----------*-----  Physical Processor 10

-----------*----  Physical Processor 11

------------*---  Physical Processor 12

-------------*--  Physical Processor 13

--------------*-  Physical Processor 14

---------------*  Physical Processor 15

 

Logical Processor to Socket Map:

****************  Socket 0

 

Logical Processor to NUMA Node Map:

****************  NUMA Node 0

 

[...]

But when starting ASA it only uses one core on that box -- but my understanding would by it is using all of them.

Hi.

I'm trying to compare 2 SA12 databases in Sybase Central using "Tools - SQL Anywhere 12 - Compare databases...".

Both databases are quite small (< 100 Mb), almost no data.

DB1 is an old ASA9 which has been upgraded to SA12 using unload/reaload and "Upgrade database".

DB2 is a SA12 from the start.

It's a lot of similarities in the databases, but I think there are a few missing tables, FK's, triggers and such in DB1.

Therefore I'm trying to compare them so that I can get at sql-file to make them identical.

But it looks like the compare-function never gets finished.

I started it on friday afternoon, and it was still running this morning. So I cancelled the job.

When comparing 2 small databases like this, I think something is wrong?

Or is it supposed to take this long?

I've installed the latest EBF (4104), and started the compare once again.

Is this the best way to compare the databases?

Is there perhaps a commandline I can use?

Regards,

Bjarne Anker

Maritech Systems

Norway

In this post, originally written by Glenn Paulley and posted to sybase.com in September of 2009, Glenn discusses using the PRIORITY option in SQL Anywhere.

SQL Anywhere version 11 deprecated the BACKGROUND_PRIORITY connection option in favour of a new connection option, PRIORITY.

The PRIORITY connection option establishes the processing priority of any SQL request for this connection. The default is "Normal"; other potential values are Critical, High, Above Normal, Below Normal, Low, and Background. When SQL requests are queued for service, the server will process the queue in priority order. Setting the priority option to different values for different connections (or users) permits the categorization of service levels across the entire server's workload.

While individual users can set their own PRIORITY setting, they cannot set their connection's PRIORITY to be greater than the value of the MAX_PRIORITY option. The default setting for the MAX_PRIORITY option is also "Normal"; it's value can be altered only by a user with DBA privileges. Altering the setting is straightforward via the SET OPTION statement:

SET EXISTING OPTION PRIORITY = 'Low'

As with other server, database, and connection-level options, the values of PRIORITY and MAX_PRIORITY can be queried through various means, including the sa_conn_properties() procedure and the CONNECTION_PROPERTY() function, as follows:

Update: I have identified where is the problem located, is in this part of the Publication (where clause), but still don't have solution:

TABLE "TPDA_SERVICE_LINE_DETAIL" WHERE NSLI_SERVICELINE_ID = ANY (SELECT SL.NSLI_SERVICELINE_ID                                  FROM TPDA_JOB JO, TPDA_SERVICE_LINE SL, TPDA_M_STATE_MACHINE SM, TPDA_M_STATE_MACHINE SM2                                  WHERE SM.VSTM_ENTITY = 'J'                                    AND SM.NSTM_NUMBER = 2 -- Done. If the Job is Failed or Recalled, its service line details won't be uploaded.                                    AND JO.NSTM_STATUS_ID = SM.NSTM_STATUS_ID                                    AND SL.NJOB_JOB_ID = JO.NJOB_JOB_ID                                    AND SM2.VSTM_ENTITY = 'S'                                    AND SM2.NSTM_NUMBER = 1 -- Processed. If the Service Line is Failed, its details won't be uploaded.                                    AND SL.NSTM_STATUS_ID = SM2.NSTM_STATUS_ID ),

I have also changed the query to be more compliant, but no sucess:

NSLI_SERVICELINE_ID = ANY (SELECT SL.NSLI_SERVICELINE_ID
FROM
TPDA_SERVICE_LINE SL
inner join TPDA_JOB JO on JO.NJOB_JOB_ID = SL.NJOB_JOB_ID
inner join TPDA_M_STATE_MACHINE SM on SM.NSTM_STATUS_ID = JO.NSTM_STATUS_ID
inner join TPDA_M_STATE_MACHINE SM2 on SM2.NSTM_STATUS_ID = SL.NSTM_STATUS_ID
WHERE SM.VSTM_ENTITY = 'J'
AND SM.NSTM_NUMBER = 2 -- Done. If the Job is Failed or Recalled, its service line details won't be uploaded.
AND SM2.VSTM_ENTITY = 'S'
AND SM2.NSTM_NUMBER = 1) -- Processed. If the Service Line is Failed, its details won't be uploaded.

Hi All!

I'm having some problems on migrating an Ultralite database (v.11) to version 16 using sybase central on Windows 7 x64 (using both 32 and 64 bit versions). I had unload the database with the Sybase central wizard, and created an XML containing all data and schema, and also publications. When I try to load this XML into a new database version 16, the apps Crashes:

I've identified that if i don't include the Publications in the unload, then all works.

Also when I try to create a new publication the Sybase central crashes:

[ODBC] [UltraLite Database] Connection was terminated

SQLCODE: -308

SQLSTATE: ERROR

SQL Statement:

I have tried also to recreate the publications with this SQL Script:

CREATE PUBLICATION "fullSynchro_Pub" (  TABLE "TPDA_ADJUSTMENT_LINE",  TABLE "TPDA_JOB",  TABLE "TPDA_M_ACTION_TYPE",  TABLE "TPDA_M_ADJUST_TYPE",  TABLE "TPDA_M_ASSIGNED_QUESTIONNAIRES",  TABLE "TPDA_M_COUNTRY_PARAMETERS",  TABLE "TPDA_M_DATA_USE_CONSENT",  TABLE "TPDA_M_ELECTRIC_COMPANY",  TABLE "TPDA_M_ELECTRIC_REFUND_TYPE",  TABLE "TPDA_M_FAILURE_REASON",  TABLE "TPDA_M_INDICATOR_TYPE",  TABLE "TPDA_M_JOB_TYPE",  TABLE "TPDA_M_LANGUAGE",  TABLE "TPDA_M_MANUFACTURER",  TABLE "TPDA_M_MODEL",  TABLE "TPDA_M_PARAM_DOMINIUM",  TABLE "TPDA_M_PARAMETER",  TABLE "TPDA_M_PRODUCT",  TABLE "TPDA_M_PRODUCT_ADJUST_NEED",  TABLE "TPDA_M_PRODUCT_GROUP",  TABLE "TPDA_M_PRODUCT_TYPE",  TABLE "TPDA_M_QUESTIONNAIRE",  TABLE "TPDA_M_RISK_ASSESSMENT_QUESTION",  TABLE "TPDA_M_RISK_QUESTION_ANSWER",  TABLE "TPDA_M_STATE_MACHINE",  TABLE "TPDA_M_STREET_TYPE",  TABLE "TPDA_M_THERAPY_SORT",  TABLE "TPDA_M_TRIP_TYPE",  TABLE "TPDA_M_UNSIGNED_REASON",  TABLE "TPDA_M_VAN_OPERATIONS",  TABLE "TPDA_M_VAN_STATUS",  TABLE "TPDA_MATERIAL",  TABLE "TPDA_NEXT_VISIT",  TABLE "TPDA_PATIENT",  TABLE "TPDA_PATIENT_ADDRESS",  TABLE "TPDA_PATIENT_DOCUMENTS",  TABLE "TPDA_PATIENT_INDICATOR",  TABLE "TPDA_PATIENT_SIGNATORIES",  TABLE "TPDA_PATIENT_SIGNATURE",  TABLE "TPDA_READING_METER_LINES",  TABLE "TPDA_RISK_ASSESSMENT_ANSWER",  TABLE "TPDA_SAFETY",  TABLE "TPDA_SERVICE_LINE" WHERE NSTM_STATUS_ID IN (11,12),  TABLE "TPDA_SERVICE_LINE_DETAIL" WHERE NSLI_SERVICELINE_ID = ANY (SELECT SL.NSLI_SERVICELINE_ID                                  FROM TPDA_JOB JO, TPDA_SERVICE_LINE SL, TPDA_M_STATE_MACHINE SM, TPDA_M_STATE_MACHINE SM2                                  WHERE SM.VSTM_ENTITY = 'J'                                    AND SM.NSTM_NUMBER = 2 -- Done. If the Job is Failed or Recalled, its service line details won't be uploaded.                                    AND JO.NSTM_STATUS_ID = SM.NSTM_STATUS_ID                                    AND SL.NJOB_JOB_ID = JO.NJOB_JOB_ID                                    AND SM2.VSTM_ENTITY = 'S'                                    AND SM2.NSTM_NUMBER = 1 -- Processed. If the Service Line is Failed, its details won't be uploaded.                                    AND SL.NSTM_STATUS_ID = SM2.NSTM_STATUS_ID ),  TABLE "TPDA_SUMMARY_MATERIAL",  TABLE "TPDA_SYNCHRO_INFORMATION",  TABLE "TPDA_THERAPY",  TABLE "TPDA_THERAPY_PARAMETER",  TABLE "TPDA_TRIP",  TABLE "TPDA_VAN_LOADED_MATERIAL" WHERE BVLM_ACCEPTED = 1,  TABLE "TPDA_VAN_RECOUNT_MATERIAL" WHERE BREC_ACCEPTED = 1,  TABLE "TPDA_W_IDENTIFIERS",  TABLE "TPDA_W_SQL_SENTENCES"
)
GO
CREATE PUBLICATION "loadVanSynchro_Pub" (  TABLE "TPDA_SAFETY",  TABLE "TPDA_SYNCHRO_INFORMATION",  TABLE "TPDA_VAN_LOADED_MATERIAL" WHERE BVLM_ACCEPTED = 1,  TABLE "TPDA_VAN_RECOUNT_MATERIAL" WHERE BREC_ACCEPTED = 1
)
GO
CREATE PUBLICATION "loadVisionOx_Pub" (  TABLE "TPDA_VISIONOX"
)
GO
CREATE PUBLICATION "openTrip_Pub" (  TABLE "TPDA_SAFETY",  TABLE "TPDA_SYNCHRO_INFORMATION",  TABLE "TPDA_TRIP",  TABLE "TPDA_VAN_LOADED_MATERIAL" WHERE BVLM_ACCEPTED = 1,  TABLE "TPDA_VAN_RECOUNT_MATERIAL" WHERE BREC_ACCEPTED = 1
)
GO

But I only can create the first one ("fullSynchro_pub").

When I try to delete it on the new database, i get the same error again...

There is a bug related or something that i'm doing wrong? Somebody can help?

Thanks a lot. I've attached the full SQL Script and XML File to help understanding.

Thanks a lot in advance.

Message was edited by: Naim Raja

Hi all,

I'm having problems while synchronizing an ultralite database (migrated from v.11 to v.16) in a windows mobile application. The server has this config (log startup):

I. 2014-05-29 10:17:36. SQL Anywhere MobiLink Server Version 16.0.0.1824

I. 2014-05-29 10:17:36.

I. 2014-05-29 10:17:36. Copyright ø 2014 SAP AG or an SAP affiliate company.

I. 2014-05-29 10:17:36. All rights reserved.

I. 2014-05-29 10:17:36. Use of this software is governed by the Sybase License Agreement.

I. 2014-05-29 10:17:36. Refer to http://www.sybase.com/softwarelicenses.

I. 2014-05-29 10:17:36.

I. 2014-05-29 10:17:36. This server is licensed to:

I. 2014-05-29 10:17:36.     Developer Edition

I. 2014-05-29 10:17:36.     Restricted Use

I. 2014-05-29 10:17:36. Running Windows 7 Build 7601 Service Pack 1 on X86_64

I. 2014-05-29 10:17:36. Server built for X86_64 processor architecture

I. 2014-05-29 10:17:36. <Main> Option 1: -c

I. 2014-05-29 10:17:36. <Main> Option 2: dsn=BDConsolidada16;uid=CARMCTUser;pwd=********

I. 2014-05-29 10:17:36. <Main> Option 3: -zs

I. 2014-05-29 10:17:36. <Main> Option 4: devNaim

I. 2014-05-29 10:17:36. <Main> Option 5: -dl

I. 2014-05-29 10:17:36. <Main> Option 6: -x

I. 2014-05-29 10:17:36. <Main> Option 7: http(host=10.7.27.114;port=2009)

I. 2014-05-29 10:17:36. <Main> Option 8: -o

I. 2014-05-29 10:17:36. <Main> Option 9: D:\Desarrollo\BDMobiLinkConsolidada\Mobilink.log

I. 2014-05-29 10:17:36. <Main> Option 10: -v+

I. 2014-05-29 10:17:36. <Main> Option 11: -sl

I. 2014-05-29 10:17:36. <Main> Option 12: dnet(-clrVersion=v4.0.30319

I. 2014-05-29 10:17:36. <Main> Option 13: -MLAutoLoadPath=D:\Projects\Inator3\PDASYS~1\PDA\SYNCHR~1\SYNCHR~1.0-S\bin\Debug

I. 2014-05-29 10:17:36. <Main> Verbose logging: show upload row values

I. 2014-05-29 10:17:36. <Main> Verbose logging: show download row values

I. 2014-05-29 10:17:36. <Main> Verbose logging: show script names when invoked

I. 2014-05-29 10:17:36. <Main> Verbose logging: show script contents when invoked

I. 2014-05-29 10:17:36. <Main> Verbose logging: show schema for each table

I. 2014-05-29 10:17:36. <Main> Verbose logging: show an error when the first read of a synchronization fails

I. 2014-05-29 10:17:36. <Main> Verbose logging: show translated SQL for prepared statements

I. 2014-05-29 10:17:36. <Main> Verbose logging: show rowcount values

I. 2014-05-29 10:17:36. <Main> Cache size: 52428800 bytes

I. 2014-05-29 10:17:36. <Main> Download cache directory size: 10485760 bytes

I. 2014-05-29 10:17:36. <Main> Local file for remote synchronization logs: 'mlsrv.mle'

I. 2014-05-29 10:17:37. <Main> Starting cache sizes: min of 52428800 bytes; max of 5973578956 bytes; initial size of 52142080 bytes

I. 2014-05-29 10:17:37. <Main> Individual database connections will be closed after synchronization errors

I. 2014-05-29 10:17:37. <Main> Maximum number of BLOB bytes to compare: 4294967295

I. 2014-05-29 10:17:37. <Main> Maximum number of database connections: 5

I. 2014-05-29 10:17:37. <Main> Maximum number of deadlock retries: 10

I. 2014-05-29 10:17:37. <Main> Timeout for inactive database connections: 60 minutes

I. 2014-05-29 10:17:37. <Main> Maximum delay between retries after deadlock: 30 seconds

I. 2014-05-29 10:17:37. <Main> Rowset size: 10

I. 2014-05-29 10:17:37. <Main> Number of database worker threads: 5

I. 2014-05-29 10:17:37. <Main> Unknown users will be rejected (when there is no authenticate_user script)

I. 2014-05-29 10:17:39. <Main> ODBC DBMS Name: SQL Anywhere

I. 2014-05-29 10:17:39. <Main> ODBC DBMS Version: 16.00.0000

I. 2014-05-29 10:17:39. <Main> ODBC DBMS Driver Version: 16.00.1824

I. 2014-05-29 10:17:39. <Main> ODBC Version supported by the driver: 3.52

I. 2014-05-29 10:17:39. <Main> Collation sequence of the consolidated database is 'UTF-8'

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        select db_property( 'Capabilities' )

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        select db_property( 'Capabilities' )

I. 2014-05-29 10:17:39. <Main> ODBC DBMS Type: SQL Anywhere

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT @@spid

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        SELECT @@spid

I. 2014-05-29 10:17:39. <Main> Shared administrative connection with connection ID 'SPID 1' has been established

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        set temporary option chained = 'ON'

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        set temporary option chained = 'ON'

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        set temporary option st_geometry_asbinary_format = 'WKB( endian=little )'

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        set temporary option st_geometry_asbinary_format = 'WKB( endian=little )'

I. 2014-05-29 10:17:39. <Main> ODBC isolation set to: Read Committed

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT user_id, name, hashed_password, policy_id, user_dn FROM ml_user WHERE 1=2

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        SELECT user_id, name, hashed_password, policy_id, user_dn FROM ml_user WHERE 1=2

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT rid, remote_id, script_ldt, sync_key, description FROM ml_database WHERE 1=2

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        SELECT rid, remote_id, script_ldt, sync_key, description FROM ml_database WHERE 1=2

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT rid, subscription_id, user_id, progress, publication_name, last_upload_time, last_download_time FROM ml_subscription WHERE 1=2

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        SELECT rid, subscription_id, user_id, progress, publication_name, last_upload_time, last_download_time FROM ml_subscription WHERE 1=2

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT ldsrv_id, ldsrv_name, search_url, access_dn, access_dn_pwd, auth_url, num_retries, timeout, start_tls FROM ml_ldap_server WHERE 1=2

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        SELECT ldsrv_id, ldsrv_name, search_url, access_dn, access_dn_pwd, auth_url, num_retries, timeout, start_tls FROM ml_ldap_server WHERE 1=2

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT file_name FROM ml_trusted_certificates_file WHERE 1=2

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        SELECT file_name FROM ml_trusted_certificates_file WHERE 1=2

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT policy_id, policy_name, primary_ldsrv_id, secondary_ldsrv_id, ldap_auto_failback_period, ldap_failover_to_std FROM ml_user_auth_policy WHERE 1=2

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        SELECT policy_id, policy_name, primary_ldsrv_id, secondary_ldsrv_id, ldap_auto_failback_period, ldap_failover_to_std FROM ml_user_auth_policy WHERE 1=2

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT table_id, name FROM ml_table WHERE 1=2

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        SELECT table_id, name FROM ml_table WHERE 1=2

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT component_name, property_set_name, property_name, property_value FROM ml_property WHERE 1=2

I. 2014-05-29 10:17:39. <Main> Translated SQL:

                        SELECT component_name, property_set_name, property_name, property_value FROM ml_property WHERE 1=2

I. 2014-05-29 10:17:39. <Main> System event on shared administrative connection:

                        SELECT script_id, script, script_language FROM ml_script WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT script_id, script, script_language FROM ml_script WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT version_id, name, description FROM ml_script_version WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT version_id, name, description FROM ml_script_version WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT version_id, event, script_id FROM ml_connection_script WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT version_id, event, script_id FROM ml_connection_script WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT version_id, table_id, event, script_id FROM ml_table_script WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT version_id, table_id, event, script_id FROM ml_table_script WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT last_modified FROM ml_scripts_modified WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT last_modified FROM ml_scripts_modified WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT version_id, table_id, idx, name, type FROM ml_column WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT version_id, table_id, idx, name, type FROM ml_column WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT server_id, name, connection_info, instance_key, start_time FROM ml_primary_server WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT server_id, name, connection_info, instance_key, start_time FROM ml_primary_server WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT script_id, script_name, flags, affected_pubs, script, description FROM ml_passthrough_script WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT script_id, script_name, flags, affected_pubs, script, description FROM ml_passthrough_script WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT remote_id, run_order, script_id, last_modified FROM ml_passthrough WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT remote_id, run_order, script_id, last_modified FROM ml_passthrough WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT status_id, remote_id, run_order, script_id, script_status, error_code, error_text, remote_run_time FROM ml_passthrough_status WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT status_id, remote_id, run_order, script_id, script_status, error_code, error_text, remote_run_time FROM ml_passthrough_status WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT failed_script_id, error_code, new_script_id, action FROM ml_passthrough_repair WHERE 1=2

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT failed_script_id, error_code, new_script_id, action FROM ml_passthrough_repair WHERE 1=2

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT count(*) FROM ml_scripts_modified

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT count(*) FROM ml_scripts_modified

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT CONNECTION_PROPERTY( 'ALLOW_SNAPSHOT_ISOLATION' )

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT CONNECTION_PROPERTY( 'ALLOW_SNAPSHOT_ISOLATION' )

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT file_name FROM ml_trusted_certificates_file

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT file_name FROM ml_trusted_certificates_file

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT ldsrv_id, ldsrv_name, search_url, access_dn, access_dn_pwd, auth_url, timeout, num_retries, start_tls FROM ml_ldap_server order by 1

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT ldsrv_id, ldsrv_name, search_url, access_dn, access_dn_pwd, auth_url, timeout, num_retries, start_tls FROM ml_ldap_server order by 1

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        SELECT policy_id, policy_name, primary_ldsrv_id, secondary_ldsrv_id, ldap_auto_failback_period, ldap_failover_to_std FROM ml_user_auth_policy order by 1

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        SELECT policy_id, policy_name, primary_ldsrv_id, secondary_ldsrv_id, ldap_auto_failback_period, ldap_failover_to_std FROM ml_user_auth_policy order by 1

I. 2014-05-29 10:17:40. <Main> System event on shared administrative connection:

                        select cast(property_value as char(254)) from ml_property where component_name = 'MLS' AND property_set_name = 'locking_and_blocking_detection' AND property_name = 'blocking_threshold_in_seconds'

I. 2014-05-29 10:17:40. <Main> Translated SQL:

                        select cast(property_value as char(254)) from ml_property where component_name = 'MLS' AND property_set_name = 'locking_and_blocking_detection' AND property_name = 'blocking_threshold_in_seconds'

I. 2014-05-29 10:17:41. <Main> Loaded Assembly "iAnywhere.MobiLink.Script, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a53f0c6f719e2641" from "file:///C:/Program Files/SQL Anywhere 16/Assembly/v2/iAnywhere.MobiLink.Script.DLL" into Domain "DefaultDomain"

I. 2014-05-29 10:17:42. <Main> Loaded Assembly "iAnywhere.MobiLink, Version=16.0.0.1824, Culture=neutral, PublicKeyToken=a53f0c6f719e2641" from "file:///C:/Program Files/SQL Anywhere 16/Assembly/v2/iAnywhere.MobiLink.dll" into Domain "DefaultDomain"

I. 2014-05-29 10:17:42. <Main> Loaded Assembly "iAnywhere.MobiLink.Script, Version=1.0.0.0, Culture=neutral, PublicKeyToken=a53f0c6f719e2641" from "file:///C:/Program Files/SQL Anywhere 16/Assembly/v2/iAnywhere.MobiLink.Script.dll" into Domain "DefaultMobiLinkDNetScriptingDomain"

I. 2014-05-29 10:17:43. <Main> Loaded Assembly "iAnywhere.MobiLink, Version=16.0.0.1824, Culture=neutral, PublicKeyToken=a53f0c6f719e2641" from "file:///C:/Program Files/SQL Anywhere 16/Assembly/v2/iAnywhere.MobiLink.dll" into Domain "DefaultMobiLinkDNetScriptingDomain"

I. 2014-05-29 10:17:43. <Main> Loaded Assembly "SynchroServer, Version=10.3.0.0, Culture=neutral, PublicKeyToken=null" from "file:///D:/Projects/Inator3/PDASystem/PDA/SynchroServer/SynchroServer_10.3.0.0-SQLAnywhere16/bin/Debug/SynchroServer.DLL" into Domain "DefaultMobiLinkDNetScriptingDomain"

I. 2014-05-29 10:17:44. <Main> System event on locking/blocking detector connection:

                        SELECT @@spid

I. 2014-05-29 10:17:44. <Main> MobiLink server started

The server raises some errors:

I. 2014-05-29 11:16:56. <8> Request from "UL 16.0.1824" for: remote ID: 16494c50-e688-11e3-8000-883086e0189e, user name: *******, version: verNewTrip

E. 2014-05-29 11:16:57. <8> [-10060] Memory allocation failed

E. 2014-05-29 11:16:57. <8> [-10001] Protocol error: 400

E. 2014-05-29 11:16:57. <8> [-10410] The client failed to send a complete sequence of commands

I. 2014-05-29 11:16:57. <8> Synchronization failed

I. 2014-05-29 11:16:57. <8> PHASE: sync_request: 318

I. 2014-05-29 11:16:57. <8> PHASE: receive_upload: 433

I. 2014-05-29 11:16:57. <8> PHASE: get_db_worker: 0

I. 2014-05-29 11:16:57. <8> PHASE: connect: 0

I. 2014-05-29 11:16:57. <8> PHASE: authenticate_user: 0

I. 2014-05-29 11:16:57. <8> PHASE: begin_sync: 0

I. 2014-05-29 11:16:57. <8> PHASE: apply_upload: 0

I. 2014-05-29 11:16:57. <8> PHASE: prepare_for_download: 0

I. 2014-05-29 11:16:57. <8> PHASE: fetch_download: 0

I. 2014-05-29 11:16:57. <8> PHASE: end_sync: 0

I. 2014-05-29 11:16:57. <8> PHASE: send_download: 0

I. 2014-05-29 11:16:57. <8> PHASE: wait_for_download_ack: 0

I. 2014-05-29 11:16:57. <8> PHASE: get_db_worker_for_download_ack: 0

I. 2014-05-29 11:16:57. <8> PHASE: connect_for_download_ack: 0

I. 2014-05-29 11:16:57. <8> PHASE: nonblocking_download_ack: 0

E. 2014-05-29 11:16:57. <9> [-10117] Stream Error: Unable to continue unknown HTTP session

Has someone some help?

Thanks in advance.

There is a case wherein we embedded the Client Program written in Java Swings inside the DB and invoke the main class. The problem is that even if it is invoked from the client machine, the relevant forms and all open up in the server machine. We would like to know how the same can be invoke locally on the client machine, thereby creating the JVM locally on the client machine and loading the relevant forms on the client machine.