----------------
EXPORTING DATA
----------------
To create an Oracle Export file that contains all of the CampaignMax demo data, follow these instructions:

1. Before starting you must have the following:
a. The SYS or SYSTEM user's password on the target system.
b. You must be able to login to the target system as SYS or SYSTEM using SQL*Plus.
c. The name of the Oracle schema (username) that contains the CampaignMax data. The default name is DEMO.

NOTE: The remaining instructions use the default names indicated above. If your names are different, you will have to substitute the correct names in the commands given below.

2. Export the data:
a. Issue the following at a OS command line:
EXP system/manager file=dumpfilename.dmp consistent=Y owner=demo

----------------
IMPORTING DATA
----------------
If you have an Oracle Export file that contains CampaignMax data, these instructions will help you import that data into an Oracle database.

1. Before starting you must have the following:
a. The SYS or SYSTEM user's password on the target system.
b. You must be able to login to the target system as SYS or SYSTEM using SQL*Plus.
c. The name of the Oracle schema (username) that contains the CampaignMax data in the Export file. The default name is DEMO.
d. The name of the tablespaces that contain the data in the Export file. The default is Demo_Data and Demo_Index.
e. The size of the tablespaces. Generally, 100-200M is sufficient for the CampMgr_Data tablespace and half that is required for the CampMgr_Index tablespace.
f. The location of the tablespaces on the target system. The default is C:\Douglas\Data.

NOTE: The remaining instructions use the default names indicated above. If your names are different, you will have to substitute the correct names in the commands given below.

2. Create the tablespaces on the target system:
a. Start SQL*Plus.
b. Connect to the target Oracle system as SYS or SYSTEM.
c. Issue this SQL command:
CREATE TABLESPACE Demo_Data
DATAFILE 'C:\Douglas\Data\Demo_Data.dbf'
SIZE 200M AUTOEXTEND ON;
d. Issue this SQL command:
CREATE TABLESPACE Demo_Index
DATAFILE 'C:\Douglas\Data\Demo_Index.dbf'
SIZE 100M AUTOEXTEND ON;
e. Issue this SQL command:
CREATE TABLESPACE TrainMgr_Data
DATAFILE 'C:\Douglas\Data\TrainMgr_Data.dbf'
SIZE 200M AUTOEXTEND ON;
f. Issue this SQL command:
CREATE TABLESPACE TrainMgr_Index
DATAFILE 'C:\Douglas\Data\TrainMgr_Index.dbf'
SIZE 100M AUTOEXTEND ON;

3. If the target user exists on the target system, you must delete that user:
a. Start SQL*Plus.
b. Connect to the target Oracle system as SYS or SYSTEM.
c. Issue this SQL command:
DROP USER TrainMgr CASCADE;

4. Create the user on the target system:
a. Start SQL*Plus.
b. Connect to the target Oracle system as SYS or SYSTEM.
c. Issue this SQL command:
CREATE USER TrainMgr
IDENTIFIED BY password
DEFAULT TABLESPACE TrainMgr_Data
QUOTA UNLIMITED ON Demo_Data
QUOTA UNLIMITED ON Demo_Index
QUOTA UNLIMITED ON TrainMgr_Data
QUOTA UNLIMITED ON TrainMgr_Index;

5. Grant basic rights to the user:
a. Start SQL*Plus.
b. Connect to the target Oracle system as SYS or SYSTEM.
c. Issue this SQL command:
GRANT CONNECT, RESOURCE TO TrainMgr;

6. Import the data:
a. Issue the following at a OS command line:
IMP system/manager file=dumpfilename.dmp fromuser=demo touser=trainmgr

NOTE: The import should "terminate successfully with warnings". You should see many CampaignMax tables listed with "nnn rows imported" after their name. You will also probably receive numerous warning messages. Do not let these alarm you. We are simply importing the "raw" data in this step. The next step will clean everything up in the Oracle database.

7. Run the CampaignMax Database Update Utility.

8. Login to CampaignMax as the "owner" (our example used TrainMgr) and create user accounts. These are not transferred by the Oracle Import utility.

9. Login to CampaignMax as one of the users you just created. Check the data to be sure it converted correctly.