Segment Metadata Move Space. Start Db Oracle Database. Installation of the database software. Installation of the software patch. Oracle Database - Installation.
Download the installation file : Oracle Database 10g Release 2 Download the last patch on Metalink. Set this variable to point to the host name of the computer on which you are installing Oracle Database.
One or both values can be specified. If it is not specified, then the registry is checked for the current setting. This is an optional parameter. If you do not specify how to stop an instance, then normal is the default mode. You can edit an existing instance to change such values as instance name, startup mode, shutdown mode, and shutdown type. To specify a new initialization parameter file for the instance prod , for example, you can enter:. Migrating an Oracle Database 10 g Release 2 Migrating an Oracle Database 10 g Release 1 Create a.
To migrate an Oracle Database 10 g Release 2 Create the new Oracle Database 10 g Release 2 If you have a password file that resides in the bit Oracle home, then copy the password file to the bit Oracle home. Edit the trace file created in "Backing Up a Bit Oracle Database" to change the paths to the datafiles, log files and control files to point to the Oracle home on the bit computer. Here is an example of a database named "orcl32" on a bit computer migrating to "orcl64" on a bit computer:.
Alter the init file from the bit computer to include the new control file generated in the preceding step. You might need to use the PFILE option to specify the location of your initialization parameter file. Check the spool file and verify that the packages and procedures compiled successfully.
Correct any problems you find in this file. To migrate an Oracle Database 10 g Release 1 Perform steps 1 - 11 in "Migrating an Oracle Database 10 g Release 2 Naming Conventions for Oracle Database All mounted Oracle Database servers in a network must have unique database names. If you specified non-OFA directories during installation, then your directory paths will differ.
Database creations are of three types: Copy an existing database and delete the old database. Copy an existing database and keep the old database.
Create a new database when no database exists on your system. Exporting an Existing Database You are required to export an existing database only if you intend to copy its contents to a new database.
Note: If you use parameter mode, then Data Pump Export considers filenames and directory names to be invalid if they contain one or more blank spaces. Note: If you use parameter mode, then Export considers filenames and directory names to be invalid if they contain one or more blank spaces.
Deleting Database Files Deleting database files is required only when you copy an existing database to a new database to replace the old database.
Note: Beginning with Oracle9 i release 2 9. This may affect how Oracle Database interprets parameter values in your initialization parameter file.
Starting with release 9. See Also: Oracle Database Reference for information on other initialization parameters that you can add or modify. Starting an Oracle Database Instance Start an instance without mounting a database. Creating and Starting an Oracle Database Service You are required to create and start an Oracle Database service only if you do one of the following: Copy an existing database to a new database and keep the old database Create a new database when you have no other database to copy Before you create the database, first create a Windows service to run the database.
Oracle-managed files eliminates the requirement to directly manage operating system files comprising an Oracle Database server, because you specify operations in terms of database objects rather than filenames. Note: If you use parameter mode, then Data Pump Import considers filenames and directory names to be invalid if they contain one or more blank spaces. Note: If you use parameter mode, then Import considers filenames and directory names to be invalid if they contain one or more blank spaces.
Note: If the original database from which the export file was generated contains a tablespace that is not in the new database, then Import tries to create that tablespace with associated datafiles. See Also: Chapter 14, "Configuration Parameters and the Registry" for more information on subkey locations for multiple Oracle homes.
Backing Up the New Database Caution: If anything goes wrong while operating the new database without a backup , then you must repeat the database creation procedure. Back up your database now to prevent loss of data. Caution: Although ORADIM returns the prompt immediately, you must wait for the database and the service to stop completely before continuing to Step 2. If you do not do this, then the backup may be useless because it was taken while data was being written to datafiles.
Caution: Do not store database files on a compressed drive. This can result in write errors and decreased performance. See Also: Your operating system documentation for instructions on starting services.
Editing an Instance You can edit an existing instance to change such values as instance name, startup mode, shutdown mode, and shutdown type. If you do not specify it, then operating system authentication is used, and no password is required. Ensure that you specify the full path name with the -PFILE option, including drive letter of the Oracle home directory.
All rights reserved. Creating Directories. It is recommended that a second copy of the control file is available so an instance can be easily restarted after copying the good control file to the location of the bad control file. The default value is 4. When the Chicago database is running in the standby role, it uses the Boston database as the FAL server from which to fetch request missing archived redo log files if Boston is unable to automatically send the missing log files.
This parameter converts the path names of the primary database datafiles to the standby datafile path names. If the standby database is on the same system as the primary database or if the directory structure where the datafiles are located on the standby site is different from the primary site, then this parameter is required. Note that this parameter is used only to convert path names for physical standby databases.
Multiple pairs of paths may be specified by this parameter. This parameter converts the path names of the primary database log files to the path names on the standby database. If the standby database is on the same system as the primary database or if the directory structure where the log files are located on the standby system is different from the primary system, then this parameter is required.
Caution: Review the initialization parameter file for additional parameters that may need to be modified. In addition, you may have to create directories on the standby system if they do not already exist.
Step 1 Copy the primary database parameter file to the standby database. This name stays with the database and does not change even if the primary and standby databases reverse roles.
When the Boston database is running in the standby role, it uses the Chicago database as the FAL server from which to fetch request missing archived redo log files if Chicago is unable to automatically send the missing log files. Step 1 Create a Windows-based service. Step 2 Create a password file. Step 4 Create Oracle Net service names.
Step 5 Create a server parameter file for the standby database. Step 1 Start the physical standby database. Step 3 Test archival operations to the physical standby database. Step 1 Identify the existing archived redo log files. Step 2 Force a log switch to archive the current online redo log file. The archived redo log files are now available to be applied to the physical standby database. Step 4 Verify new archived redo log files were applied.
The following list describes additional preparations you can take on the physical standby database: Upgrade the data protection mode The Data Guard configuration is initially set up in the maximum performance mode the default. Enable Flashback Database Flashback Database removes the need to re-create the primary database after a failover. All rights reserved. Book List. Master Index. Contact Us. Section 3. Enable Forced Logging. Create a Password File.
Configure a Standby Redo Log. Set Primary Database Initialization Parameters. Enable Archiving. Specify an 8-character name. Specify a unique name for each database. Specify the path name for the control files on the primary database.
Specify where the redo data is to be archived on the primary and standby systems. Set the same password for SYS on both the primary and standby databases. Specify the maximum number from 1 to 30 of archiver ARC n processes you want Oracle software to invoke initially. Specify the Oracle Net service name of the FAL server typically this is the database running in the primary role. Specify the Oracle Net service name of the Chicago database.
Specify the path name and filename location of the primary database datafiles followed by the standby location. Specify the location of the primary database online redo log files followed by the standby location. Set to AUTO so when datafiles are added to or dropped from the primary database, corresponding changes are made automatically to the standby database. Create a Control File for the Standby Database.
Start the Physical Standby Database. Specify a unique name for this database. Specify the path name for the control files on the standby database.
0コメント