Migrate Storage tool drops the feature class when an error is encountered creating the spatial index

Description

The Migrate Storage geoprocessing tool drops the feature class being migrated if the process encounters an error when creating the spatial index. The issue only impacts feature classes stored in Oracle that are being migrated from compressed binary geometry to ST_Geometry. When the bug is encountered, the tool returns the following error message:

Code:
Executing: MigrateStorage 'Database Connections\Connection to TRUENORTH.sde\BOB.PARCELS' DEFAULTS
Start Time: Sat Feb 07 22:15:14 2015
ERROR 000955: Error encountered migrating the database storage of Database Connections\Connection to TRUENORTH.sde\BOB.PARCELS..
Underlying DBMS error [Error executing PL/SQL Block db_stgeom_create_index_by_schema::-ORA-29855: error occurred in the execution of ODCIINDEXCREATE routine
ORA-01654: unable to extend index BOB.S2$_IX1 by 128 in tablespace USERS] [BOB.PARCELS]
Failed to execute (MigrateStorage).
Failed at Sat Feb 07 22:19:21 2015 (Elapsed Time: 4 minutes 7 seconds)

Code:
Executing: MigrateStorage 'Database Connections\Connecton to TRUENORTH.sde\BOB.PARCELS' DEFAULTS
Start Time: Sat Feb 07 22:22:56 2015
ERROR 000955: Error encountered migrating the database storage of Database Connections\Connecton to TRUENORTH.sde\BOB.PARCELS..
DBMS table not found [ORA-00942: table or view does not exist] [BOB.PARCELS]
Failed to execute (MigrateStorage).
Failed at Sat Feb 07 22:23:00 2015 (Elapsed Time: 4.89 seconds)

Note:
Before performing a data migration, always create a backup of the database. For more information on migration requirements, see Data migration from one storage type to another.

Cause

The Migrate Storage geoprocessing tool is mistakenly dropping the feature class when an error is encountered creating the spatial index.

Workaround

1. Restore the database backup.
2. Apply the above patch on the machine from which the Migrate Storage tool is run.
3. Re-run the Migrate Storage tool.