Oracle (1) Database 10g Administration Workshop I

https://support.oracle.com/CSP/main/article?cmd=show&type=NO...
How to Perform a Full Database Export Import during Upgrade, Migrate, Copy, or Move of a Database [ID 286775.1]
Modified 17-AUG-2011 Type BULLETIN Status PUBLISHED
PURPOSE
-------
This article describes how to run a full database export on a source
database and how to import the export dumpfile into a target database.
SCOPE & APPLICATION
-------------------
The article is intended for the Database Administrator of the Oracle7,
Oracle8, Oracle8i, Oracle9i, and Oracle10g databases who wish to use
the EXPORT and IMPORT utilities to perform a full database export from
an Oracle database release x and import this data with a full database
import into an Oracle database release y.
The steps provided in this article do not apply to the export and import
or Oracle Applications databases, nor to the export and import of the
Portal Database schema's. See the references at the end of this document
for links to documents that describe the steps for those databases.
HOW TO PERFORM A FULL DATABASE EXPORT IMPORT DURING UPGRADE, MIGRATE,
=====================================================================
COPY, OR MOVE OF A DATABASE
===========================
Introduction.
-------------
1. For information about the concepts how the Oracle export and import
Rate this document
utilities can be used to transfer data, schemas, tablespaces, databases
across platforms and across 32-bit/64-bit processor servers, see:
Note:277650.1 "How to Use Export and Import when Transferring Data Across
Platforms or Across 32-bit and 64-bit Servers"
2. When migrating or upgrading a database, ensure that you have read the
referenced notes at the bottom of this article.
3. All the queries mentioned below, are based on a connection in SQL*Plus:
% sqlplus /nolog
SQL> CONNECT system/manager
SQL> SET lines 200
TARGET DATABASE
---------------
1. If there are any other Oracle databases already installed on the target
machine, issue a clean shutdown of those databases (SHUTDOWN IMMEDIATE),
and create a full database backup of those databases. This ensures that
1 of 5 01/25/2012 05:07 PM
if anything goes wrong during the full database import (e.g. ORACLE_SID
was set to the wrong database by mistake), you can restore that database
from this backup.
2. On the target machine, install the Oracle software. To eliminate any known
issues during the full database import and for which a fix already exists,
it is recommended to apply the latest patchset in this $ORACLE_HOME.
For a summary of the latest Oracle Server releases, see:
Note:161818.1 "Oracle Server (RDBMS) Releases Support Status Summary"
See the README file of the patchset how to install the patchset and
how to run the required post-installation steps. See also:
Note:176311.1 "Good practices applying patches and patchsets"
SOURCE DATABASE
---------------
2. To eliminate any known issue during the full database export and for
which a fix already exists, it is recommended to apply the latest patchset
in the $ORACLE_HOME of the source database.
For a summary of the latest Oracle Server releases, see:
See the README file of the patchset how to install the patchset and
how to run the required post-installation steps. See also:
3. In the source database, check which options were installed:
- Oracle Text - schema: CTXSYS
- Oracle OLAP - schema: OLAPSYS
- Oracle Spatial - schema: MDSYS
- Oracle Data Mining - schema: DMSYS
- Oracle Ultra Search - schema: WKSYS
- Oracle Label Security - schema: LBACSYS
- Oracle JVM ? - object_types: 'JAVA CLASS', 'JAVA DATA', 'JAVA RESOURCE'
- Oracle interMedia - schema: ORDSYS
- Oracle XML DB - schema: XDB
Possible ways to find out which options are in use:
- Oracle9i 9.2.0. and above: use the query:
SELECT SUBSTR(schema,1,10) schema, SUBSTR(comp_id,1,10) comp_id, status,
SUBSTR(version,1,10) version, SUBSTR(comp_name,1,35) comp_name
FROM dba_registry ORDER BY 1;
- use the Database Configuration Assistant (modify database)
- run queries:
SELECT username FROM dba_users WHERE username IN ('CTXSYS', 'OLAPSYS',
'MDSYS', 'DMSYS', 'WKSYS', 'LBACSYS', 'ORDSYS', 'XDB');
SELECT object_type, COUNT(*) FROM dba_objects
WHERE object_type LIKE 'JAVA%' GROUP BY object_type;
4. In the source database, check the characterset of the database:
SELECT * FROM nls_database_parameters
WHERE parameter LIKE '%SET' ORDER BY 1;
5. In the source database, check which users can connect AS SYSBDA:
SELECT * FROM v$pwfile_users;
TARGET DATABASE
---------------
2 of 5 01/25/2012 05:07 PM
6. On the target machine, determine what the characterset should be for
the database. If the database characterset does not need to be changed,
use the same characterset. See also step 4 above, and:
Note:77441.1 "Steps to Create a New Database With a Character Set
Other Than US7ASCII"
7. For Oracle9i and higher, determine how the undo management should take
place: Manual, or Automatic. See also:
Note:135090.1 "Managing Rollback/Undo Segments in AUM (Automatic
Undo Management)"
8. For Oracle8i and higher, determine how the space management in the
tablespaces should take place. For Oracle9i and higher, it is recommended
to use locally managed tablespaces. See also:
Note:105120.1 "Advantages of Using Locally Managed vs Dictionary Managed
Tablespaces"
9. On the target machine, create a new parameter file with the initialization
parameters. For Oracle9i and higher, determine whether the initialization
parameters should be stored in the old-style pfile (init.ora) or in the
new style server parameter file (spfile). For details, see:
Note:249664.1 "Pfile vs SPfile"
10. On the target machine, create the new target database with the Database
Configuration Assistant. When using the Database Configuration Assistant
(dbca), you can specify which options need to be installed. Choose the
same options that were installed in the source database, unless you are
absolutely sure that although the option was installed in the source
database, it was not used (see also step 3 above).
It is also possible to create the new database with an existing script
file or with a script file that you created yourself. In that case,
ensure that this script file calls all the other scripts that are required
to to add the options and components that are needed in this target
database.
11. When using the old-style (pre-Oracle9i) manual undo management
(see step 7 above), create an extra rollback segment in the SYSTEM
tablespace and put it online. For details, see:
Note:112479.1 "ORA-01552 Error Creating a Rollback Segment in a Locally-
Managed Tablespace"
12. Check whether all objects in the target database are valid:
SELECT status, object_id, object_type, owner||'.'||object_name
"OWNER.OBJECT"
FROM dba_objects WHERE status != 'VALID' ORDER BY 4,2;
If there are invalid objects, recompile them. For details, see also:
Note:213600.1 "How to Compile Invalid Objects in SYS Schema after
RDBMS 8.0"
13. For Oracle9i Release 2 (9.2.0) and higher release databases, check
the status of the data dictionary:
SELECT SUBSTR(comp_id,1,15) comp_id, status, SUBSTR(version,1,10) version,
SUBSTR(comp_name,1,30) comp_name
FROM dba_registry ORDER BY 1;
Ensure that data dictionary components such as CATALOG and CATPROC
have the same version as the version of the Oracle executable:
SELECT * FROM v$version;
3 of 5 01/25/2012 05:07 PM
RELATED DOCUMENTS
-----------------
Note:277650.1 "How to Use Export and Import when Transferring Data
Across Platforms or Across 32-bit and 64-bit Servers
Note:133920.1 "Complete Upgrade Checklist for Manual Upgrades from 8.x to
8.x"
Note:159657.1 "Complete Upgrade Checklist for Manual Upgrades from 8.X /
9.0.1 to Oracle9i"
Note:204015.1 "Export/Import Process for Oracle Applications Release 11i
Database Instances"
Note:230627.1 "9i Export/Import Process for Oracle Applications Release 11i"
Note:228516.1 "How to copy (export/import) Portal database schemas of IAS
9.0.2 to another database"
Other referenced documents:
Note:77441.1 "Steps to Create a New Database With a Character Set Other
Than US7ASCII"
Note:105120.1 "Advantages of Using Locally Managed vs Dictionary Managed
Tablespaces"
Note:249664.1 "Pfile vs SPfile"
Note:213600.1 "How to Compile Invalid Objects in SYS Schema after RDBMS 8.0"
Note:112479.1 "ORA-01552 Error Creating a Rollback Segment in a Locally-
Managed Tablespace"
Related
Products
Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Enterprise Edition
Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Personal Edition
Oracle Database Products > Oracle Database > Oracle Database > Oracle Server - Standard Edition
Keywords
EXPORT; IMPORT; INVALID OBJECT; JAVA CLASSES; DYNAMIC ADV USE
Errors
ORA-1552; 01552 ERROR
Back to top
4 of 5 01/25/2012 05:07 PM
Copyright (c) 2007, 2010, Oracle. All rights reserved. Legal Notices and Terms of Use | Privacy Statement
5 of 5 01/25/2012 05:07 PM

Oracle (1) Database 10g Administration Workshop I

Enviado por

Dados do documento

Título original

Direitos autorais

Formatos disponíveis

Compartilhar este documento

Compartilhar ou incorporar documento

Opções de compartilhamento

Você considera este documento útil?

Este conteúdo é inapropriado?

Direitos autorais:

Formatos disponíveis

Oracle (1) Database 10g Administration Workshop I

Enviado por

Direitos autorais:

Formatos disponíveis

https://support.oracle.com/CSP/main/article?cmd=show&type=NO...

Você também pode gostar