All
�
In order to save time, we have decided to load our new test servers with
hundreds of thousands of assets through a direct SQL import from an earlier
direct SQL export rather than through Atrium AI and the Reconciliation Engine.�
We have figured out which tables had to
be exported, have imported both the staging and production data using SQL, and
all seems well after the import except for one detail.
When we first run the Reconciliation Engine Job that pushes data from staging
into production (needed when we incrementally add assets after the initial SQL
import), every single asset imported initially through SQL is Merged, and of
course this takes a very long time.� This was surprising because in the
database from the SQL import, every asset in the staging dataset has
ReconciliationMergeStatus=50 (Merge Done) and our Job does not Merge
unchanged CIs.� I expected none of these assets to be included in a Merge.�
Moreover, all of our SQL-imported assets had Reconciliation IDs and the
Reconciliation Job did correctly skip the Identification Step.
Does anyone know why we are seeing this behavior?� Is there another
field on another form that controls why all of our records were merged even
though ReconciliationMergeStatus=50.
We are using 8.0 and oracle 11g.
Thanks
Atul
_______________________________________________________________________________
UNSUBSCRIBE or access ARSlist Archives at www.arslist.org
"Where the Answers Are, and have been for 20 years"
