Data Import

Setup the target version

1 On the database server, create another database schema to use for importing the migration data for testing purposes. If you use Oracle, please ask your DBA to do this. If you use MySQL, follow the same steps as you did previously to create (a) new database schema(s) and add permissions for the user “apriori”. This time give the new schema a different name such as including the current version, for example: "apriori_2016R1".

2 On the database server, import the migrationdata dump file into your new master database schema, and import the standarddata dump file into any other database schemas. Use the section below that reflects your database management system.

Note: If you only have one database schema, that is your master database schema. If you have multiple database schemas, one of them is the master. The master schema is the one which contains users and license information. It is also the database that was entered at the time you installed the aPriori client software and is referenced in the hibernate.properties file (found in the aPriori installation’s home directory).

ORACLE: Ask your DBA to import the following files using Oracle’s impdp utility:

migrationdata<version>_oracle.dmp into the new master schema

standarddata<version>_oracle.dmp into any other schemas.

The details of the database dump files including the user and tablespace from which they were exported are included in the readme.txt file inside the zip file containing the database dump files. The databases can be remapped to a different user and tablespace.

MySQL: Follow these steps:

From a command prompt use the following command to import the database file to your master database:

mysql –user=root –password=<rootPassword> aPriori_<version>
< migrationdata<version>_mysql.sql

The command prompt disappears while the data is importing. It takes a few minutes for the import. After the data is imported successfully, the prompt returns with no message. You know it imported successfully if no error messages are displayed.

If the MySQL \bin directory is not in the PATH environment variable, Windows does not know where to find the mysql.exe file. Therefore, you may have to enter the full path:

\Program Files\MySQL\MySQL Server 5.6\bin

If migrationdata<version>_mysql.sql is not in the same folder as your command prompt, either move it to that folder, navigate to that folder in the command window, or provide the full path to the file.

Repeat the above steps to import standarddata<version>_mysql.sql for each additional deployment schema/database you are migrating. Keep the command window open for the next steps.

3 On the migration computer, install the target version of aPriori in the same manner you would install any other version. These are the exceptions from default when installing.

• Change the name of the installation from the default of apriori to also include the version (for example, apriori2016R1).

• Make sure you point it to the new database you just created and to which you imported the file.

4 Allocate additional memory. Most databases require additional memory beyond the default of 1280Mb. To do this, edit the file <apriori_install>\ext\migration-import-plugin\plugin.properties. Find the line towards the bottom of the file: launcher.max.memory=2048m. Change 2048 to 4096, then save and close the file.