Upgrading ASM manually to version 11.2.0.2


Upgrading ASM manually to version 11.2.0.2

Due to a bug in Oracle upgrade process it is impossible to upgrade ASM 10g to ASM 11g using the GUI. The proposed method uninstalls ASM 10g and installs ASM 11g from scratch.

1.      Ask a UNIX admin to create a new disk called “dummy” of any size at the same location as the rest of the existing Oracle data disks. It will be used during the installation.
2.      Download  the following file containing ASM 11.2.0.2:

p10098816_112020_Linux-x86-64_3of7.zip

3.      Shutdown ALL databases, listener and ASM instance on the target box.
4.      Save the old /usr/local/bin/dbhome and /usr/local/bin/oraenv to some backup location just in case we’ll need them later on.
5.      As a root, go to the old $ORACLE_HOME and run the following command in order to unregister ASM 10g and stop all ASM-related processes :

localconfig delete

Make sure that no oracle processes are running afterwards.

6.      Add the following entry to /etc/oratab :

grid11:/oracle/app/oracle/product/grid11:N

7.      Remove the +ASM entry from /etc/oratab completely

8.      Create a new directory to hold the ASM software :

mkdir /oracle/app/oracle/product/grid11

9.      Run . oraenv grid11
10.  Unset TNS_ADMIN, make sure that all $ORA* environment variables point to a new Oracle directory
Unset $TNS_ADMIN
11.  Unpack the file from the p.1 and start the installer from the unpacked directory in XWindows:

export DISPLAY=<myipaddress>:0
./grid/runInstaller


12.  Oracle will offer several options. Choose option 2 (“Configure Grid Infrastucture for Standalone server”). Follow the instructions and enter the new ORACLE_HOME for the 11g grid installation :
/oracle/app/oracle/product/grid11
13.  When asked to enter a new diskgroup name, enter DUMMY_DATA and choose the dummy disk created in p.1 from the list of available disks. Choose “External redundancy” radio button.
14.  At the end of the upgrade you will be asked to run root.sh as user root. Please ask UNIX admin to do that and accept all default values during the run; review the output.
15.  After the installation is completes move the +ASM pfile out of DUMMY_DATA into $ORACLE_HOME/dbs as follows:

. oraenv +ASM
sqlplus "/ as sysasm"
create pfile='/oracle/app/oracle/product/grid11/dbs/init+ASM.ora'from spfile;
shutdown immediate;
startup pfile='/oracle/app/oracle/product/grid11/dbs/init+ASM.ora';
alter diskgroup DUMMY_DATA mount;
drop diskgroup DUMMY_DATA including contents;
create spfile from pfile;
alter system set spfile='/oracle/app/oracle/product/grid11/dbs/spfile+ASM.ora';
shutdown immediate;
startup;

16.  Make sure that the updated +ASM entry in the /etc/oratab looks like this:

+ASM:/oracle/app/oracle/product/grid11:Y

17.  Make sure that +ASM instance is running, if not – start it from the new $ORACLE_HOME

sqlplus / as sysasm
startup

18.  Mount all diskgroups manually for the first time.
19.  Grant sysasm to sys in the new +ASM instance

sqlplus / as sysasm
grant sysasm to sys;
exit

20.  Check that the new +ASM instance has all diskgroups mounted :

Sqlplus / as sysdba @/oracle/app/oracle/local/asm/asm_diskgroups

21.  Ensure that the 11.2.0.2 listener.ora is configured properly.  Remove the listener.ora from the 10.2.0.4 oracle home
vi /oracle/app/oracle/product/11.2.0.2/network/admin/listener.ora

22.  Register the correct listener with CRS.
. oraenv grid11
srvctl stop lsnr
srvctl remove lsnr
srvctl add listener -l listener -p 1521 -o /oracle/app/oracle/product/11.2.0.2
srvctl start lsnr

23.  Restart ASM, Mount all diskgroups and start all databases on the box.


Comments

Post a Comment

Popular posts from this blog

Useful OEM Queries to get Target details from OEM Repository

List Targets with TNS Listener ports configured : SELECT mgmt$target.host_name , mgmt$target.target_name , mgmt$target.target_type , mgmt$target_properties.property_name , mgmt$target_properties.property_value FROM mgmt$target , mgmt$target_properties WHERE ( mgmt$target.target_name = mgmt$target_properties.target_name ) AND ( mgmt$target.target_type = mgmt$target_properties.target_type ) and ( mgmt$target.target_type = 'oracle_listener' ) and ( mgmt$target_properties.property_name = 'Port' ); Devora02       LISTENER_ora02                       oracle_listener Port 1529 Devora01       LISTENER_ora01                       oracle_listener Port 1529 Devora04       LISTENER_ora04                       oracle_listener Port 1529 List Machine_Names, CPU Count & Database Verion for Licensing SELECT mgmt$target.host_name , mgmt$target_properties.property_name , mgmt$target_properties.property_value FROM mgmt$target , mgmt$target_properties WHERE ( mgmt$
Read more

WARNING: Subscription for node down event still pending' in Listener Log

Image
These messages are related to the Oracle TNS Listener's default subscription to the Oracle Notification Service (ONS). In a non-RAC environment it is recommended to disable this subscription.   This feature was introduced in Oracle 10g. SOLUTION Set the following parameter in the listener.ora: SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener_name>=OFF Where <listener_name> should be replaced with the actual listener name configured in the LISTENER.ORA file. SUBSCRIBE_FOR_NODE_DOWN_EVENT_<listener_name> parameter is to be placed by itself on an empty line. It will be necessary to restart or reload the listener following the addition of this parameter. This will prevent the messages from being written to the log file and may also prevent the TNS Listener from hanging periodically.  See (10g only) NOTE 340091.1 Intermittent TNS Listener Hang, New Child Listener Process Forked Please Note: Setting SUBSCRIBE_FOR_NODE_DOWN_<listener_n
Read more

ORA-65139: Mismatch between XML metadata file and data file

Error: CDB$ROOT@EBTUPRDC> CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse; CREATE PLUGGABLE DATABASE EBTUSPRDPDB1 using '/home/oracle/EBTUSPRDC.xml' nocopy tempfile reuse * ERROR at line 1: ORA-65139: Mismatch between XML metadata file and data file /u05/odb/ORADATA_1/EBTUSPRDC/datafile/system.1531.807800993 for value of fcpsb (2230502002 in the plug XML file, 2230505492 in the data file) Fix: Don't open Non-CDB database until we complete pdb creation other wise we will get above error. Shutdown immediate; startup mount; alter database open read only; create xml file. shutdown immediate; Connect to CDB and Create Pluggable database .
Read more