PQ65714: AFTER A BAD SQL, SEQUELINK SERVER FAILS IN THE NEXT TRANSACTION.

APAR status
Closed as Vendor Solution.

Error description
A connection cannot be used in a transaction if a "bad"  SQL
statement was executed in the previous transaction involving
DataDirect (formerly Merant) SequeLink Server.
.
The error message from SequeLink server for the first bad SQL
statement was:
.
  [MERANT][SequeLink JDBC Driver][SQL Server]Syntax error
  converting the varchar value '2202MAY123' to a column of data
  type int.
.
The statement and connection were closed properly, and a
"good" SQL statement was tried again in a new transaction with a
new connection, SequeLink threw the following error:
.
  [MERANT][SequeLink JDBC Driver][SQL Server]Distributed
  transaction completed. Either enlist this session in a new
  transaction or the NULL transaction.
Local fix
The same scenario works correctly when either the DataDirect
ConnectJDBC driver is used or the MicroSoft JDBC driver is used,
instead of the SequeLink driver.
Problem summary Problem conclusion Temporary fix Comments
This is being addressed by Merant, case 15002202 was opened.
Merant claims the problem is fixed with SequeLink 5.3.
APAR information
APAR number PQ65714
Reported component name WEBSPHERE AE NT
Reported component ID 5630A2201
Reported release 400
Status CLOSED ISV
PE NoPE
HIPER NoHIPER
Submitted date 2002-08-29
Closed date 2002-10-01
Last modified date 2002-10-01

APAR is sysrouted FROM one or more of the following:

APAR is sysrouted TO one or more of the following:

Modules/Macros

Fix information

Applicable component levels


Document Information


Product categories: Software > Application Servers > Distributed Application & Web Servers > WebSphere Application Server > General
Operating system(s):
Software version: 400
Software edition:
Reference #: PQ65714
IBM Group: Software Group
Modified date: Oct 1, 2002