Change IP adress/hostname of Cluster Interconnect. Changing private hostname. Required Skills/Credentials: 2.1 Tasks for Preparing to Upgrade Oracle Database. In preparation for upgrading Oracle Database, you review the new features and determine the best upgrade path and. Build Your Own Oracle RAC 11g Cluster on Oracle Linux and iSCSI by Jeffrey Hunter. Learn how to set up and configure an Oracle RAC 11g Release 2 development cluster. KorayKey® – Blog RSS - Yaz. HPE – Storage. Why Choose a Hybrid-Everywhere Data Protection Strategy; HPE and Nimble Storage at Cloud Field Day. Oracle Database 11g Release 2 RAC On Linux 6.3 Using VirtualBox. In pre- 1. 1. 2 Oracle Clusterware, private hostname is recorded in OCR, it can not be updated. Generally private hostname is not required to change. Its associated IP can be changed. The only way to change private hostname is by deleting/adding nodes, or reinstall Oracle Clusterware. In 1. 1. 2 Grid Infrastructure, private hostname is no longer recorded in OCR and there is no dependancy on the private hostname. It can be changed freely in /etc/hosts. Changing private IPOn Unix/Linux systems, the interface names are generally assigned by the OS, and standard names vary by platform. For Windows systems,see additional notes below. Our example below shows currently interface eth. Starting with 1. 1g. R2, cluster. Simply shutdown Oracle Clusterware stack on the node where change required, make IP modification at OS layer (eg: /etc/hosts, OS network config etc) for private network, restart Oracle Clusterware stack will complete the task. Preparing to Upgrade Oracle Database. Before you upgrade Oracle Database, you must understand the requirements and recommendations. This chapter provides information and procedures for the pre- upgrade tasks, including installing the new Oracle software for the upgrade. Tasks for Preparing to Upgrade Oracle Database. In preparation for upgrading Oracle Database, you review the new features and determine the best upgrade path and method to use. Oracle recommends that you test the upgrade process and prepare a backup strategy. Complete the following tasks to prepare to upgrade your database: 2. ![]() Determine the Upgrade Path for Oracle Database. The path that you must take to upgrade to the latest release of Oracle Database 1. You may perform a direct upgrade to the new release if your current Oracle Database is release 1. You may directly upgrade from release 1. If your current Oracle Database is a release earlier than 1. Oracle Database to the latest release is not supported. In this case, you are required to upgrade to an intermediate release before upgrading to Oracle Database 1. For example, if the database from which you are upgrading is running Oracle Database 9i, then follow these steps: Upgrade release 9. Oracle Database Upgrade Guide 1. Release 2 (1. 0. 2). Upgrade Oracle Database 1. Release 2 (1. 0. 2. Oracle Database 1. Oracle Database Upgrade Guide, which is this book. Table 2- 1 contains the required upgrade path for each release of Oracle Database. Use the upgrade path and the specified documentation to perform an intermediate upgrade of your database before fully upgrading to Oracle Database 1. Table 2- 1 Examples of Upgrade Paths for Oracle Database 1. If your Current Release is: Then the Direct or Intermediate Upgrade Path is: 1. Direct upgrade is supported. Perform the upgrade using the current Oracle Database Upgrade Guide, which is this guide. Direct upgrade to Oracle Database 1. Solution: Upgrade to an intermediate Oracle Database release (that can be directly upgraded to release 1. Oracle Database 1. This does not include upgrading using Oracle Data Pump export/import. When upgrading to an intermediate Oracle Database release, follow the instructions in the intermediate release's documentation. Then, upgrade the intermediate release database to the new Oracle Database 1. Chapter 3, . However, Oracle offers several methods to fully upgrade your database that support the complexities of your enterprise. DBUA automates the upgrade process by performing all of the tasks normally performed manually. DBUA makes appropriate recommendations for configuration options such as tablespaces and redo logs. You can then act on these recommendations. In an Oracle Real Application Clusters (Oracle RAC) environment, DBUA does not upgrade all the databases per se; DBUA upgrades all the database files and configuration files on all nodes in the cluster. The Manual, Command- line Method for Upgrading Oracle Database. A manual upgrade consists of running SQL scripts and utilities from a command line to upgrade a database to the new Oracle Database release. While a manual upgrade gives you finer control over the upgrade process, it is more susceptible to error if any of the upgrade or pre- upgrade steps are either not followed or are performed out of order. Before the Upgrade. The following list provides a high- level summary of the manual upgrade steps: Analyze the database using the Pre- Upgrade Information Tool. The Pre- Upgrade Information Tool is a SQL script that is supplied with Oracle Database, and DBUA uses this tool as part of its upgrade process. Run the Pre- Upgrade Information Tool on the database you are upgrading. The Pre- Upgrade Information Tool displays warnings about possible upgrade issues with the database, and generates fixup scripts for you to use to address any issues. It also displays information about required initialization parameters for the new release of Oracle Database. Prepare the new Oracle home. Perform a backup of the database. Depending on the release of the database being upgraded, you might be required to perform additional pre- upgrade steps (adjust the parameter file for the upgrade, remove desupported initialization parameters and adjust initialization parameters that might cause upgrade problems). After the Upgrade. Review the upgrade spool log file and use the Post- Upgrade Status Tool, utlu. The Post- Upgrade Status Tool is a SQL script that is included with Oracle Database. You run the Post- Upgrade Status Tool in the environment of the new release. You can run the Post- Upgrade Status Tool any time after upgrading the database. The Export/Import Method for Migrating Data When Upgrading Oracle Database. Unlike DBUA or a manual command- line upgrade, the Oracle Data Pump Export and Import utilities physically migrate a copy of data from your current database to a new database in the new release. Data Pump Export and Import are recommended for higher performance and to ensure support for new datatypes. The new database must exist, or you must have created the database in the new Oracle home, before the contents of the export dump file(s) can be loaded. When importing data from an earlier release, the import utility of the new Oracle Database release makes appropriate changes to data definitions as it reads the export dump files from the earlier release. Note: If your database is earlier than Oracle Database release 1. Export and Import utilities to perform a full or partial export from your database, followed by a full or partial import into a new database for the upgraded Oracle Database. Export/Import can copy a subset of the data in a database, leaving the original database unchanged. The original Export utility is no longer being updated to support new datatypes. The Effects of Export/Import on Upgraded Oracle Databases. The Export/Import data migration method does not change the current database, which enables the database to remain available throughout the upgrade process. However, if a consistent snapshot of the database is required (for data integrity or other purposes), then the database must run in restricted mode or must otherwise be protected from changes during the export procedure. Because the current database can remain available, you can, for example, keep an existing production database running while the newly upgraded Oracle Database database is being built at the same time by Export/Import. During the upgrade, to maintain complete database consistency, changes to the data in the database cannot be permitted without the same changes to the data in the newly upgraded Oracle database. Most importantly, the Export/Import operation results in a completely new database. Although the current target database ultimately contains a copy of the specified data that you migrated, the upgraded database might perform differently from the original source database. For example, although Export/Import creates an identical copy of the database, other factors, such as disk placement of data and unset tuning parameters, might cause unexpected performance issues. Export/Import Benefits for Migrating Data for Oracle Database. Migrating data when upgrading Oracle Database using Export/Import has benefits, including compressing and restructuring the database for increased performance. Using Export/Import to migrate data: Defragments the data. You can compress the imported data to improve performance. Restructures the database. You can create new tablespaces or modify existing tables, tablespaces, or partitions to be populated by imported data. Facilitates side- by- side testing of the old and new releases of Oracle Database because an entirely new database is created. Enables the copying of specified database objects or users. Importing only the objects, users, and other items you need is useful for establishing a test environment for the new software on only a subset of the production data. Data Pump Export/Import provides flexible data- subsetting capabilities. Serves as a backup archive. You can use a full database export as an archive of the current database. Enables the upgraded database to be established on an operating system or hardware platform that is different from that which is supporting the database being upgraded. Network- based Data Pump Import allows the new Oracle database to be directly loaded across the network from the old database being upgraded. Thus, no intervening dump files are required. Time Requirements for Migrating Data and Upgrading with Export/Import. Migrating data and upgrading an entire Oracle database by using Export/Import can take a long time, especially compared to using DBUA or performing a manual upgrade. Therefore, you might be required to schedule the upgrade during non- peak hours or make provisions for propagating to the new database any changes that are made to the current database during the upgrade. Choose a New Location for Oracle Home when Upgrading. You must choose a location for Oracle home for the new release of Oracle Database that is separate from the Oracle home of your current release. You cannot install the new software into the same location for Oracle home as your current release. Using separate installation locations enables you to keep your existing Oracle software installed along with the new Oracle software. This method enables you to test the upgrade process on a test database before replacing your production environment entirely. Develop a Test Plan for Upgrading Oracle Database. You need a series of carefully designed tests to validate all stages of the upgrade process. Executed rigorously and completed successfully, these tests ensure that the process of upgrading the production database is well understood, predictable, and successful. Perform as much testing as possible before upgrading the production database. Do not underestimate the importance of a complete and repeatable testing process.
0 Comments
Leave a Reply. |
AuthorWrite something about yourself. No need to be fancy, just an overview. Archives
August 2017
Categories |