Extended Feeder Manager Conversion Tool

  • Create a backup of your geodatabase before running this tool. Should this tool fail, the changes cannot be rolled back. 

  • Enable Oracle's EZCONNECT. For more information, please refer to Oracle's documentation.

  • The conversion may take several hours to complete on an SDE geodatabase. It is recommended that you delete any unnecessary versions and compress the geodatabase prior to running this conversion tool.

  • Ensure you are the only user logged in during conversion. The tool will fail if other users are logged in and versions are locked while it is running.

What the Extended Feeder Manager Conversion Tool Does

The Extended Feeder Manager (EFM) Conversion tool adds the GlobalID field to the CircuitSourceID table. The tool also adds some new fields to support this change and assigns the appropriate field model names.

The Extended Feeder Manager Conversion cannot be added to any toolbar. It is available in: Program Files\Miner and Miner\ArcFM Solution\Bin\EFMStandAloneConversion.exe.

When to Use the Extended Feeder Manager Conversion Tool

The conversion tool enables Extended Feeder Manager to rely on GlobalID-based relationships to the CircuitSourceID table by adding a GlobalID field to the CircuitSourceID table, and making the schema, configuration, and data changes necessary to the Feeder Manager features in order to maintain the consistency of the Feeder Manager network. Use this conversion tool if:

Converting a Database 

To convert a database, follow the steps below.

  1. In the ArcFM Solution\Bin directory, double-click EFMStandAloneConversion.exe. When the tool opens, select a database in the Browse to database field.

  2. A login window opens.
    For Oracle: In the User Name field, type in the user who owns the business data.
    For SQL: In the Database field, type in the name of the database. In the User Name field, type in the user who owns the business data.
    NOTE: This tool uses both a non-SDE connection and an SDE connection. When you log into the database in the first window log in as the data owner. Generally, the first part of a table's name may indicate its owner. For example, if a table is named Arcfm.Transformer, the owner of the table is Arcfm.
  3. After you select the database and log in as the data owner, several fields should automatically fill with standard default information. Verify that this standard default information is accurate, and fill in the DB field.



    Browse tothe SDE database being updated

    The connection to the database.


    The server on which the database resides.

    Database (EZConnect Name)

    Oracle: This field defines the Oracle connection. Type in the EZConnect name of the database. EZConnection names are case-sensitive. For more information, please see the Oracle documentation.

    SQL: This field is not needed for an SQL connection. (It defines the Oracle connection.)

    Port (Oracle) or Instance Name (SQL Server)

    The port, if oracle, or Instance Name, if SQL server, used by the database.


    This field is for establishing an Oracle  or SQL connection. Log in as a user who has permission to write to the database.



    Fully qualified SDE registry table name

    If you changed the name of the SDE registry table, replace the default name (SDE.TABLE_REGISTRY) with the new name.

  4. Click Connect. The Run button will become active.
  5. Click Run. A warning window appears. If the database is backed up, click Yes.

  6. After a successful conversion, the following window appears. Click OK to exit the Extended Feeder Manager Conversion tool.
    NOTE: If the conversion was not successful, you will need to restore the database from the backup.
QR code for this page

Was this helpful?