laptop and a wrench

不具合

Synchronizing the one-way parent-to-child replica generates null values.

最後に公開された状態: June 11, 2021 ArcSDE/Enterprise Geodatabase
不具合 ID 番号 BUG-000137415
送信されましたFebruary 11, 2021
最終更新日June 5, 2024
適用対象ArcSDE/Enterprise Geodatabase
見つかったバージョン10.7.1
オペレーティング システムWindows OS
オペレーティング システムのバージョンN/A
ステータスWill Not Be Addressed

参考情報

The behavior comes down to a data modeling problem. The problem is there are "chained" relationships based on the same field being both foreign and primary keys. Although the geodatabase may allow certain edits to these types of relationships, geodatabase replication is more strict. Where there is a dangling foreign key, nullify it. One reason for this is to avoid the dangling records being inadvertently related to a different record if at a later point in time an original record is created with that key value. The recommendation is for "chained" relationships to be based on different key fields for each relationship class (do not have the same field used for all the relationships). If the relationships cannot be changed accordingly, then update the data to ensure values for all the related records in the chain before the sync. The particular feature class, in this case, had 7 relationships – 5 with origin keys and 2 with foreign keys (one foreign key based in the field being edited and the other was based on another field – the latter is the recommended way to establish these relationships).

対処法

Unregistering the relationship class (Strc_CFR_DSSPinsToCRPins) where DepProjNo is the foreign key from the replica resolves the issue.

再現の手順

不具合 ID: BUG-000137415

ソフトウェア:

  • ArcSDE/Enterprise Geodatabase

バグのステータスが変更されたときに通知を受け取る

Esri Support アプリのダウンロード

このトピックについてさらに調べる

ArcGIS エキスパートのサポートを受ける

テクニカル サポートへのお問い合わせ

Esri Support アプリのダウンロード

ダウンロード オプションに移動