FMEMC. The schema name is fixed cannot be changed; as a consequence it is also not possible to have more than one schema installed on the same database instance.
FMEMCis created and granted access to all necessary packages, objects and privileges (also see section Oracle Privileges). For storing data and indices two tablespaces are also created for use by
FMEMC(also see section Oracle Tablespaces).
FMEMCuser during installation. After database installation has completed successfully, it is possible to log in with the user
FMEMCand connect to the migration-center database in order to start using the solution.
SYS. Since this might not be possible in some environments, there is the alternative of customizing the critical part of the setup and having an administrator execute the appropriate scripts.
FMEMC, tablespaces, data files, etc., and then run the rest of the setup by running the setup program using the previously created user
FMEMCfor connecting to the database instead of
SYS. In this case the below permissions must be granted to user
FMEMCin order for the setup program to determine whether migration-center tablespaces and/or data files already exist on the instance where the database is supposed to be installed.
GRANT SELECT ON SYS.DBA_DATA_FILES TO FMEMC;
GRANT SELECT ON SYS.DBA_TABLESPACES TO FMEMC;
GRANT CONNECT, RESOURCE TO FMEMC;
GRANT CREATE JOB TO FMEMC;
GRANT SELECT ON SYS.V_$INSTANCE TO FMEMC;
GRANT CREATE VIEW TO FMEMC;
GRANT SYS.DBMS_LOCK TO FMEMC;
GRANT SYS.UTL_RAW TO FMEMC;
GRANT SYS.UTL_ENCODE TO FMEMC;
GRANT SYS.DBMS_SCHEDULER TO FMEMC;
GRANT SYS.UTL_TCP TO FMEMC;
GRANT SYS.UTL_SMTP TO FMEMC;
SYSwhich may not be allowed to be used.
FMEMCinstead of user