This document explains how to move an Ignite Repository from one Oracle database to another.  This document assumes:

- you are running Ignite 4.3 or higher.

- the new Repository database has already been created and is accessible from the Ignite PI Server.

1. Shutdown the Ignite PI Server
   a. Windows – stop the Ignite PI Server service
   b. Linux / Unix – run shutdown.sh
   c. Linux / Unix – Ensure there are no crontab entries that will automatically restart Ignite

2. Export the schema holding the Ignite Repository.  Type the following command (all on one line):

   exp <ignite_username>/<ignite_password>@<database> file=ignite_repo.dmp owner=<ignite_username> grants=Y buffer=2000000

3. Create a schema in the new Repository database using any username/password you like.

   Note: You may wish to create an Ignite tablespace to hold the Ignite data in the new Repository.

   SQL> create user <ignite_username> identified by <password> default tablespace <ignite_tbsp>;
   SQL> grant dba to <ignite_username>;

4. Import the Repository data (from previous step) into the new database.  Type the following command (all on one line):

   imp <ignite_username>/<ignite_password>@<database> file=ignite_repo.dmp full=Y buffer=2000000

5. Update the repository database information in the repo.properties file on the Ignite PI Server to point to the new Ignite repository
   a. Windows – By default, located in C:\Program Files\Confio\Ignite PI\iwc\tomcat\ignite_config\idc
   b. Linux / Unix – Located in <IgniteHome>/iwc/tomcat/ignite_config/idc
   c. Modify the following lines as needed:
        repo.serviceName=
        repo.port=
        repo.user=
        repo.host=
        repo.password=<type the password in clear text and Ignite will encrypt it>
        repo.name=<Display name for repository, typically username@reponame>

6. Start the Ignite PI Server and open the Ignite GUI interface
   a. Ensure the PI Server connects to the proper repository database.
   b. Review the status of monitors and start / stop accordingly.
   c. Review Ignite log entries for obvious errors.

7. Test to ensure the move is successful
   a. Wait at least 10 minutes and drill into several databases
   b. Does data for the last 10 minutes appear for all monitored databases?

8. Connect to the old Repository Instance as a DBA user and remove the old repository:

   SQL> drop user <ignite_username> cascade;