Oracle 10.2.0.1 in Windows2003+mscs dual-machine hot standby environment

One, all data operation first step: backup data, I like to use EXPDP, very soon.

Ii. offline Oracle database instances and listening resources in Cluster Manager

Third, in order to prevent system crashes, first do Node2 node upgrade (Node2 do not do domain name server, relatively good recovery), copy the upgrade file copy to Node1 and Node2, decompression.

Four, in the Node2 run Setup.exe installation, note that the prompts need to choose Oracle_home, must be oracle_home selected in the original Oracle installation Oracle_home, in the installation process error, prompted the need to upgrade the file or program is being used , then restart Node2.

Five, Node2 start, again run Setup.exe, at this time can normally pass, installation needs 3-5 minutes, very soon.

Vi. in cluster management, move all resources to Node2 restart Node1

Seven, in the Node2 into the upgrade mode upgrade. Annoying Windows system, when the Oracle instance service is taken offline, the error occurs when using the SYS user to log on to start the data

Sql*plus:release 10.2.0.4.0-production on Saturday March 27 02:38:45 2010

Copyright (c) 1982, 2007, Oracle. All Rights Reserved.

Sql> Conn/as SYSDBA

Error-ora-12560:tns:protocol Adapter Error

Manually turn on the listening service

Log on with full name

Sql> Conn SYS/XXXXXXXXX@ZSGL as Sysdba

You are connected to an idle routine.

Sql> Startup upgrade

Tip The parameter file could not be found. Manual positioning Pfile

sql> startup upgrade pfile= ' G:xxxxxinitxxxx.ora '

This will be resolved after the upgrade is completed.

Run the script @rdbms/admin/catupgrd.sql, this process is relatively long, at IBM X3950 server roughly about 45 minutes.

Shutdown immediate

Startup

Run Script @rdbms/admin/utlrp.sql

Eight, upgrade node1:node1 only need to upgrade the program files, to extract the upgrade package, run Setup.exe, such as the encounter prompts need to upgrade the file or program is being used, restart the Node1, run Setup.exe again.

Nine, the cluster manager, the Oracle instance resources and listening resources online. The resource starts normally. Move resource groups to each other to see if the resource group can switch normally.

X. sql> alter system reset Log_archive_start scope=spfile sid= ' * ';

System altered.

Restart the database.

Resolve the previous ORA-32004 error.

XI. Command archive lost list, make a temporary table and insert a large table to see if the archive is normal.

12, run the Rman backup script, observe the Rman backup is normal.

This article source: It Technology network (http://www.52ij.com/jishu/132.html)