----------------
EXPORTING DATA
----------------
To create an Oracle Export file that contains all of the CampaignMax data, follow these instructions:
1. Before starting you must have the following:
a. The SYS or SYSTEM user's password on the target system. (default is MANAGER)
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. (default name is CampMgr)
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. Click on Run and type CMD (this will take you to the C: Prompt)
b. Issue the following at a OS command line: (Be sure that the command line is the location of the file i.e. C:\Douglas\Data\Campmgr)
CMD> EXP system/manager file=dumpfilename.dmp consistent=Y owner=campmgr
----------------
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. (default is MANAGER)
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 CampMgr.
d. The name of the tablespaces that contain the data in the Export file. The default is CampMgr_Data and CampMgr_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.
TO BEGIN: Click on RUN and type CMD. You must then start SQL Plus
with the following commands (keep SQL Plus active for instructions
2-5):
a. Start SQL*Plus.
CMD> sqlplus /nolog
b. Connect to the target Oracle system as SYS or SYSTEM.
SQL> connect system/manager
2. Create the tablespaces on the target system:
a. Issue this SQL command:
SQL> CREATE TABLESPACE CampMgr_Data
DATAFILE 'C:\Douglas\Data\CampMgr_Data.dbf'
SIZE 200M AUTOEXTEND ON;
b. Issue this SQL command:
SQL> CREATE TABLESPACE CampMgr_Index
DATAFILE 'C:\Douglas\Data\CampMgr_Index.dbf'
SIZE 100M AUTOEXTEND ON;
3. If the user exists on the target system, you must delete that user:
a. Issue this SQL command:
SQL> DROP USER CampMgr CASCADE;
4. Create the user on the target system:
a Issue this SQL command:
SQL> CREATE USER CampMgr
IDENTIFIED BY password
DEFAULT TABLESPACE CampMgr_Data
QUOTA UNLIMITED ON CampMgr_Data
QUOTA UNLIMITED ON CampMgr_Index;
5. Grant basic rights to the user:
a. Issue this SQL command:
SQL> GRANT CONNECT, RESOURCE TO CampMgr;
6. Import the data:
a. Issue the following at a OS command line(be sure that you are at the C: Prompt. To do this type cd c:\and the file locations):
CMD> IMP system/manager file=dumpfilename.dmp fromuser=campmgr touser=campmgr
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" (default is CampMgr) 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.