JR34950: ODBC CONNECTOR LOGS SOME OF THE FATAL ERRORS AS WARNINGS AND DO NOT ABORT THE JOB

Download Fix Pack 2 for InfoSphere Information Server Version 8.1

APAR status

• Closed as program error.

Error description

• ODBC Connector logs some of  the fatal errors as warnings and
  does not abort the job when executing in dual query mode.
  (insert then update etc ....).
  

Local fix

Problem summary

• ****************************************************************
  USERS AFFECTED:
  Users using ODBC Connector and running against SQL Server.
  ****************************************************************
  PROBLEM DESCRIPTION:
  When the user is running ODBCCC with WriteMode 'Insert then
  Update' and when the
  Transaction Log in the database becomes full, the job is
  reported to be completed successfully.
  However, when we check the table contents, it is observed that
  all the records are not processed successfully.
  
  While we execute the dual query, we would ignore the errors
  returned in the first query with an assumption that the records
  will be processed successfully when we execute the first query
  or we will get the same error while executing the second query.
  However, when the transaction log is filled up, the insert
  statement gets the error and we will ignore that and when
  executing the update statement, we are getting no data to
  update and we rarely get the transaction log full error
  depending on other factors such as the number of records to be
  updated, transaction size etc.
  Because of this, the results of the job run will not be
  consistent and they will be incorrect.
  
  Note : Please note that this issue will not happen consistently
  when
  1. Number of records are less.
  2. Lower value of record count is used. (like for example 10)
  3. When the Autocommit mode is set to Yes.
  ****************************************************************
  RECOMMENDATION:
  Apply the following APAR.
  ****************************************************************
  

Problem conclusion

• Currently handling transaction log failure in the first
  statement of 'insert then update' mode.
  

Temporary fix

Comments

APAR Information

• APAR is sysrouted FROM one or more of the following:

• APAR is sysrouted TO one or more of the following:

Fix information

• Fixed component name

  WIS DATASTAGE

• Fixed component ID

  5724Q36DS

Applicable component levels

• R810 PSN

     UP