How to perform FULL System Export/Imports
A Full System Export and Import is a useful way to replicate or clean up a database. Please note the following guidelines when performing a Full System Export and Import:
1. When performing the import, ensure you are pointing at the correct instance. Always check values for the SID and two task driver before proceeding.
*Note: On Unix systems, just entering a sub-shell, such as using C-shell, can change the database that the import would work against.
2. When possible, it is advisable to take a physical copy of the exported database and the database you intend to import into before starting the import. This ensures any mistakes are reversible.
3. *NEVER* run a FULL SYSTEM IMPORT on a machine that has more than one database UNLESS you are 100% sure all tablespaces have been pre-created. A full import will create any undefined tablespaces using the same datafile names as the exported database. There are situations where this is very dangerous:
-> If the datafiles belong to ANY other database, they will be CORRUPTED. This is especially true if the exported database is on the same machine, because its datafiles will be re-used by the database you are importing into.
-> If the datafiles have names that clash with existing operating system files.
4. When exporting, it is advisable to also produce a report showing information you may need before / after the import:
-> List the tablespaces and datafiles
-> List the rollback segments (in case of using Manual Undo Management)
-> List a count, by user, of each object type such as tables, indexes, etc.
This enables you to ensure that tablespaces have been pre-created and to check the success of the import after it is complete.
5. If you are creating a completely new database from an export and you are using Manual Undo Management, remember to create an extra rollback segment in SYSTEM, and make this available in the init.ora file before proceeding with the import.
6. There are some versions of export that do not retain sequence numbers correctly. It is advisable to select next_value for each sequence after the export so that these can be checked after import.
1. When performing the import, ensure you are pointing at the correct instance. Always check values for the SID and two task driver before proceeding.
*Note: On Unix systems, just entering a sub-shell, such as using C-shell, can change the database that the import would work against.
2. When possible, it is advisable to take a physical copy of the exported database and the database you intend to import into before starting the import. This ensures any mistakes are reversible.
3. *NEVER* run a FULL SYSTEM IMPORT on a machine that has more than one database UNLESS you are 100% sure all tablespaces have been pre-created. A full import will create any undefined tablespaces using the same datafile names as the exported database. There are situations where this is very dangerous:
-> If the datafiles belong to ANY other database, they will be CORRUPTED. This is especially true if the exported database is on the same machine, because its datafiles will be re-used by the database you are importing into.
-> If the datafiles have names that clash with existing operating system files.
4. When exporting, it is advisable to also produce a report showing information you may need before / after the import:
-> List the tablespaces and datafiles
-> List the rollback segments (in case of using Manual Undo Management)
-> List a count, by user, of each object type such as tables, indexes, etc.
This enables you to ensure that tablespaces have been pre-created and to check the success of the import after it is complete.
5. If you are creating a completely new database from an export and you are using Manual Undo Management, remember to create an extra rollback segment in SYSTEM, and make this available in the init.ora file before proceeding with the import.
6. There are some versions of export that do not retain sequence numbers correctly. It is advisable to select next_value for each sequence after the export so that these can be checked after import.
來自 “ ITPUB部落格 ” ,連結:http://blog.itpub.net/22664653/viewspace-688797/,如需轉載,請註明出處,否則將追究法律責任。
相關文章
- How to Perform a Healthcheck on the DatabaseORMDatabase
- How to Perform a Health Check on the DatabaseORMDatabase
- How to Perform SQL Server Log ShippingORMSQLServer
- ORA-31633: unable to create master table "SYSTEM.SYS_EXPORT_FULL_XX"ASTExport
- full database export and import(實戰)DatabaseExportImport
- Oracle 12c full transportable export & importOracleExportImport
- [ISSUE]how to perform unit testing in J2EE enviornment?ORM
- 翻譯|How to Export a Connected ComponentExport
- 【轉載-ORACLE】ORA-6512 During Full ExportOracleExport
- Oracle 10.2.0.1 exp 之 full database export and import(實戰)OracleDatabaseExportImport
- 【健康檢查】How to Perform a Health Check on the Database (Doc ID 122669.1)ORMDatabase
- View and Data API Tips: how to make viewer full screenViewAPI
- How To Export a Concurrent Program and Executable Using Fndload ?Export
- How to get and set the system socket buffer in AIXAI
- 完全可傳輸的匯出/匯入(full transportable export/import)ExportImport
- Oracle OCP 1Z0-053 Q513(how to perform tablespace point-in-time recovery)OracleORM
- Oracle 12c 使用(Full Transportable Export/Import)進行升級/遷移OracleExportImport
- HDD Drilling Mud Cleaning System export to South KoreaExport
- Minimum Requirements to Use Export DataPump and IMP(System Privileges)_351598.1UIREMExport
- HTML imports 入門HTMLImport
- How to copy a datafile from ASM to a file system not using RMANASM
- How does the system determine the quantity structure for the cost estimate (CK11N)?Struct
- 【Scala】Scala之Packaging and ImportsImport
- @EXPORT and @EXPORT_OKExport
- [譯] 什麼是 WebAssembly table importsWebImport
- How to Clean Up Duplicate Objects Owned by SYS and SYSTEM Schema_1030426.6Object
- export 和 export default 區別Export
- ORA-20010: INTERNAL ERROR: dumped min/max is null for table EXP.SYS_EXPORT_FULL_01ErrorNullExport
- exportExport
- JavaScript中的export、export default、exports和module.exports(export、export default、exports使用詳細)JavaScriptExport
- export和export default的區別Export
- export ORACLE_SID=founder exportExportOracle
- How To Restore 12cR1DB to New Host File System using RMAN(一)REST
- How to Restore CRS after accidentally run localconfig on RAC system_747415.1RESTIDE
- How to set up Software raid1 configuration on a running systemAI
- Index Full Scan vs Index Fast Full ScanIndexAST
- Index Full Scans和Index Fast Full ScansIndexAST
- Index Full Scan 與 Index Fast Full ScanIndexAST