My Oracle Support Banner

After a The Source Table is Dropped the Associated Table is not Being Dropped in BDR (Doc ID 2213274.1)

Last updated on APRIL 08, 2020

Applies to:

Big Data Appliance Integrated Software - Version 4.5.0 and later
Linux x86-64

Goal

NOTE: In the examples that follow, user details, cluster names, hostnames, directory paths, filenames, etc. represent a fictitious sample (and are used to provide an illustrative example only). Any similarity to actual persons, or entities, living or dead, is purely coincidental and not intended in any manner. 

Why are tables that are dropped in the source cluster not being dropped in BDR.

Drop Table Example:
1. Source Cluster: create default.table t1 (c1 int);
2. Destination Cluster: replication (database=default, table_regex=[\w_]+)
2.1. Result: Table default.t1 is replicated
3. Source Cluster: create table default.t2 (c1 int);
4. Destination Cluster: replication (database=default, table_regex=[\w_]+)
4.1. Result: Table default.t1 and default.t2 are replicated
5. Source Cluster: drop table default.t2
6. Destination Cluster: replication (database=default, table_regex=[\w_]+)
6.1. Result: Table default.t1 is replicated and default.t2 is not dropped
 

Solution

To view full details, sign in with your My Oracle Support account.

Don't have a My Oracle Support account? Click to get started!


In this Document
Goal
Solution


My Oracle Support provides customers with access to over a million knowledge articles and a vibrant support community of peers and Oracle experts.