Managing replications
Introduction
DCT 9.0.0 introduces the feature to differentiate between the replicated objects and original objects in case of a parent and replicated engines, both are registered with DCT.
Prerequisites
One parent and one replicated engine is required with few replicated dSources and VDBs.
User interface
-
Convenient separation between the replicated objects(VDB/dSource/environments) and original objects.
-
Users can filter the replicated object using the advanced filter.
-
All the actions on the replicated objects are disabled.
-
The status of the replicated objects are N/A.
-
On the VDB provisioning wizard, replicated objects(VDB/dSources) are marked as replicated.
API
Expand the section below to show search APIs that are updated to return three additional fields: is_replica
, namespace_id
, and namespace_name
. These fields are described below.
-
is_replica
: Boolean telling that this object id replicated or not. -
namespace_id
: This field will only come for replicated objects and is essentially thenamespace id
of the replicated object. -
namespace_name
: This field will only come for replicated objects and is essentially thenamespace name
of the replicated object.