Davadmin Migration Needs To State When Malformed Events Are Dropped
Last updated on DECEMBER 03, 2015
Applies to:Oracle Communications Calendar Server - Version 7.0 and later
Information in this document applies to any platform.
Calendar Server 7 with patch 121657-06
Currently, when using "davadmin migration" we can turn on trace (option -c) for testing, But, this does not really scale to an entire production migration, regardless of size. We have calendars here with over 350K events and 100K tasks. Having to manually go through the trace logs for such a large migration would be daunting for an administrator. It would be ideal to have the same summary lines on failures, as we see with successful migrations.
The davadmin migration command should show sufficient summary information on*any* migration stop. This would include interruptions, control-C, or any failure to communicate across the network. If the migration stops, log the summary of the migration to the point of stopping, like it does when migration completes successfully.
Sign In with your My Oracle Support account
Don't have a My Oracle Support account? Click to get started
Million Knowledge Articles and hundreds of Community platforms