Skip to content

DOC-4384 removed spurious info on RDI Oracle prep page #787

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 3 commits into from
Oct 21, 2024
Merged

DOC-4384 removed spurious info on RDI Oracle prep page #787

Changes from all commits
Commits
Show all changes
3 commits
Select commit Hold shift + click to select a range
f17c3c4
DOC-4384 removed spurious info on RDI Oracle prep page
andy-stark-redis Oct 21, 2024
765fbfd
Revert "DOC-4384 removed spurious info on RDI Oracle prep page"
andy-stark-redis Oct 21, 2024
97363d5
DOC-4384 fix previous incorrect change
andy-stark-redis Oct 21, 2024
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
12 changes: 7 additions & 5 deletions content/integrate/redis-data-integration/data-pipelines/prepare-dbs/oracle.md
View file
Open in desktop
Original file line number Diff line number Diff line change
Expand Up @@ -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.
Expand All @@ -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
Expand All @@ -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
Expand Down Expand Up @@ -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
Expand Down Expand Up @@ -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.
Loading