Symptoms

When using an Oracle writer in FME there are times when the engine will lock a table and not allow other data manipulation language (DML) statements to execute against the table that may come from other Oracle Sessions.  Obviously this is not an ideal situation. 

We have a PR in the works to resolve this problem but for now there is a sort of a work around available.

Cause

In the instance of FME Server it will require the Engine to be restarted to release the lock on the table.  Essentially there is no COMMIT being issued when the translation completes.  This is to allow a rollback to occur if only a part of the Translation was successful when writing to a database.

Resolution

The work around is to run a statement "SQL Statement to execute after Translation" on the writer.  One particular statement that would fit this is the following:

'BEGIN dbms_wm.gotoWorkspace('LIVE'); END;'

This essentially invokes an "implicit commit' and the lock on the table gets released.   A bogus DDL statement would also likely do the same but I've not tested this. A customer reports success with the above statement.
 

This article will be removed when the PR is resolved.