That is a really weird error to get, I've never seen it myself. The error comes from Oracle, not from FME, but it is of course possible that FME is doing something to provoke the error on the Oracle side, although I cannot imagine how, really.

Is installing FME 2016.1 an option to see if this is a bug that has already been fixed?

You can have several different versions of FME installed simultaneously, as long as you install them into different folders.

You should probably also try to update the Oracle client libraries.

I would try to avoid reading too many tables at a time. This can be done by using the schema reader and follow by a WorkSpaceRunner. That transformer can call a second workspace with the Oracle Spatial Reader and the parameter "Feature types to read" as a published parameter. The schema reader can feed the tables to the second workspace one by one and so avoid reading all tables at once.

An additional idea: Instead of the Schema reader use the SQLCreator reading the table names from the Oracle view USER_TAB_COLUMNS (or ALL_TAB_COLUMNS) so you can filter on tables having the data type SDO_GEOMETRY.

Thanks for the answer.

Unfortunately I can't try with FME 2016. For the moment I use FME 2013. I will try to optimize my script because I do not think the Schema reader is made to retrieve geographical tables like I want. Like erik_jan says maybe with an SQLCreator.

Hi thank you for the answer.

Yes I think i will try the SQLCreator approch, because at the end I just want the list of the geographical tables and not all the information retrieved by the Schema Reader.