Troubleshooting ECM errors

Identifying ECM Error Types and Number of Records Involved

There are times when you will encounter errors when processing data into V9 using ECM. This document will provide you with the steps you need to take in order to identify the data type (customer, document, item) as well as the total number of records that have this error. This document is not intended to provide you with the steps required to resolve error conditions as there are numerous possible errors that can be encountered during ECM processing that will each require individual review and steps to resolve based on their unique conditions.

ECM Proc Window

While processing data into V9 you are presented with the ECM Proc window which provides the user with line by line detailed information of each data type being processed in, the start time, duration and if an error is encountered the type of error along with the Doc_Sid of the first record that had the error condition. It is important here to understand that it is very possible that there are more records that also had this error condition, although you will only see the first record listed here.

When ECM is processing in and encounters an error this is what occurs. In the ECM Proc Window and the ECM log the type of error is logged along with the Doc Sid of the first record to have this type of error. The error along with the Doc Sid is also logged in a .trc file in the Trace directory found in the path below.

X:\Oracle\diag\rdbms\rproods\rproods\trace - Where X:\ is the drive where you have Oracle installed.

The bad record is not processed into the database. ECM then continues to process through the XML file, successfully processing in records that do not have errors and rejecting and logging errors in the .trc file for each individual record that has an error condition. Once ECM has finished processing through the xml file, and if there was 1 or more errors found while processing that xml file, the entire xml file is left in the TEMP directory.

Below is an example of a ORA-00001: Unique Constraint error found during processing inventory records into V9 as seen in the Proc Log.

The ECM Log


In addition to being notified vai the Proc Window that a log has occured you can see the error is also entered into the ECM logs. In the Status column for the ECM Proc Session will be information about the type of error received. Again, this only records the first instance of each error type along with the Doc_Sid of the first record to have this error condition. We will need to examine the .trc files to find a list of all records that were rejected with this error condition.

The Trace Directory

As mentioned above the error along with the Doc Sid is also logged in a .trc file in the Trace directory. Below are the paths where they can be found based on the version of Oracle database installed.

Oracle 9i (R1 and R2)

X:\Oracle\Admin\Rproods\Udump (Where X:\ is the drive where you have Oracle installed)

Oracle 11g (R3, R4 and R5)

X:\Oracle\diag\rdbms\rproods\rproods\Trace (Where X:\ is the drive where you have Oracle installed)

Once you have located the appropriate directory based on your version of Oracle the best way to find the specific .trc file that contains information about the error is to sort the list of files in this directory by modified date and time. Then search for the .trc file that was created after processing was started but close to the time the error was logged. In addition, the file will typically be larger than the default size of 1kb as seen below

The .TRC file

Looking at the screen shot above we have identified the proper .trc file as rproods_ora_4164.trc based on this file being created just minutes after processing in, and the file size being larger than 1kb. Upon examining this file we are able to see the same error logged in the file, and each associated Doc_Sid for each record that was rejected by ECM upon processing the data into V9. As you scroll through this file you will see each record that had the error listed. It is easiest to simply search the string "Doc_Sid" and you can review each record one by one if needed.

Review of important points

1. ECM will only log one instance of each error type received and the first record to have this error conditon.

2. The .trc files will contain a list by doc_sid of all history documents, items or customer records that were rejected.

3. Records that do not have this error will be processed into V9, only bad records will be rejected.

4. If errors were encountered the entire xml file will be left in the TEMP directory

Published on Mar 18, 2014 in ECM


Find Another Article