Upgrade Oracle from 10.2.0.1 To 10.2.0.4. PLSQL: Oracle System Tables. Stopping Processes in Oracle RAC Databases and Performing Oracle Clusterware Rolling Upgrades. This appendix describes how to stop processes in an Oracle Real Application Clusters (Oracle RAC) database, for one of the following two scenarios: Scenario One: Stopping processes in an entire database, in preparation for adding additional products to an existing database, or in preparation for patch updates. Scenario Two: Stopping processes on selected nodes in a database, in preparation for performing a rolling upgrade of Oracle Clusterware from any 10.2 installation to the latest patch update; for example, you can perform a rolling upgrade from 10.2.0.1 to 10.2.0.3. Note: For all command lines, Oracle_home represents the Oracle home path on your system, CRS_home represents the Oracle Clusterware home path on your system, and SID represents the Oracle system identifier (or name) of the database instance.
This appendix contains the following topics: Back Up the Oracle Software Verify System Readiness for Patches and Upgrades See Also: Oracle Database Upgrade Guide Stop All Oracle Processes. Oracle Export and Import Utility. These tools are used to transfer data from one oracle database to another oracle database. You Export tool to export data from source database, and Import tool to load data into the target database. When you export tables from source database export tool will extracts the tables and puts it into the dump file. This dump file is transferred to the target database. At the target database the Import tool will copy the data from dump file to the target database. From Ver. 10g / 11g Oracle is recommending to use Data Pump Export and Import tools, which are enhanced versions of original Export and Import tools. The export dump file contains objects in the following order: Type definitions Table definitions Table data Table indexes Integrity constraints, views, procedures, and triggers Bitmap, function-based, and domain indexes Invoking Export and Import You can run Export and Import tool in two modes Command Line Mode Interactive Mode Command Line Parameters of Export tool USERID username/password.
Importing into Oracle tutorial. Brian Peasland: This is a pretty common procedure, which isn't too hard to accomplish. So here is a step-by-step guide. Export the entire schema from production: exp userid=system file=user_a.dmp log=user_a.log owner=a FTP the dump file (in BINARY mode) to the development server. Make sure user B exists in your development instance. Run this command: imp userid=system file=user_a.dmp log=imp.log fromuser=a touser=b The only big sticking point is that user B may have a different default tablespace than user A, if user A exists.
Brian Peasland: You can do this a few ways. If you are not using 9i, or do not wish to use this method, then you can use the UTL_FILE supplied package. Karen Morton: You can run imports of the same dump file multiple times BUT you must make sure that if you do, you do it in such a way as to not create duplicates or attempt to "re-do" work you accomplished in a previous import.
I would stay away from LONG RAWS since they are more restrictive and will be desupported soon.