Data Replication
- Data Replication 9.8.0
- All Products
Exit Code
| Description
|
---|---|
0
| The replication task completed processing successfully.
|
30
| The replication task ended abnormally because of an SQLite repository error.
|
31
| The replication task could not connect to the source database.
|
32
| The replication task could not connect to the target database.
|
33
| InitialSync failed to use a Flashback query to unload data from the Oracle source.
|
34
| The replication task ended abnormally because of a database error.
|
35
| The replication task could not find the XML configuration file.
|
36
| The replication task could not find the XSD schema file.
|
37
| The replication task could not parse the XML configuration file because the file is corrupted.
|
38
| Internal error. The replication task could not process the transform.xsl file. Contact Informatica Global Customer Support.
|
39
| The replication task did not process change data from a column because the column datatype is not supported. Edit the replication configuration to unmap the column with the unsupported datatype.
|
40
| The replication task could not build the ODBC connection string.
|
41
| InitialSync did not resynchronize tables because no tables were selected for resynchronization.
|
42
| The Extractor task could not process WHERE conditions for source columns.
|
43
| The replication task could not parse an intermediate file. The intermediate file might be corrupted.
|
44
| Internal error. A memory allocation error occurred. Contact Informatica Global Customer Support.
|
45
| An I/O operation failed.
|
47
| The replication task was started with command line arguments that were not valid. For more information about the command line arguments that the replication task supports, see
Command Line Parameters for Data Replication Components.
|
49
| An operating system error occurred.
|
50
| The replication task ended abnormally because of an error in the SQLite configuration repository.
|
51
| Internal error. Cannot save the XML configuration file. Contact Informatica Global Customer Support.
|
52
| The replication task expected data with a different endianness.
|
53
| The Applier did not apply change data to the target tables because these tables were not initially synchronized with the source tables. Run InitialSync before you start change data replication the first time.
|
54
| A replication task ended abnormally because of insufficient disk space on the Data Replication system. Ensure that the system has enough free disk space and then restart the replication task.
|
55
| InitialSync ended because the db2.initial_lsn runtime parameter does not specify an initial LSN value. For DB2 sources, unless you override the default LSN value, you must run the Extractor before InitialSync to record an initial LSN in the db2.initial_lsn parameter. The first time you run the Extractor after InitialSync completes, the Extractor begins extracting changes from this LSN.
|
56
| The database user that Data Replication uses to connect to the source or target database has insufficient privileges. Grant the required privileges to the database user. For more information, see
Preparing Source and Target Systems.
|
57
| InitialSync cannot synchronize source tables with target tables that are not empty. Truncate the mapped target tables and run InitialSync again.
|