Exploiting 11g ASM features against 10g database
We all know that new Oracle 11g release has much more to offer. Its going to take some time for every one to adopt 11g
in production. Lot of testing to be done. Management has to be
convinced about its stability based on success stories of others
customers. But somewhere, someone has to start.
For those who are using ASM as their storage can upgrade their ASM instance alone to 11g immediately and start exploiting 11g ASM features against their 10g database.
Following are the simple steps to follow and you are all set to go with ASM 11g features for your 1og database.
1. Install Oracle 11g RDBMS software for your new ASM 11g HOME.
2. Shutdown your 10g database & ASM instance
3. Reconfigure Oracle Cluster Synchronization Services to run from new 11g home
Set PATH and other environment variables(ORACLE_HOME, ORACLE_SID) to new ORACLE 11g executables.
Login as root and run following command.
[root@arul oracle]# localconfig reset
Successfully accumulated necessary OCR keys.
Creating OCR keys for user 'root', privgrp 'root'..
Operation successful.
Configuration for local CSS has been initialized
Stale CSS daemon is running... killing it now
Cleaning up Network socket directories
Setting up Network socket directories
Adding to inittab
Startup will be queued to init within 30 seconds.
Checking the status of new Oracle init process...
Expecting the CRS daemons to be up within 600 seconds.
Cluster Synchronization Services is active on these nodes.
arul
Cluster Synchronization Services is active on all the nodes.
Oracle CSS service is installed and running under init(1M)
[root@arul oracle]#
4. Copy password file & S/Pfile to new 11g ORACLE_HOME/dbs folder
$ cp spfile+ASM.ora /u02/app/oracle/product/11g/db_1/dbs
$ cp orapw+ASM /u02/app/oracle/product/11g/db_1/dbs
5. Remove the obsolete initialization parameters
Parameters like background/user/core dump dest are obsolete in 11g, so remove those parameters.
Change the remote login passwordfile to exclusive.
6. Login as sysdba and start the ASM instance from 11g home and grant sysasm privilege.
$ sqlplus / as sysdba
SQL*Plus: Release 11.1.0.6.0 - Production on Mon Jan 21 09:11:50 2008
Copyright (c) 1982, 2007, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ASM instance started
Total System Global Area 284565504 bytes
Fixed Size 1299428 bytes
Variable Size 258100252 bytes
ASM Cache 25165824 bytes
ASM diskgroups mounted
SQL> grant sysasm to sys;
Grant succeeded.
SQL> exit
7. Start 10g RDBMS instance.
set PATH and other environment variables(ORACLE_HOME, ORACLE_SID) to ORACLE 10g RDBMS instance.
$ sqlplus / as sysdba
SQL*Plus: Release 10.2.0.1.0 - Production on Mon Jan 21 09:13:46 2008
Copyright (c) 1982, 2005, Oracle. All rights reserved.
Connected to an idle instance.
SQL> startup
ORACLE instance started.
Total System Global Area 184549376 bytes
Fixed Size 1218412 bytes
Variable Size 71305364 bytes
Database Buffers 109051904 bytes
Redo Buffers 2973696 bytes
Database mounted.
Database opened.
SQL>
8. All set to go.
Now you can use 11g ASM features for your 10g RDBMS instance.
ASMCMD has the few very handy new commands: cp, lsdsk, pwd...
Few examples..
ASMCMD [+data/mars] > cp spfilemars.ora +data/mars/test/spfilemars.ora
source +data/mars/spfilemars.ora
target +data/mars/test/spfilemars.ora
copying file(s)...
file, +DATA/mars/test/spfilemars.ora, copy committed.
ASMCMD [+data/mars] > cd test
ASMCMD [+data/mars/test] > ls
spfilemars.ora
$ asmcmd -v
asmcmd version 11.1.0.6.0
ASMCMD [+data/mars/test] > pwd
+data/mars/test
ASMCMD [+data/mars/test] > lsdsk
Path
/dev/raw/raw1
/dev/raw/raw2
ASMCMD [+data/mars/test] > lsct
DB_Name Status Software_Version Compatible_version Instance_Name Disk_Group
mars CONNECTED 10.2.0.1.0 10.2.0.1.0 mars DATA
mars CONNECTED 10.2.0.1.0 10.2.0.1.0 mars FRA