We are running the OEM version of ASA 9.0.2.2451. We have run into an
issue running another vendor's software (Pervasive Data Integrator)
where the connection loses its authentication for no apparent reason.
The logs do not show a disconnect and reconnect, just a sudden failure
on an insert (not always the same one) with an authentication
violation. We are connecting to the database via an ODBC connection
using Shared Memory. The first thing we do is create the connection
and set the temporary option CONNECTION_AUTHENTICATION. Then it runs
through a series of inserts and updates. Occasionally we can process
our entire file (an XML file that we have mapped to insert data into
the database) with no problems. But most of the time it will get part
way through processing the file and throw the Authentication
Violation.

Any ideas what would cause this to happen?

Thanks!

-Heather

The enforcement of the authentication starts after 30seconds. How long
into the application does it encounter the problem?

If the timing is off, please capture a request level log (SQL) i.e.,
dbeng9 -zr sql -zo requests.log. This might help to isolate what is
happening. Specifically, look for errors during calls that involve
authentication.

-chris


Heather T. wrote:

Ok, that's the problem. I studied the logs and discovered that
contrary to what they told me their software was doing, it is in fact
applying the authentication and then disconnecting. Thus when it
reconnects to do all of the processing, it is dying at 30 seconds due
to the enforcement of the authentication.

Thank you!


On Jan 15, 2:29*pm, "Chris Keating (Sybase iAnywhere)"
<keating_nos... (AT) sybase (DOT) com> wrote:

Is there any way to temporarily change that length of 30 seconds to
extend it a bit, allow our processing to complete (which takes less
than a minute), then change the length back to 30 seconds?

-Heather

On Jan 15, 2:29*pm, "Chris Keating (Sybase iAnywhere)"
<keating_nos... (AT) sybase (DOT) com> wrote:

This is not configurable option.

The OEM (AKA Authenticated) edition of SQL Anywhere is licensed for
unrestricted access *only* from the application (in this case, Pervasive
Data Integrator) that provides that edition. End-users of such
applications are not licensed to use the software in ways that violate
those restrictions. For most OEM deployments, this means that end-user
customers are only permitted 'read-only' access to the database i.e., no
actions that modify the database including but not limited to inserts
and updates. Subject to the licensing of the Pervasive software,
unrestricted access to the database would require additional SQL
Anywhere licensing.

-chris


Heather T. wrote:

Okay, that's what I figured. Thank you!

-Heather

On Jan 18, 1:37*pm, "Chris Keating (Sybase iAnywhere)"
<keating_nos... (AT) sybase (DOT) com> wrote: