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.
相关文章
target\surefire-reports for the individual test results
target\surefire-reports for the individual test results
761 0
|
2月前
|
Kubernetes Unix 容器
As the default settings are now deprecated, you should set the endpoint inste
As the default settings are now deprecated, you should set the endpoint inste
|
4月前
|
JavaScript
error Component name “Login“ should always be multi-word vue/multi-word-component-names【已解决】
error Component name “Login“ should always be multi-word vue/multi-word-component-names【已解决】
221 1
|
5月前
|
JavaScript
解决报错did you register the component correctly? For recursive components, make sure to provide the “na
解决报错did you register the component correctly? For recursive components, make sure to provide the “na
|
5月前
|
SQL 关系型数据库 MySQL
[已解决]ERROR tool.ExportTool: Error during export: Export job failed!
[已解决]ERROR tool.ExportTool: Error during export: Export job failed!
145 0
|
10月前
Error: Plugin/Preset files are not allowed to export objects, only functions……
Error: Plugin/Preset files are not allowed to export objects, only functions……
913 error Component name “home“ should always be multi-word vuemulti-word-component-names
913 error Component name “home“ should always be multi-word vuemulti-word-component-names
95 0
|
Shell
Detected problems with app native libraries (please consult log for detail): lib.so: text relocation
Detected problems with app native libraries (please consult log for detail): lib.so: text relocation
155 0
|
开发工具
Flutter ServicesBinding.defaultBinaryMessenger was accessed before the binding was initialized.
Flutter ServicesBinding.defaultBinaryMessenger was accessed before the binding was initialized.
296 0
how does gateway framework treat default system flag in customizing
Suppose we have maintain multiple backend system as “default” in customizing:
130 0
how does gateway framework treat default system flag in customizing