Skip to main content
Question

FME shows successful when disconnected from database


Forum|alt.badge.img

When using FME (2017) to extract a largish amount of data (~6,000,000 rows x 40 columns) from an Oracle database, the process is sometimes stopped, assuming by a DBA due to the size. However, FME returns with a translation successful message in the log rather than failure. Is this a known issue? or am I doing something wrong? or is there a workaround to catching this type of error? Like getting FME to do a record count beforehand.

 

Note while I can get around the issue by breaking down the query. I would like to know if FME can trap/detect this type of issue.

5 replies

david_r
Celebrity
  • May 27, 2019

Are there any warnings or errors in the FME log that indicates this issue?


Forum|alt.badge.img
  • Author
  • May 27, 2019
david_r wrote:

Are there any warnings or errors in the FME log that indicates this issue?

No warnings or errors. The log file has "Translation was SUCCESSFUL with 0 warning(s)"


david_r
Celebrity
  • May 27, 2019

I've seen at least one example where a message that should've been classified as a warning or error in FME was simply logged as INFORM, thereby getting drowned in the other messages. Could that be the case here? Can you read through the log file carefully and see if you can find any mention of a dropped connection or similar?

If not, then I suspect that the error lies entirely with either the backend database or the client driver, not with FME.


andreaatsafe
Safer
Forum|alt.badge.img+12

Hi @nic_

Would you be able to try the latest FME 2019.0 to see if this still occurs. I believe that the message logging has been improved a fair amount since FME 2017.

Typically, if an error occurs when reading/writing from the database, FME would report this as an error message (and any error message that the database may have given) and cause the translation to stop.

If you are still seeing this same issue in FME 2019, would you be able to share your log file?

- Andrea


Forum|alt.badge.img
  • Author
  • May 28, 2019
andreaatsafe wrote:

Hi @nic_

Would you be able to try the latest FME 2019.0 to see if this still occurs. I believe that the message logging has been improved a fair amount since FME 2017.

Typically, if an error occurs when reading/writing from the database, FME would report this as an error message (and any error message that the database may have given) and cause the translation to stop.

If you are still seeing this same issue in FME 2019, would you be able to share your log file?

- Andrea

Thanks @andreaatsafe I will try upgrading when I can. Note I am using the SQL creator to retrieve the data from Oracle. I have attached an image of the final result. Which should be about 5.4m records. Each time I run the exact same process, the number varies considerably.


Cookie policy

We use cookies to enhance and personalize your experience. If you accept you agree to our full cookie policy. Learn more about our cookies.

 
Cookie settings