Do not input private or sensitive data. View Qlik Privacy & Cookie Policy.
Skip to main content

Announcements
ALERT: The support homepage carousel is not displaying. We are working toward a resolution.

Qlik Replicate: SQL Server running out of space due to the replication

No ratings
cancel
Showing results for 
Search instead for 
Did you mean: 
lyka
Support
Support

Qlik Replicate: SQL Server running out of space due to the replication

Last Update:

Mar 14, 2022 11:07:31 AM

Updated By:

Sonja_Bauernfeind

Created date:

Mar 3, 2022 7:53:07 PM

Sample Error:

Line 691: 00012316: 2022-03-03T16:11:14 [SOURCE_CAPTURE ]E: RetCode: SQL_ERROR SqlState: 42000 NativeError: 9002 Message: [Microsoft][SQL Server Native Client 11.0][SQL Server]The transaction log for database 'TEST' is full due to 'REPLICATION'. Line: 1 Column: -1 [1022502] (ar_odbc_stmt.c:4895)

If the log reader job is running without error and the oldest transaction is moving forward then the log should be getting truncated when the backup runs. If it is not then there is something else causing the log to be locked up.

If the log reader job is having issues and the log needs to be cleared up, the following manual 'emergency' procedure can be used so that Replicate will not miss any changes:

  1. Stop the Log Reader SQL server agent job.
  2. Run sp_repldone to mark everything as replicated: exec sp_repldone @xactid = NULL, @xact_seqno = NULL, @numtrans = 0, @time = 0, @reset = 1;
  3. Execute a transaction log backup.

Environment:

Qlik Replicate 

Labels (1)
Version history
Last update:
‎2022-03-14 11:07 AM
Updated by: