FMEMC. Currently it is not possible to change the schema’s name or install multiple schemas on the same database instance.
SYSuser or an Oracle administrative user with enough privileges. And the database name must be selected from the dropdown field.
FMEMCwill be granted to use the following Oracle packages:
FMEMC_USER_ROLEwill be created and granted the required privileges on
FMEMCschema objects. This role must be granted to any database user that needs to use migration center.
FMEMCuser can be created manually via scripts, and the Database installer can be run with the
FMEMCuser afterwards, instead of using the
SYSuser. This can be done by running the scripts located in
...\Database\Utilfolder of the installation kit. The scripts are:
FMEMCand tablespaces do not meet the requirements of the customer or conflict with internal company policies and guidelines.
9700but any free port can be used.
Jobserver.tar.gzin the desired location using the command:
tar -zxvf Jobserver.tar.gz
./runConsole.shin the bin folder
9701and can be changed in “server-config.properties” file located in “lib/mc-core” folder.
startService.batfor starting the service
stopService.batfor stopping the service
Migration Center Job Serverservice and starting it.
./startDaemon.shfor starting the daemon
./stopDaemon.shfor stopping the daemon
./runConsole.shin the bin folder.
drop_fmemc_schema.sqlscript can be found in
database/util. Run this script against the Oracle database instance using the
SYSuser. The FMEMC schema should be removed using the Oracle administration tool of your choice.
FMEMCschema. The easiest way to do this is with Oracle’s EXP. See screen shot below for the basic steps required to back up a schema. For more information consult the documentation provided by Oracle.