Skip to main content
Announcements
July 15, NEW Customer Portal: Initial launch will improve how you submit Support Cases. READ MORE

Qlik Replicate Task fails after DB2 LUW Upgrade: Unexpected Error Original SQLCODE -1263: ' message SQL1263N

100% helpful (1/1)
cancel
Showing results for 
Search instead for 
Did you mean: 
Bill_Steinagle
Support
Support

Qlik Replicate Task fails after DB2 LUW Upgrade: Unexpected Error Original SQLCODE -1263: ' message SQL1263N

Last Update:

Jul 31, 2024 10:17:58 AM

Updated By:

Sonja_Bauernfeind

Created date:

Jul 31, 2024 10:17:58 AM

After a DB2 LUW Upgrade, Qlik Replicate tasks fail with:

"ReadNextBufferWait: Error reading buffer Error at 'Reading log records': Unexpected Error. Original SQLCODE -1263: ' message SQL1263N The archive log file "S0673464.LOG" is not a valid log file for database "REP" on database partition "0" and log stream "0". 

Environment:

  • Qlik Replicate
  • DB2 LUW Endpoint

Resolution

Reload the task using the DB2 LUW Endpoint.

Cause

Qlik Replicate saves the last save stream position when a task is stopped.

Since the DB2 LUW environment was upgraded, the transaction log will be different and the task (tables) need to be reloaded.

An SQL Lite file called DB2LUW_TIMESTAMP_MAP is defined in the tasks directory, which stores the LSN/LRI position with the timestamp for the given task. This file includes the old DB2 LUW transaction log which is pointing to the old DB2 transaction log version.

Labels (1)
Version history
Last update:
7 hours ago
Updated by: