Skip to content

Corrected query syntax/description #1848

New issue

Have a question about this project? Sign up for a free GitHub account to open an issue and contact its maintainers and the community.

Sign up for GitHub

By clicking “Sign up for GitHub”, you agree to our terms of service and privacy statement. We’ll occasionally send you account related emails.

Already on GitHub? Sign in to your account

Merged
merged 2 commits into from
Apr 23, 2025
Merged

Corrected query syntax/description #1848

Changes from all commits
Commits
Show all changes
2 commits
Select commit Hold shift + click to select a range
718ac05
Corrected query syntax/description
finnigd Apr 9, 2025
0142a06
Update sql-transaction-log-grows.md
sevend2 Apr 23, 2025
File filter

Filter by extension

Filter by extension
Conversations
Failed to load comments.
Loading
Jump to
Jump to file
Failed to load files.
Loading
Diff view
Diff view
6 changes: 3 additions & 3 deletions support/sql/database-engine/replication/sql-transaction-log-grows.md
View file
Open in desktop
Original file line number Diff line number Diff line change
@@ -1,7 +1,7 @@
---
title: SQL Transaction log grows continuously
description: This article helps you resolve the problem where you notice continuous transaction log growth for a CDC enabled database.
ms.date: 03/16/2020
ms.date: 04/23/2025
ms.custom: sap:Replication, Change Tracking, Change Data Capture, Synapse Link
---
# SQL Transaction log grows when you use Change Data Capture for Oracle by Attunity
Expand Down Expand Up @@ -37,10 +37,10 @@ DBCC execution completed. If DBCC printed error messages, contact your system ad

You may have a non-distributed LSN because CDC for Oracle uses CDC for SQL stored procedures, and that, in turn, uses the replication log reader. This non-distributed LSN corresponds to the log entries to add the mirrored table in the Attunity CDC database.

If you run this query, the `log_reuse_wait_desc` option returns a value of `REPLICATION`, indicating the cause. Select the `log_reuse_wait_desc` name from `sys.databases`, where the name is \<your_cdc_database\>:
If you run this query, the `log_reuse_wait_desc` option returns a value of `REPLICATION`, indicating the cause.

```sql
REPLICATION <your_cdc_database>
SELECT log_reuse_wait_desc FROM sys.databases WHERE name = '<your_cdc_database>'
```

## Resolution
Expand Down