2.4 Importing with the BI Migration Script (migration-tool.sh|cmd)

You must import the export bundle using the BI Migration Script (migration-tool.sh|cmd). The BI Migration Script automatically determines the Oracle home and the Domain home directories.

You can include the following parameters while running the BI Migration Script to import the export bundle in to the 12c system:

Table 2-4 Parameter Description: Importing the export bundle

Parameter	Description
in	Indicates the BI Migration Script to import the bundle.
config	Indicates the BI Migration Script to overwrite the configuration files during the import process. This allows you to also migrate the configuration along with the data.
<export bundle>	The path where the export bundle is located.
<service instance name>	Specifies the name of the service instance, which is service1.

To import the metadata and configuration in to the 12c system:

1. Run the BI Migration Script with the following parameters:
   On UNIX operating system:
   $DOMAIN_HOME/bitools/bin/migration-tool.sh in config <export bundle> <service instance name>
   For example,
   $DOMAIN_HOME/bitools/bin/migration-tool.sh in config /tmp/migration-tool-test/test_export.jar service1
   On Windows operating system:
   %DOMAIN_HOME%\bitools\bin\migration-tool.cmd in config <export bundle> <service instance name>
   For example,
   %DOMAIN_HOME%\bitools\bin\migration-tool.cmd in config /tmp/migration-tool-test/test_export.jar service1
   Where,

   Table 2-5 Parameter Values: Importing the export bundle

   Parameter	Description
   in	Indicates the BI Migration Script to import the bundle.
   config	Indicates the BI Migration Script to overwrite the configuration files during the import process.
   /tmp/migration-tool-test/test_export.jar	The path where the export bundle is located.
   service1	Specifies the name of the service instance.

2. If the migration is successful, you see the output such as the following:

   Import succeeded
   About to close down logging to: $DOMAIN_HOME/bilogs/migration/migration-2016-05-05-06-13-05.log
   This is so that the log file can be archived into the diagnostics zip
   Any remaining log entries will go to '/tmp/migration.log', and will not appear in the diagnostics zip
   Migration action succeeded
   

You can now start the 12c system. For more information about starting the 12c system, see About Managing Oracle Business Intelligence Processes in System Administrator's Guide for Oracle Business Intelligence Enterprise Edition.

Note:

It takes about 10 more minutes for the Application roles and policies to migrate after the migration process is complete.

After completing the import process, you must start OBIS1 and OBIPS1 which you stopped before beginning the migration process.