TitleEngTAG 


<HTML><H3>Import Error Codes</H3></HTML>

During the incoming data handling it is possible that a data error is detected: this could be due to a different database schema (tables or fields not existing) or to a different data status. 

When such an error is detected, it is impossible to complete the import: the transaction is aborted with a rollback, and copy of incoming data is inserted into [Data Distrib. Import Error] table; the detected error is shown in the field [Handling Error Code].

Possible Error Codes are:

  * **D-EVENTERR ** DELETE: an error has been raised during OnBeforeSpkDeleteRecord Event handling
  * **D-NOREC** DELETE: a record with given primary key not exists
  * **D-NOTBL** DELETE: the destination table not exists into the database
  * **D-TBLDND**    DELETE: the destination table cannot be modified
  * **I-DUPL ** INSERT: a record with given primary key already exists 
  * **I-EVENTERR ** INSERT: an error has been raised during OnBeforeSpkInsertRecord Event handling
  * **I-FLDNACTV**  INSERT: the destination field is not active
  * **I-FLDUNKNW** INSERT: the destination field not exists into the destination table
  * **I-NOTBL** INSERT: the destination table not exists into the database
  * **I-TBLDND**    INSERT: the destination table cannot be modified
  * **M-EVENTERR ** MODIFY: an error has been raised during OnBeforeSpkModifyRecord Event handling
  * **M-FLDNACTV**  MODIFY: the destination field is not active
  * **M-FLDUNKNW**  MODIFY: the destination field not exists into the destination table
  * **M-NOREC** MODIFY: a record with given primary key not exists
  * **M-NOTBL**     MODIFY: the destination table not exists into the database 
  * **M-TBLDND**    MODIFY: the destination table cannot be modified
  * **R-EVENTERR ** RENAME: an error has been raised during OnBeforeSpkRenameRecord Event handling
  * **R-EXISTS** RENAME: a record with given renamed primary key already exists 
  * **R-NOREC** RENAME: a record with given primary key to be renamed not exists
  * **R-TBLDND**    RENAME: the destination table cannot be modified
  * **R-UNKNW** RENAME: the rename transaction raised an unhandled error.\\ As usual, this error is shown when raised by the OnRename trigger called into the remote database. 
  * **T-FLDNACTV**  REPLICATE: the destination field is not active
  * **T-FLDUNKNW**  REPLICATE: the destination field not exists into the destination table 
  * **T-NOTBL**     REPLICATE: the destination table not exists into the database
  * **T-TBLDND**    REPLICATE: the destination table cannot be modified
  * **X-DST**       (ALL): Target Peer is unknown
  * **X-SRCOFF**    (ALL): Import is disabled for the Source Peer 
  * **X-SRCUNKNW**  (ALL): Source Peer is unknown