Skip to main content
Solved

Force error when source table doesn't exist or attributes are missing

tfcw
Participant
Forum|alt.badge.img+1
  • tfcwParticipant
  • Participant

I have a lot of workspaces running off a lot of Oracle tables in a lot of different databases. When I run a workspace in which an attribute defined in a Reader doesn't exist in the source, I get this message in the log:

2021-01-06 11:31:24|   1.4|  0.0|WARN  |Oracle Reader: Column 'COLUMN_2' specified on Feature Type but does not exist in table 'TEST' and will be ignored

When I run a workspace in which the table no longer exists, or I lost access to it, I get no message at all and the workspace just treats it as reading 0 rows from the source.

 

Is there a way to configure FME so that these cases will cause the translation to fail? I know I can do post reading checks to make sure rows came through and each attribute isn't missing, but I have a whole lot of these so it would be nicer if there was just a switch I could flip somewhere.

Best answer by markatsafe

@tfcw​ There is no simple switch I'm afraid. But we recently presented a webinar on these very ideas.: Database Tips & Tricks: Strategies for Detecting and Handling Schema Drift. So have a flick through that to see if there is anything that helps.

As a starting point, FeatureReader returns both the features and the schema metadata, so comparing those will get you part of the way.

View original
Did this help you find an answer to your question?

2 replies

M
Forum|alt.badge.img+2
  • markatsafe
  • Best Answer
  • January 6, 2021

@tfcw​ There is no simple switch I'm afraid. But we recently presented a webinar on these very ideas.: Database Tips & Tricks: Strategies for Detecting and Handling Schema Drift. So have a flick through that to see if there is anything that helps.

As a starting point, FeatureReader returns both the features and the schema metadata, so comparing those will get you part of the way.

david_r
Evangelist
  • david_rEvangelist
  • January 7, 2021

If you need to stop on missing input tables, make sure that "Ignore failed readers" is set to NO under Workspace Parameters / Translation.

Reply


Helpful Members This Week

Community Stats

30,940
Posts
117,251
Replies
38,742
Members

Latest FME

Terms & ConditionsCookie settings

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
A product of
Safe Software respectfully acknowledges that we live, learn and work on the traditional and unceded territories of the Kwantlen, Katzie, and Semiahmoo First Nations.