@@ -216,7 +216,7 @@ you might want to prevent the Debezium user from creating tables, or
216
216
selecting or locking any table.
217
217
218
218
The Debezium user needs the ` CREATE TABLE ` privilege to create the
219
- ` LOG_MINING_FLUSH ` and ` signals ` tables when it connects for the first
219
+ ` LOG_MINING_FLUSH ` table when it connects for the first
220
220
time. After this point, it doesn't need to create any more tables,
221
221
so you can safely revoke this privilege with the following command:
222
222
@@ -225,8 +225,8 @@ REVOKE CREATE TABLE FROM c##dbzuser container=all;
225
225
```
226
226
227
227
[ The example above] ( #create-dbz-user ) grants the ` SELECT ANY TABLE ` and
228
- ` FLASHBACK ANY TABLE ` privileges for convenience, but only the tables synced to RDI,
229
- the ` signals ` table, and the ` V_$XXX ` tables strictly need these privileges.
228
+ ` FLASHBACK ANY TABLE ` privileges for convenience, but only the tables synced to RDI
229
+ and the ` V_$XXX ` tables strictly need these privileges.
230
230
You can replace the ` GRANT SELECT ANY TABLE ` command with explicit
231
231
commands for each table. For example, you would use commands like the
232
232
following for the tables in our sample
@@ -235,7 +235,6 @@ database. (Note that Oracle 19c requires you to run a separate `GRANT`
235
235
command for each table individually.)
236
236
237
237
``` sql
238
- GRANT SELECT ON signals TO c# #dbzuser;
239
238
GRANT SELECT ON chinook .album TO c# #dbzuser;
240
239
GRANT SELECT ON chinook .artist TO c# #dbzuser;
241
240
GRANT SELECT ON chinook .customer TO c# #dbzuser;
@@ -246,7 +245,6 @@ Similarly, instead of `GRANT FLASHBACK ANY TABLE`, you would use the following
246
245
commands:
247
246
248
247
``` sql
249
- GRANT FLASHBACK ON signals TO c# #dbzuser;
250
248
GRANT FLASHBACK ON chinook .album TO c# #dbzuser;
251
249
GRANT FLASHBACK ON chinook .artist TO c# #dbzuser;
252
250
GRANT FLASHBACK ON chinook .customer TO c# #dbzuser;
0 commit comments