This note describes the steps for upgrading
ASM running on Oracle 10.2.0.4 to Oracle 11.2.0.1 on a HP UX platform.
To upgrade the ASM, we need to install the 11g R2 Grid Infrastructure software as ASM
is now no longer part of the database software as was the case in Oracle 10g.
We launch the installer from Grid Infrastructure
software directory - unzip the file hpia64_11gR2_grid.zip which we have
downloaded from OTN.
Optional -------------------- When you are using HP UX platform normally ignore this step
This error
“Unable to get the current group” when we launch the installer is a known error
for HP UX which is resolved by applying the OS patch OS patch PHCO_40381
----------------------------------------------------------------------------------------------
Ensure the “Upgrade Grid Infrastructure” is chosen
The OUI detects the running 10g ASM
instance and automatically the Upgrade Grid Infrastructure option is selected.
Specify the password for ASMSNMP user
Select the appropriate group – we use dba
group for all three – ignore the warning message which will follow.
One of the new 11g OUI features is that it
generates some fix-up scripts which can be run to change or modify certain
kernel parameter settings.
Click on the “Fix and Check Again” button
A fix-up script runfixup.sh has been
generated which needs to be run as root – note some parameters cannot be
changed on the fly and require a system reboot.
After running the script, we click on OK and then on Check Again.
Even after running the fix-up script, some
kernel parameters cannot be modified without a reboot.
Since this is a test, we do not do a
machine reboot at this stage and we check the Ignore All box and click on Next
Note that Migrate ASM is showing the value true
root@inpsidt1#
./rootupgrade.sh
Running
Oracle 11g root.sh script...
The
following environment variables are set as:
ORACLE_OWNER= oracle
ORACLE_HOME= /data/oracle/product/11.2.0/grid
Enter
the full pathname of the local bin directory: [/usr/local/bin]:
The
file "dbhome" already exists in /usr/local/bin. Overwrite it? (y/n) [n]:
The
file "oraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]:
The
file "coraenv" already exists in /usr/local/bin. Overwrite it? (y/n) [n]:
Entries
will be added to the /etc/oratab file as needed by
Database
Configuration Assistant when a database is created
Finished
running generic part of root.sh script.
Now
product-specific root actions will be performed.
2011-05-17
12:24:49: Checking for super user privileges
2011-05-17
12:24:49: User has super user privileges
2011-05-17
12:24:49: Parsing the host name
Using
configuration parameter file:
/data/oracle/product/11.2.0/grid/crs/install/crsconfig_params
Creating
trace directory
stty:
: Not a typewriter
stty:
: Not a typewriter
stty:
: Not a typewriter
mesg:
cannot change mode
LOCAL
ADD MODE
Creating
OCR keys for user 'oracle', privgrp 'oinstall'..
Operation
successful.
CSS
appears healthy
Stopping
CSSD.
Shutting
down CSS daemon.
Shutdown
request successfully issued.
Shutdown
has begun. The daemons should exit soon.
CRS-4664:
Node inpsidt1 successfully pinned.
Adding
daemon to inittab
CRS-4123:
Oracle High Availability Services has been started.
ohasd
is starting
inpsidt1 2011/05/17 12:26:18
/data/oracle/product/11.2.0/grid/cdata/inpsidt1/backup_20110517_122618.olr
Successfully
configured Oracle Grid Infrastructure for a Standalone Server
Updating
inventory properties for clusterware
Starting
Oracle Universal Installer...
Checking
swap space: must be greater than 500 MB.
Actual 7591 MB Passed
The
inventory pointer is located at /var/opt/oracle/oraInst.loc
The
inventory is located at /home/oracle/oraInventory
'UpdateNodeList'
was successful.
Automatic Storage Management Configuration
Assistant ASMCA is a new tool in Oracle 11g for performing ASM administration.
Previously we used to do the same via DBCA
in Oracle 10g.
From the installation log files we can see
that ASM is being upgraded by the ASMCA which has been invoked by the OUI.
INFO:
Starting 'Automatic Storage Management Configuration Assistant'
INFO:
Starting 'Automatic Storage Management Configuration Assistant'
INFO:
Executing ASMCA
INFO:
Command /data/oracle/product/11.2.0/grid/bin/asmca -silent -oui_internal
-upgradeASM
INFO:
... GenericInternalPlugIn.handleProcess() entered.
INFO:
... GenericInternalPlugIn: getting configAssistantParmas.
INFO:
... GenericInternalPlugIn: checking secretArguments.
INFO:
... GenericInternalPlugIn: starting read loop.
INFO:
Read: ASMSNMP_PASSWORD_PROMPT
INFO:
Processing: ASMSNMP_PASSWORD_PROMPT for argument tag –asmMonitorPassword
INFO:
End of argument passing to stdin
INFO:
Read:
INFO:
Read: ASM upgraded and started successfully.
INFO:
Read:
INFO:
Completed Plugin named: Automatic Storage Management Configuration Assistant
We can see that the oratab file has also
been updated and the ORACLE_HOME for the ASM instance is now showing the 11g
Oracle Home
.
root@inpsidt1# cat /etc/oratab |grep ASM
+ASM:/data/oracle/product/11.2.0/grid:N
Let us now add a new disk to the previously
existing disk group DATA which was created in 10g ASM.
We launch ASMCA via asmca from Grid Infrastructure software home
Note there are two types of compatibility
for the diskgroup. One is the ASM compatibility and the other is Database
compatibility.
- ASM
Compatibility: The minimum version of the ASM software that can access the
disk group. In 11g, the default setting is 10.1.
- Database
Compatibility: The minimum
COMPATIBLEdatabase initialization parameter setting for any database instance that uses the disk group. In 11g, the default setting is 10.1.
Note – before
performing the ASM upgrade, shut down any Oracle databases on the same machine
or they will be abnormally shutdown when communication to the ASM instance is
lost as the existing 10g ASM instance is shutdown as part of the ASM upgrade
process.
We can see lines like this in the database
alert log:
Errors
in file
/data/oracle/product/10.2.0.4.5/admin/test11g/bdump/test11g_asmb_15099.trc:
ORA-15064:
communication failure with ASM instance
ORA-03113:
end-of-file on communication channel
Tue
May 17 12:25:08 2011
ASMB:
terminating instance due to error 15064
No comments:
Post a Comment