Not a change per-se in IDM 4. It has always been better to be more specific in your configuration
of the database objects.

Usually that message means that it either can't find the table in question (security, naming, etc)
or that it is a table with an issue with keys.

If you want to see specifically the issue, set it back the way it was, set the trace level to 25 and
restart the driver. It will spew out every detail including the exact SQL calls that discover the

On 7/18/2012 9:56 AM, gregwilkerson wrote:
> Well, I was wrong about the version of IDM. We're running 4.0.1. I
> wasn't aware of that.
> And, in a wild attempt to see if I could get this working, I updated
> the table_name column to include the owning schema of the Employee table
> (changed the value from 'Employee' to 'dirxml.Employee' and the driver
> started processing. It's slow, but at least it's working.
> So, what this a change in IDM 4?
> Greg