Error management and performance monitoring

When Integration Composer runs mappings, it provides information about mapping executions, data transactions, and errors in log files.

Log files can be found in the location InstallDir/log.

By default, the mxe.fusion.mapping.showRecordCounts property in the fusion.properties file is set to true, and the fusion.log file shows record counts for records created, updated, and deleted.

The log file also shows information about events related to the Naming and Reconciliation Service (NRS) process. This file includes information about actions taken when duplicate deployed assets are found and Naming and Reconciliation Service record counts.

Mapping execution completed
Mapping: cent2007
Execution time: 00:02:45
Deployed Assets created: 211
Records created: 8356
Records updated: 0
Records deleted: 0
Errors: 0

NRS GUIDs created: 210
NRS records updated on Alternate Keys: 0
NRS records found as duplicate: 0
NRS records deleted because of duplicate: 0

Naming and Reconciliation Service logs

There is a Naming and Reconciliation Service-specific log file, dis%u.consolidate, that provides information about the Naming and Reconciliation Service process. Both log and trace information are recorded in this log file. The log file is saved in the location InstallDir\log\dis%u.consolidate.

When the log file is written, the %u characters are replaced with a number that identifies the log file.

Database mapping information

You can view information about mapping executions in the TLOAMFSNRUNSTATUS table in the Integration Composer repository in the Maximo® database. This table maintains the following information about mapping runs:

Mapping name.
Source and target schema.
Source and target data source.
Start and end time for the mapping.
Number of records inserted, updated, deleted.
Whether the mapping failed or not.
Number of errors

This information is updated when mapping execution is completed. There is one record per mapping name. You cannot view this information in the user interface. You must use a query tool to view information in the database.

Database errors

The errors that cause Integration Composer to stop processing data are described as follows.

DB2® Database Errors

When processing data from a DB2 database, Integration Composer stops processing and shows an error message when one of the following events occurs:

The package corresponding to an SQL statement execution request is not found (binding). For example, SQLCODE: -805m SQLSTATE: 51002, SQLERRMC: NULLID.SYSLH204
Virtual storage or adequate database resource is unavailable (table space). For example, SQLCODE: -289, SQLSTATE: 57011, SQLERRMC: MAXDATA.

When these errors are encountered, mapping execution stops and the following message is shown: Error Message: Stop on FATAL error. The problem is resolved by a system or database administrator.

Oracle Database Errors: When processing data from an Oracle database, Integration Composer stops processing if any of the errors in the following table occur. Error 01632 applies to indexes, and errors 01651 through 01667 apply to table space errors.

Table 1. Oracle database error messages
Message Number	Message Description
ORA-01632	Maximum number of extents (name) was reached in index name.
ORA-01651	Unable to extend save undo segment by string for table space string.
ORA-01652	Unable to extend temp segment by string in table space string.
ORA-01653	Unable to extend table string.string by string in table space string.
ORA-01654	Unable to extend index string.string by string in table space string.
ORA-01655	Unable to extend cluster string.string by string in table space string.
ORA-01656	Maximum number of extents (string) reached in cluster string.string.
ORA-01657	Invalid SHRINK option value.
ORA-01658	Unable to create INITIAL extent for segment in table space string.
ORA-01659	Unable to allocate MINEXTENTS beyond string in table space string.
ORA-01660	Table space string is already permanent.
ORA-01661	Table space string is already temporary.
ORA-01662	Table space string is not empty and cannot be made temporary.
ORA-01663	The contents of table space string is constantly changing.
ORA-01664	Transaction which has expanded the Sort Segment has aborted.
ORA-01665	Control file is not a standby control file.
ORA-01666	Control file is for a standby database.
ORA-01667	Cannot add any more table spaces: limit of string exceeded.

Performance monitoring

You can use the PerfMon performance monitoring tool to analyze performance and isolate problems in processing. To activate this tool, uncomment the perfmon.logfrequency property in the fusion.properties file.

After you activate this property, a log file is created when you run a mapping. The default location for the log file is in the log directory. This log file provides information about the total mapping time and the amount of time that was required to perform the following operations:

Call Naming and Reconciliation Service.
Retrieve Integration Composer metadata from the repository.
Run the mapping expressions (by class).
Retrieve data from the target.
Compare source and target data.
Update/insert/delete in the target database.
Retrieve source data.

Feedback