SSMA Oracle to SQL Server data migration step fails with no explanation

SSMA Oracle to SQL Server data migration step fails with no explanation 

• 
  

• The conversion process worked fine and created the objects in SQL Server but when I try and migrate the data it doesn't work and gives no explanation why.  The output looks like this:

  Migrating data...
  Analyzing metadata...
  Preparing table TIMECARD.TBLSTAFFID...
  Preparing table TIMECARD.TBLTIMECARD...
  Preparing table TIMECARD.TBLTIMECARDDETAIL...
  Preparing data migration package...
  Starting data migration Engine
  Starting data migration...
  Data migration operation has finished.
   0 table(s) successfully migrated. 
   0 table(s) partially migrated. 
   3 table(s) failed to migrate.

  There are no errors on the error list tab.  The report looks like this:

  Status    From-Table    To-Table    Total-Rows    Migrated-Rows    Success-Rate    Duration(DD:HH:MM:SS:MS)    Error-Messages
  Initial "TIMECARD"."TBLSTAFFID"                                                     N/A  
  Initial "TIMECARD"."TBLTIMECARD"                                                  N/A  
  Initial "TIMECARD"."TBLTIMECARDDETAIL"                                       N/A

  There is a red X for the status on each but when I select any row the details button remains greyed out.

  Same result whether I use server side or client side migration.

• ===============================================================

• After a lot of building of VM's and reverting snapshots to test a lot of different things it turns out this was a problem with the case sensitivity in the schema mapping.

  The database is named TIMECARD in Oracle and when I have been creating it in SQL Server I have been calling it TimeCard.  Even though it seems to be ok when it creates the objects on the SQL Server, when it goes to migrate the schema mapping defaults to:

  TIMECARD --> TIMECARD.dbo

  This does not work.  But when I change the schema mapping to:

  TIMECARD --> TimeCard.dbo

  Then it works fine.

  For what it is worth I am using the default collation sequence on the SQL Server which is case insensitive so this looks like an SSMA sensitivity.

  I still don't know what the memory error messages in the SSMA log are about when I use the 32 bit version but they don't seem to make any difference as far as I can tell.

  ==================================================================