Skip to main content
Question

Oracle Reader - Different handling in null columns in an aggregate function in 25.1 and 25.2

  • January 20, 2026
  • 3 replies
  • 28 views

max_h
Enthusiast
Forum|alt.badge.img+23

I just updated to version 25.2 and my oracle reader is failing and throwing this warning (not an error):
An error occurred while fetching from query `SELECT a.*** FROM *** a' : OCI_SUCCESS_WITH_INFO: ORA-24347: Warning of a NULL column in an aggregate function

Which causes Translation FAILED with 0 error(s) and 1 warning(s) (0 feature(s) output).

My colleague tried the same on version 25.1 and whilst he also gets the warning his translation does not stop and he gets all features to work with. (As did I before my update)

Ignoring the fact that the view should be fixed, is there a way to continue the translation with all features? Troubleshoot option Ignoring failed readers simply skips the reader and thus returning zero features.

Furthermore I did see a few changes regarding oracle in the changelogs but I could not pinpoint which one is referring to this problem.

3 replies

david_r
Celebrity
  • January 20, 2026

You can try to replace the reader with a FeatureReader (not very likely to make a difference, but you never know), or a SQLExecutor (which should work, but it’ll most likely be slower)


max_h
Enthusiast
Forum|alt.badge.img+23
  • Author
  • Enthusiast
  • January 20, 2026

Thanks for the suggestions, but sadly FeatureReader, SQLExecutor and SQLCreator are all writing to Rejected port with reader_error: An error has occurred. Check the logfile above for details’ → ORA-24347: Warning of a NULL column in an aggregate function


max_h
Enthusiast
Forum|alt.badge.img+23
  • Author
  • Enthusiast
  • January 20, 2026

I fixed the view, issue was that listagg() had a few null values as it seems, so I had to add a few ‘not null’ conditions.

 

Still wondering though, what changed between the FME versions in this regard as it definitly worked beforehand on 25.1