From f17c3c409e610d1200cb3aea1b2962d5481884cd Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Mon, 21 Oct 2024 09:41:40 +0100 Subject: [PATCH 1/3] DOC-4384 removed spurious info on RDI Oracle prep page --- .../data-pipelines/prepare-dbs/oracle.md | 22 ------------------- 1 file changed, 22 deletions(-) diff --git a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md index a4644d9fb0..817203ae53 100644 --- a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md +++ b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md @@ -78,28 +78,6 @@ exec rdsadmin.rdsadmin_util.set_configuration('archivelog retention hours',24); exec rdsadmin.rdsadmin_util.alter_supplemental_logging('ADD'); ``` -You must enable supplemental logging for the tables you want to capture or -for the entire database. This lets Debezium capture the state of -database rows before and after changes occur. - -The following example shows how to configure supplemental logging for all columns -in a single table called `inventory.customers`: - -```sql -ALTER TABLE inventory.customers ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS; -``` - -{{< note >}}If you enable supplemental logging for *all* table columns, you will -probably see the size of the Oracle redo logs increase dramatically. Avoid this -by using supplemental logging only when you need it. {{< /note >}} - -You must also enable minimal supplemental logging at the database level with -the following command: - -```sql -ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; -``` - ## 2. Check the redo log sizing Before you use the Debezium connector, you should check with your From 765fbfd0fdb07e7090df7f7a0e770dc70ab3e8fe Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Mon, 21 Oct 2024 10:44:06 +0100 Subject: [PATCH 2/3] Revert "DOC-4384 removed spurious info on RDI Oracle prep page" This reverts commit f17c3c409e610d1200cb3aea1b2962d5481884cd. --- .../data-pipelines/prepare-dbs/oracle.md | 22 +++++++++++++++++++ 1 file changed, 22 insertions(+) diff --git a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md index 817203ae53..a4644d9fb0 100644 --- a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md +++ b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md @@ -78,6 +78,28 @@ exec rdsadmin.rdsadmin_util.set_configuration('archivelog retention hours',24); exec rdsadmin.rdsadmin_util.alter_supplemental_logging('ADD'); ``` +You must enable supplemental logging for the tables you want to capture or +for the entire database. This lets Debezium capture the state of +database rows before and after changes occur. + +The following example shows how to configure supplemental logging for all columns +in a single table called `inventory.customers`: + +```sql +ALTER TABLE inventory.customers ADD SUPPLEMENTAL LOG DATA (ALL) COLUMNS; +``` + +{{< note >}}If you enable supplemental logging for *all* table columns, you will +probably see the size of the Oracle redo logs increase dramatically. Avoid this +by using supplemental logging only when you need it. {{< /note >}} + +You must also enable minimal supplemental logging at the database level with +the following command: + +```sql +ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; +``` + ## 2. Check the redo log sizing Before you use the Debezium connector, you should check with your From 97363d5295a8fd4cdca0d2d5bd79269680c3ccf0 Mon Sep 17 00:00:00 2001 From: Andy Stark Date: Mon, 21 Oct 2024 10:47:37 +0100 Subject: [PATCH 3/3] DOC-4384 fix previous incorrect change --- .../data-pipelines/prepare-dbs/oracle.md | 12 +++++++----- 1 file changed, 7 insertions(+), 5 deletions(-) diff --git a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md index a4644d9fb0..03a1c9c85d 100644 --- a/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md +++ b/content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md @@ -71,13 +71,15 @@ should reboot your Oracle AWS RDS instance. Once `LOG_MODE` is correctly set to ARCHIVELOG, execute the following commands to complete the LogMiner configuration. The first command enables -archive logging and the second adds supplemental logging. +archive logging and the second adds [supplemental logging](#supp-logging). ```sql exec rdsadmin.rdsadmin_util.set_configuration('archivelog retention hours',24); exec rdsadmin.rdsadmin_util.alter_supplemental_logging('ADD'); ``` +## 2. Enable supplemental logging {#supp-logging} + You must enable supplemental logging for the tables you want to capture or for the entire database. This lets Debezium capture the state of database rows before and after changes occur. @@ -100,7 +102,7 @@ the following command: ALTER DATABASE ADD SUPPLEMENTAL LOG DATA; ``` -## 2. Check the redo log sizing +## 3. Check the redo log sizing Before you use the Debezium connector, you should check with your database administrator that there are enough @@ -110,7 +112,7 @@ of tables and columns in the database. If you don't have enough capacity in the logs then you might see performance problems with both the database and the Debezium connector. -## 3. Set the Archive log destination +## 4. Set the Archive log destination You can configure up to 31 different destinations for archive logs (you must have administrator privileges to do this). You can set parameters for @@ -140,7 +142,7 @@ use the following setting: } ``` -## 4. Create a user for the connector +## 5. Create a user for the connector The Debezium Oracle connector must run as an Oracle LogMiner user with specific permissions. The following example shows some SQL that creates @@ -197,7 +199,7 @@ GRANT SELECT ON V_$STATNAME TO c##dbzuser CONTAINER=ALL; exit; ``` -## 5. Configuration is complete +## 6. Configuration is complete Once you have followed the steps above, your Oracle database is ready for Debezium to use.