forked from docs/doc-exports
Hasko, Vladimir
a5cc543164
Reviewed-by: Wagner, Fabian <fabian.wagner@t-systems.com> Co-authored-by: Hasko, Vladimir <vladimir.hasko@t-systems.com> Co-committed-by: Hasko, Vladimir <vladimir.hasko@t-systems.com>
17 lines
1.5 KiB
HTML
17 lines
1.5 KiB
HTML
<a name="ddm_03_0059"></a><a name="ddm_03_0059"></a>
|
|
|
|
<h1 class="topictitle1">Reloading Table Data</h1>
|
|
<div id="body0000001195829630"><div class="section" id="ddm_03_0059__section1539512419299"><h4 class="sectiontitle">Prerequisites</h4><p id="ddm_03_0059__p2085114424292">You have logged in to the DDM console.</p>
|
|
</div>
|
|
<div class="section" id="ddm_03_0059__section434353910262"><h4 class="sectiontitle">Scenarios</h4><p id="ddm_03_0059__p1480711521513">If you want to deploy a DDM instance across regions for DR, use DRS to migrate service data and then reload table data after the migration is complete so that DDM can detect where logical table information is stored.</p>
|
|
</div>
|
|
<div class="section" id="ddm_03_0059__section7811958132013"><h4 class="sectiontitle">Procedure</h4><ol id="ddm_03_0059__ol149322218210"><li id="ddm_03_0059__li136621522122815"><span>Choose <strong id="ddm_03_0059__b1646133613526">Instances</strong> on the left navigation pane, in the instance list, locate the instance whose information is changed and click the instance name.</span></li><li id="ddm_03_0059__li1749316221218"><span>Choose <strong id="ddm_03_0059__b7969143914527">More</strong> > <strong id="ddm_03_0059__b20970439155210">Reload Table Data</strong> in the <strong id="ddm_03_0059__b179701039115218">Operation</strong> column.</span></li></ol>
|
|
</div>
|
|
</div>
|
|
<div>
|
|
<div class="familylinks">
|
|
<div class="parentlink"><strong>Parent topic:</strong> <a href="ddm_10_1000.html">Data Node Management</a></div>
|
|
</div>
|
|
</div>
|
|
|