Skip Headers
Oracle® Enterprise Data Quality for Product Data Endeca Connector Installation and User's Guide
Release 11g R1 (

Go to Documentation Home
Go to Book List
Book List
Go to Table of Contents
Go to Feedback page
Contact Us

Go to previous page
PDF · Mobi · ePub

E Endeca Connector Troubleshooting

Troubleshooting the loader and pipeline processes is typically straightforward. The Oracle DataLens Server is verbose about the errors it encounters, and typically the error messages indicate how to locate and correct them. There is an additional level of logging available by turning on the PDQ.Tracing parameter in the discovery processes, which is very verbose about the data lens each attribute comes from, and what dimensions were discovered. If the process completes successfully, you can look in the Endeca Developer Studio, and see that the dimensions have been added and that precedence rules have been built to the appropriate parent dimensions.

The Endeca Connector is configured through a number of pass through parameters as follows: The Endeca Connector parameters are:


The batch size property controls how much data is sent to the server(s) as a chunk. The chunk data is held in memory on the Endeca Server. While increasing the chunk size can improve performance, if the data fills the Endeca buffers, this causes a fatal error. The default chunk size is 15000, a recommend maximum would be 20000 and of course depends on your hardware configuration.


The DSA which will be called on the Oracle DataLens Server to process the sent data. This is also used by the loader process as described above.


The property to be used as the first (id) field in the DSA. If this property is not available for a record, errors can be generated.


The second field in the DSA. This property will be used to route the data to the correct data lens.



The fields with the record descriptions. While not required, if you do not provide any description, the results will not be very useful.




Optional fields which can provide additional fields to the DSA. These can change the behavior of the process, or include additional information for standardization or routing.




Required fields returned from the DSA. These are typically used for data lens transform fields, such as Item Definition Quality or Standardized Description. These fields do not have an attribute name/value pair, so this pass through is used to assign a property name to the returned value.


The server name and port number for the first processing server. Multiple servers can be defined. This allows for fail over and load balancing capabilities for large installations.

Optional parameters can be disabled by setting them to the string unused.

Troubleshooting the pipeline process falls into three main categories, based on the log file you need to examine as described in the following:

Forge errors

Review the Forge.log. Forge is reasonably good about what caused the error. If forge indicates the problem is with the PdqAdapter, then you need to review the Edf.Pipeline.RecordPipeline.JavaManipulator.PdqAdapter.log.

Oracle DataLens Server errors and Endeca pipeline errors

Review the Edf.Pipeline.RecordPipeline.JavaManipulator.PdqAdapter.log file. This log file contains the transactions between the Endeca pipeline and the Oracle DataLens Server. This is the main log used to troubleshoot the EDQP Endeca Connector integration. It may not be accurate in its errors because it does not have a lot of visibility into what has happened on the Endeca or EDQP sides. Additional logging can be enabled with the PDQDEBUG pass through parameter; this debug information is very verbose so it can fill your disks quickly if you leave it on.

Oracle DataLens Server errors and information

Review the dataserver.log file. Go to the Oracle DataLens Server Administration web page and review all job status information. For more information, see Oracle Enterprise Data Quality for Product Data Oracle DataLens Server Administration Guide.

Typically, you will be able to isolate the cause of an error in the DSA process. It is also useful if an error does not occur though no results are produced. The dataserver.log on the Oracle DataLens Server contains verbose errors, including stack traces if configured.