Beruflich Dokumente
Kultur Dokumente
MetricStream, Inc.
October August 2004
Copyright Notices
2004 Metric Stream, Inc. All Rights Reserved.
The Database Export/Import Guide, as well as the software
described within it, is furnished under license and may only be
used or copied within the terms of that license. The information in
this manual is provided for informational purposes only, is subject
to change without notice, and should not be construed as a
commitment by MetricStream, Inc. MetricStream, Inc. assumes no
responsibility or liability for any errors or inaccuracies that may
appear in this book.
CAUTION
This document contains proprietary, confidential information that
is the exclusive property of MetricStream, Inc. If you do not have a
valid contract with MetricStream for the use of this document, or
have not signed a non-disclosure agreement with MetricStream,
then you received this document in an unauthorized manner and
are not legally entitled to possess or read it.
Change Record
Signatures
Steps to Export
1. Export the database as system/manager. From the DOS
prompt use the following command:
exp system/manager@dbname
For example, with the above mentioned assumptions we can use
the following expression
exp system/manager@devindia
5. Drop the user QMSGOLD (In case a user with the name
QMSGOLD already exists and the exported database has to be
imported into the same user/schema)
drop user QMSGOLD cascade;
6. Drop the tablespace (In case a tablespace already exists with
the same name and can be replaced with incoming imported
data.)
drop tablespace QMSGOLD_IDX including contents
cascade constraints;
drop tablespace QMSGOLD_DATA including contents
cascade constraints;
Note: If any other schema is sharing the same tablespace, it is
recommended not to use these drop statements. Dropping sub
tablespaces will result in other users/schemas losing the data.
7. Remove the data files from the location obtained in step #4.
Note: If any other schema is sharing the same tablespace, it is
recommended not to use step #6 and #7. Doing so will result in
other users/schemas losing the data.
8. Create tablespace for data file and index file
• Run the following command from sqlplus. This will execute the
file containing commands to create a data tablespace and
index tablespace.
@create_tablespace.sql;
5. Create user QMSGOLD (or another name that you wish to use)
• Run the following command from sqlplus. This will execute the
file containing commands to create a user
@create_user;
• While the script is running you will be asked some questions.
Please provide valid inputs for them.
• Yow will be asked to provide information for the following
1. Enter value for username : QMSGOLD (The username created
above. This user would become the MetricStream repository
userid.
2. Enter value for password: QMSGOLD (The password set for the
user created above.
3. Enter value for default tablespace name: QMSGOLD_DATA
(This would be the data tablespace name created in the
previous step.)
4. Enter temp tablespace name: temp (Usually is TEMP, check
with the DBA)
5. Enter value for tablespace_index: QMSGOLD_IDX
Note: You will not be asked for Default tablespace name and
tablespace_index if you are in the same SQLPLUS session.
• The newly created user needs dba privileges to do the import.
Run the following sql,
grant dba to QMSGOLD;
6. Logout of sqlplus
7. Import the DMP file as QMSGOLD. From the DOS Prompt use
the following command:
imp QMSGOLD/QMSGOLD@dbname.
For example, with the above assumptions we can use the following
expression: -
imp QMSGOLD/QMSGOLD@albdms2.
3. Login to sqlplus as –
sqlplus system/manager@devindia
4. Drop the user MYUSER (In case a user with the name MYUSER
already exists and the exported database has to be imported in
the same user/schema)
drop user MYUSER cascade;
7. Run
<INSTALLATION_DIRECTORY>\SYSTEMi\Systemi\database\alter
_seq.sql
8. Make sure there are no invalid objects or views by re-running
the query mentioned in step 2 above (if some objects are
invalid, check if there are any bugs with the same object by
recompiling the object (Alter <object_type>
<object_name> compile). If the object doesn’t get compiled,
contact MetricStream support).
9. If there are more invalid objects, Run
<INSTALLATION_DIRECTORY>\SYSTEMi\Systemi\database\db_u
pgrade_patch.sql once again to clear these out.