Problems and Solutions

Important: Check your db_merge.log file for error, after running a datamerge. In the table below, you will find some solutions to common problems..

Following are some common problems that you can encounter while using DataMerge; the symptoms that alert you to them and solutions that you can use to correct them

Problem

Not Running the DataMerge from Command Prompt window created by Workbench

Symptoms

WARNING:Unable to translate SITE_ROOT.dlrp_init_merge

Fri Apr 10 13:25:47 1998 failure 189 <No Prname> dlrp_init_table 93

Error 2 from fio file data_field: No such file or directory

Error of type COR_SC_ERR:source 130 code 2 COR_logstatus FATAL error resulting in exit

Solution

Do the following:

  1. Open the project's Workbench.

  2. Click Tools on the menu bar.

  3. Select Command prompt…

Type datamerge.exe in the Command Prompt window.

Problem

Starting the Datamerge without running the project.

Symptoms

…CIpcPortShm::Register

m_ConnOut.Attach Err:2

Solution

Do the following:

  1. Start the project.

  2. Open the project's Workbench.

  3. Click Tools on the menu bar.

  4. Select Command prompt…

Type datamerge.exe in the Command Prompt window.

Problem

Using CIMPLICITY Point Logging (datasource) or CIMPLICITY Alarm Logging for the secondary (slave) server, without proper mapping on the primary (master) server.

Symptoms

Entry in the db_merge.log stating that there is no data to be merged. This in itself does not indicate an error. However, if you know you have data to merge, it might be one.

Solution

Rename the data sources in the ODBC Data Source Administrator window.

Problem

Using data source with the same names on the primary and secondary servers that are pointing to different databases.

Symptoms

Entry in the db_merge.log stating that there is no data to be merged. This in itself does not indicate an error. However, if you know you have data to merge, it might be one.

Solution

Rename the data sources in the ODBC Data Source Administrator window.

Problem

Rerunning the DataMerge.

Symptoms

No ptlr[date].log file found.

Solution

Rename the last modified file ptlr[date].sav to ptlr[date].log.

Problem

Rerunning the DataMerge for data that has already been processed.

Symptoms

Error message telling you that insertion violates the primary key.

Solution

The data has already been merged.

More information

About server redundancy.