Network Security Internet Technology Development Database Servers Mobile Phone Android Software Apple Software Computer Software News IT Information

In addition to Weibo, there is also WeChat

Please pay attention

WeChat public account

Shulou

How to upgrade from oracle 10g RAC to oracle 11g RAC

2025-01-18 Update From: SLTechnology News&Howtos shulou NAV: SLTechnology News&Howtos > Database >

Share

Shulou(Shulou.com)05/31 Report--

Oracle 10g RAC how to upgrade to oracle 11g RAC, I believe that many inexperienced people do not know what to do, so this article summarizes the causes of the problem and solutions, through this article I hope you can solve this problem.

Upgrade from oracle 10g RAC to oracle 11g RAC

Summary of the environment

Due to the shortage of hardware in the old environment to support the production system, you need to switch to the new hardware and plan to upgrade the version of the database from oracle RAC 10.2.0.5 to oracle RAC 11.2.0.4. The upgrade ideas are as follows:

1. Set up the oracle RAC 11g environment, and do not specify how to build it here.

2. On the Node 1 server of oracle RAC 11g, open a new user ora10g, and then install the stand-alone database of oracle 10.2.0.5. It is important to note that the group to which ora10g belongs. You must have permission in ORACLE_HOME/bin/oracle to access the asm group of oracle 11g cluster.

3. Build the DATAGUARD environment of node 1 from oracle RAC 10.2.0.5 to oracle RAC 11g. Without going into details here, it is important to note that 11g asm is used to store database files.

4. On the night of the upgrade, end the standby role of ora10g in the way of failover, switch to the master, run the 11g script, and close the database.

5. Open the database file of ora10g with 11g database software.

6. use scripts to upgrade digital dictionaries.

7. Register database services to cluster management.

8. Check configuration.

System environment description:

192.168.1.121murmuri-"originally used the oracle 10.2.0.5 cluster database environment. -"oracle users"

192.168.42.12 Murray-"New use of oracle 11g cluster environment, where there are ora10g, oracle and grid users

1. Check DG synchronization

Log in 192.168.1.121 and switch several logs in succession to the database.

Alter system archive log current

Check whether the logs are synchronized. Check synchronization at 192.168.1.121 and 192.168.42.12, respectively.

Select * from v$log_history

Select * from v$archive_dest

II. Close the main database of 192.168.1.121 and stop listening

Lsnrctl stop

Srvctl stop database-d etest

4.5 switch standby (192.168.42.12)

The failover method is used.

Log in to 192.168.42.12 server using ora10g user

Initiate in the main library (192.168.1.121) and send the standby log function to be removed.

Alter system set log_archive_dest_3='' scope=both

Execute on standby (192.168.42.12) ora10g user

Sqlplus / as sysdba

Alter database recover managed standby database finish

Alter database commit to switchover to primary

Shutdown immediate

Startup

If you have a problem opening the database here, be sure to solve it before opening it with an 11g script, otherwise the upgrade will fail.

Copy the utlu112i.sql script under 11g $ORACLE_HOME/rdbms/admin to 10g $ORACLE_HOME/rdbms/admin and execute it on 10g. This script can check some information before the upgrade. If the condition is not met, it will be listed.

Sqlplus / as sysdba

Spool upgrade_info.log

@? / rdbms/admin/utlu112i.sql

Then shut down the database of oracle 10g.

Shutdown immediate

The above script needs to be very careful. If you forget to run it, once you open it with 11g, the whole environment will be destroyed and irreversible.

Log in to the user oracle (192.168.42.12) and make sure that the instance names are configured correctly.

Use oracle 11g software to open the 10g library and upgrade the data dictionary.

Use the defined initetest1.ora file and use spfile to complete the upgrade. The initetest1.ora parameter here is not specified. You can modify it with an example of a cluster.

Sqlplus / as sysdba

Startup upgrade

Run script in upgrade mode: catupgrd.sql

Execute the statement:

This run takes a long time, about 20 minutes, and it is best to run it in the background, where the upgrade script failed due to insufficient space in the temp temporary tablespace during the test. Therefore, when putting into production, make sure that the temp space has been adjusted to the appropriate value. To restart the script, you need to restart the database, otherwise session will hang.

Determine whether the temporary tablespace of the new library exists

Select * from dba_temp_files

Expand temporary tablespaces:

Alter database tempfile'+ DATA/etest/temp01.dbf' resize 4G

Sqlplus-S-L "/ as sysdba"

Welcome to subscribe "Shulou Technology Information " to get latest news, interesting things and hot topics in the IT industry, and controls the hottest and latest Internet news, technology news and IT industry trends.

Views: 0

*The comments in the above article only represent the author's personal views and do not represent the views and positions of this website. If you have more insights, please feel free to contribute and share.

Share To

Database

Wechat

© 2024 shulou.com SLNews company. All rights reserved.

12
Report