Warning : Ignoring duplicate entry at table record 453159; no further warnings will be issued for this table

This warning is seen when there are multiple records with the same key column is present in the reference table from which lookup is done. Lookup, by default, will fetch the first record which it gets as match and will throw the warning

since it doesn’t know which value is the correct one to be returned from the reference.

To solve this problem you can either one of the reference links from  “Multiple rows returned from link” dropdown, in Lookup constraints. In this case Lookup will return multiple rows for each row that is matched.

Else use some method to eradicate duplicate multiple rows with same key columns according to the business requirements.

Warning : When checking operator: Operator of type "APT_TSortOperator": will partition despite the preserve-partitioning flag on the data set on input port 0.

These warnings are obtained when we are using some specific partitioning method in a stage in the job e.g hash/same etc but in the preceding stage , preserve portioning(also default) is set in the stage>advanced tab.

To solve this warning the preserve portioning should be set to clear in the preceding stage where we are using the particular partitioning method.

Warning : APT_CombinedOperatorController(1),0: Data string 'yyyymmdd' does not match format '%yyyy%mm%dd': an integer was expected to match tag %yyyy.

If you get the same or similar warning, check the format of the string used in the Stringtodate()/stringto timestamp() function.

The format is StringToDate(“String”,"%yyyy%mm%dd")

Where in the above case the string should be in the format e.g 20130304.

If your string is in the format ‘2013-03-04’ change the format pattern e.g StringToDate(“String”,"%yyyy%-mm%-dd")

Error : The OCI function OCIStmtExecute returned status 1. Error code: 24,381, Error message: ORA-24381: error(s) in array DML.

This warning is obtained usually when there is a problem in the number of records getting loaed in the array. For this we need to get the correct balance between the record count and array size property.

The record count should be a multiple of the value for array size. For one of the projects we set the value of record count as 10000 and array size as 2000 and the warning was gone.

Error : The OCI function OraOCIStmtPrepare returned status -1. Error code: 1,756, Error message: ORA-01756: quoted string not properly terminated. (CC_OraStatement::prepare, file CC_OraStatement.cpp, line 392)

  This occurs when the query written in the stage lacks correct format. If all columns and filters are properly defined check the parameters being passed. Most of the the times it can also

Happen due to some discrepancy in the parameter being used.

Fatal Error: Attempt to setIsNull() on the accessor interfacing to non-nullable field "column_name".

As evident this error can occur when you are trying to assign a NULL value to a NOT NULLABLE column. But this can be a little tricky sometimes.

Like if you use trim(col_name) where col_name is a not nullable column. Still it can have a NULL value as trim(Blank Spaces) in oracle gives NULL.

So, if you are using a trim in the query and the column is defined NOT NULL, beware that it can give the above error in case blank values(which are in fact NOT NULL) come in that

Column.

You can resolve it  by defining the column as NOT NULL, or remove the trim from the query and use the trim in a transformer.

Error : The OCI function OCIStmtExecute returned status -1. Error code: 1,654, Error message: ORA-01654: unable to extend index schema.index_name by 1280 in tablespace USERS. (CC_OraStatement::executeInsert, file CC_OraStatement.cpp, line 1,642)

 This error is caused due to insufficient tablespace. Ask the DBA to increase the tablespace for the concerned table.