Preconditions for the migration

1. Make note of the database parameters by filling in the user database checklist (Table 2.    User database parameters checklist.).
2. Make sure the Oracle command line programs sqlplus, exp and imp are in your path.

1. You can check if the oracle configuration is already in use by running:

> env|grep ORACLE

If the system gives output, the command line programs are available. Otherwise the Oracle configuration is needed to take in use. For that, the oraenv installation path in the system is needed. It is generally located under $ORACLE_HOME/bin, but contact the Oracle system administrator if needed.

2. Run the oraenv script in the new environment:

> source [$ORACLE_HOME/bin/]oraenv

3. If a SID is requested, enter the base name of the database server (for example DEVELDB) or leave the default.

3. Make sure that Kronodoc users exist in the AD before performing the migration. Obtain a list of users from Kronodoc and verify that users with the same usernames exist in AD. In case users exist in Kronodoc but not in AD, create them manually in AD. This holds especially true for superusers and sysadmins defined in the configuration file KRONO/conf/env.pm If these users do not exist in AD the migration script will fail with the following error message:
   
   1. Testing ActiveDirectory connection : # Failed test 9 in ../test/test.pm at line 529 fail #9

Note: If a username of a normal user does not exist in AD, the information items that refer to the user will be mapped to internal IDs. However, only users that exist in AD can be used in Kronodoc after the migration. Superusers and sysadmins must exist in AD prior to migration.

4. If removal of users is needed, decide on the Kronodoc username that gets to own all documents and folders that the user-to-be-removed owned. This user will be referenced as the default user. The user should exist both in Kronodoc and AD.