Talend Job Hangs when trying to commit [Oracle]

[Anonymous]

Hello,
I need some help on a migration from a Postgresql database to an Oracle database, I'm trying to transfer data from a table using a tMap to an identical table on Oracle, but when I run the job it hangs trying to commit the rows without showing any error messages or alerts. Here are some screenshots.

[Anonymous]

At first please connect the tOracleConnection with OnSubjobOk with the input component called smatas.
Did your tOracleOutput and tOracleCommit use the tOracleConnection?

[Anonymous]

I connected the tOracleConnection with the OnSubjobOk trigger as sugested, but the same event happens and yes sir, The Commit and Output use the tOracleConnection.

[Anonymous]

You made a mistake by connecting the tOracleCommit with a flow from the tOracleOutput.
Please connect the tOracleCommit with OnSubjobOk starting at the smatas input.
Your current way starts the commit for every row and close the connection.

[Anonymous]

I followed your instructions and nothing changed. To give you some background information, I tried this operation before with a simple tPostgresInput - tMap - tOracleOutput with the conection built in and the auto commit every 10000 rows, then I got an error which I solved by lowering the auto commit amount of rows but I got this weird event and tried using the actual Job components (tOracleconnection and commit).

[Anonymous]

I would in this case start investigating the situation with the Oracle Enterprise Manager. It looks like a deadlock or if the table is otherwise locked. Please check your insert / update with a external SQL tool like the SQLDeveloper. 
Your design is quit normal and is definitely not the problem.

[Anonymous]

Hi,
You have a warning message in your DBoutput component, can you hover on the warning sign check to see what is the message and fix that. 
This should solve your problem. This is a metadata issue which is available since your first screenshot, that is the reason, the records are not getting inserted into the target table.
Vaibhav

[Anonymous]

Hi Vaibhav,
I would not say that. The warnings often simply affects columns without the correct SQL data type. But this has only an negative effect of you let the component create the table. This is not the case here. For me it looks like the is a lock on the table caused by any other connections and DML statements running from outside Talend.