Common Adapter Errors

Products

• CA Business Service Insight

Issue/Introduction

This document list common errors found in the Adapter log file and solutions for those errors

Environment

CA Business Service Insight

Resolution

Common Errors:

1. Error
   info="Warning ! The upper limit of rejected events (100000) has been reached. The adapter was blocked."/>
   
   Solution
   This means you have reached the rejected events limit. In order to resolve this issue go to the general section of your adapter wizard, then click advanced and select the processing tab of the pop up window. Locate where the 'Runtime errors limit' setting is and increase the value. The other method is to simply go into your adapter folder and locate rejectedEvents.txt and delete the file. The adapter will automatically generate a new empty rejected events.txt on its next start up.
   
   
2. Error
   info="Can not set time field "F_2" (input format "Input1") from "Time". Expecting days according to %d [Time][%d/%m/%y].
   
   Solution
   This means a date was found in the database for the field mentioned in the error which does not match the date format selected in the general section of the adapter wizard. Please make sure your date formats in the database match the selected format in the general section from adapter wizard.
   
   
3. Error
   Configuration error : "QueryName" attribute in "AdapterConfiguration/DataSourceInterface/QueryCollection/Query" node is empty or contains illegal characters ("New Query"). Legal characters are A-Z, a-z, 0-9 and _ .
   
   Solution
   Go to the data source interface section of your adapter wizard and click advanced. Locate the 'Query name' setting and make sure you are using the proper naming convention. Legal characters are A-Z, a-z, 0-9 and _ .
   
   
4. Error
   Caught COM ERROR in operation QUERY (select e.some_id, e.some_name, n.some_availability, from some_Table n, other_Table e where e.some_id=n.some_id and e.some_id in (1000350,1000351) and some_id>0 order by some_id ) [ORA-00918: column ambiguously defined
   
   Solution
   This means you must check your query. Most of the time you just have to make your query more specific.
   
   If you take this example:
   
   select e.some_id, e.some_name, n.some_availability, from some_Table n, other_Table e where e.some_id=n.some_id and e.some_id in (1000350,1000351) and some_id>0 order by some_id
   
   It should be written like this: select e.some_id, e.some_name, n.some_id, n.some_availability, from some_Table n, other_Table e where e.some_id=n.some_id and e.some_id in (1000350,1000351) and e.some_id>0 order by e.some_id
   
   Also this query selects from two tables - a lot of times joining the tables using the join keyword as opposed to the way it's done in this query will resolve an error like this.
   
   
5. Error
   Remember: The key fields must be the first fields, and in the same order, in the select statement and in the input format."/>
   
   Solution
   Go to the data source interface part of the adapter wizard and check the SQL statement. Remember: The key fields must be the first fields, and in the same order, in the select statement and in the input format.
   
   
6. Error
   info="Error in query "NewQuery". The number of fields in the query (3) is not like the number in the input format (7)"/>
   
   Solution
   The good thing is that the BSI UI will not actually let you create invalid mapping between the input source and event type. This type of problem usually occurs after an adapter mapping has been completed and then the user goes back into the adapter and changes the SQL used to query the source DB. All of the input fields from the old query will still be on the input column of the mapping page and so will the new input fields from the new query. Please delete the old mapping input fields from the input mapping column in the mapping wizard.