Search all mapping source filters with a given text in Informatica repository;
SELECT INSTANCE_NAME, ATTR_VALUE FROM OPB_SWIDGET_ATTR, OPB_TASK_INST WHERE ATTR_VALUE LIKE '%TEXT_2_SEARCH%' AND SESSION_ID=TASK_ID
Posts Tagged ‘Informatica’
Multiple-step OLE DB operation generated errors
26
Jan
The error message which SQL Server returns is:
Database errors occurred: Microsoft OLE DB Provider for SQL Server: Multiple-step OLE DB operation generated errors. Check each OLE DB status value, if available. No work was done. Database driver error… Function Name : Execute Multiple
Please check the columns of the table which data is trying to be inserted.
eg. executed script is “INSERT INTO MY_TABLE (MY_COLUMN1, MY_COLUMN1, MY_COLUMN3) VALUES BULABULA…” but MY_TABLE does not have the column MY_COLUMN3!
Hope this helps.
Task is Succeeded but no Applied Rows
30
Jun
I faced an interesting issue in Informatica yesterday.
There is no error on the Monitor screen, but when I list the details of the “Succeeded” task, I saw:
Applied Rows = 0
Rejected Rows = 261733 (required to be applied rows number)
Last Error Code = 8425
Last Error Message = ERROR: Writer execution failed. Database error: [0]… bula bula bula
Actually, I do not interest with the error. I am confused because however there is an error, on the monitor screen task’s status is Succeeded!
What about the solution?
We want task to stop when any errors occured. So we have to follow and change:
Edit Tasks -> Config Object -> Error handling / Stop on errors = 1 (default value is 0)
As you can see below;
Or alternatively, we can add a Control with Expression “TgtFailedRows > 0″ as you can see in the figures below;
Informatica error CMN_1653 solution
30
Jun
Error Code: 1653
Error Details: CMN_1653 Cache file was created with logical database connection [Relational:DB1] while cache expects [Relational:DB2]
As you can see easily, error is because of usually a transformation (lookup, etc) in the task tries to read from cache persistently!
We have to follow and edit;
Edit Tasks -> Mapping -> Select the related Transformation -> Properties / Lookup cache persistent -> Unselect the checkbox
As you can see also in the figure below;
Could not acquire the execute lock for Worklet
10
Jun
If a worklet fails with the status message below;
ERROR: Worklet task instance [wklet_name]: Could not acquire the execute lock for Worklet [wklet_name]
This means the worklet is already working or suspended in some other workflows. You have to check other workflows and abort the worklet.
