I'm a FIM newbie and am currently configuring an Oracle Management agent to connect to a view I created on the Oracle DB server.  Everything look good with the exception of my inability to edit any of the column attributes from within the Management Agent Designer.  Specifically the column length.  I need to use a specific field (column) as an anchor, and currently it is too large (DBTYPE_WSTR length 4000).     

Any help will be appreciated.

Hello,

column length is detected automaticly on Schema discovery, you can not edit this.

Seems to be a limitation maybe, the Maximum shown in my Oracle MA implementations is 500.

You can check the Generic SQL MA currently in preview on connect, which uses ODBC instead of OLEDB, maybe this connector detects correct size of large columns. (Not checked this yet).

https://connect.microsoft.com/site433/Downloads

There is a TAP Programm if you want to choose this for production.

Another Approach is to use the Powershell MA to connect to Oracle see: http://fimcreativethoughts.blogspot.de/2015/02/fim-2010-r2-overcome-slow-performance.html

Maybe someone else has a clue on this ?

-Peter

Makes sense, but there must be a work around.  Otherwise how can one avoid the dreaded "You must select anchor attributes with a column length of 900 bytes or less" error?

Found a workaround...  I'm sure its not supported, but worked like a charm.  After creating the management agent (had to choose a different column (field) to use as an anchor because of the size limit of my desired field), I then exported the management agent, manually set the column upper limit in the XML file for the problematic field, changed the anchor attribute to point to this same field, and then used this modified XML file to update the management agent.  Voila!  As long as I don't update the MA's schema, I'm good to go. 

Only a good idea if you know that the column you are fudging will never be larger than the value you are changing it to.  As this was the case for me, I felt confident with this work around.

The proper way to do it would be to create a view wherein you truncate and Cast it to be the correct length and data type.