hi, we have an Oracle based HR system and have created a Delta view. We first run a full import. then change some data in Oracle. then run the delta import...but everytime we run the Delta import we see this message: "The selected run profile contains delta import steps. the MA has detected that a full import is required to update connector space. Running delta import at this time may result in errors." we then run another Full Import, and try the De;ta import and get the same warning. Any ideas? thank you

Some questions you need to answer first ... What is the return status of your full import? At the risk of stating the obvious, if it's "completed-no-objects" then that would explain why you're getting this message (you can't perform a delta for a DB management agent without returning at least one record in the full import). Are you using the Oracle MA, or an ECMA? If you are using an Oracle MA, it should work much the same as the SQL one, in which case the design considerations for your delta view will be basically the same (see http://technet.microsoft.com/en-us/library/cc720574(WS.10).aspx). The reason I point this out is that there are some prerequisites for your design ... for instance check that the schema for your full and delta imports vary by just the "change type" column. If, however, it is an ECMA, then some checks can be made of the generated import file to determine possible causes of your problem. Were there any discovery errors on the full import? If so then these will continue to prevent you running a delta until they are resolved. Bob Bradley, www.unifysolutions.net (FIMBob?)

Some questions you need to answer first ... What is the return status of your full import? At the risk of stating the obvious, if it's "completed-no-objects" then that would explain why you're getting this message (you can't perform a delta for a DB management agent without returning at least one record in the full import). We have a few records in the main view. we have deliberately changed some records so the delta view contains some data. Are you using the Oracle MA, or an ECMA? If you are using an Oracle MA, it should work much the same as the SQL one, in which case the design considerations for your delta view will be basically the same (see http://technet.microsoft.com/en-us/library/cc720574(WS.10).aspx). The reason I point this out is that there are some prerequisites for your design ... for instance check that the schema for your full and delta imports vary by just the "change type" column. If, however, it is an ECMA, then some checks can be made of the generated import file to determine possible causes of your problem. We are using the built-in Oracle MA. We have the 'change-type' column and confirmed we are using "add, modify, remove" Were there any discovery errors on the full import? If so then these will continue to prevent you running a delta until they are resolved. This is the only recorded error on delta import run, nothing on full import run: "The selected run profile contains delta import steps. the MA has detected that a full import is required to update connector space. Running delta import at this time may result in errors."

it seems that your HR MA is not read only, are you exporting modification or deletes? if so you need to add the modification/delete object (exported by FIM to your HR table) to the delta table, since FIM will try to confirm the exported item by re-importing. so in your case the delta import/delta table does not have all the exported-records previously done by the export profile (those objects are marked in FIM as awaiting confirmation after export), so FIM detect that and will always ask for full import.