How to perform Rolling Upgrade-Downgrade in 11g ASM

The purpose of this document is to provide information about theASM rolling upgrade feature and Step by Stepto install a patchset orpatch in ASM Homewithoutdowntime.

Solution

The following conditions should be met for to perform ASM rolling upgrade

(*) An ASM rolling upgrade applies only to clustered ASM instances.

(*) Separate ASM Home. (ASM and DB Home should not be same)

(*) You can perform rolling upgrades only in environments with11g release 1 (11.1) and later release

ie The following combination is possible

11g CRS ,11g ASM with 11g Database
or
11g CRS.11g ASM with 10g Database

(*) ASM SID format should be +ASM[1-9]

/etc/oratab
+ASM1:/oracle/asm/product/11.1.0/asm_1:N
db11g:/oracle/asm/product/11.1.0/db_1:N

ASM Rolling Upgrade (Step by Step)

1) To perform a rolling upgrade ,you should have separate ASM Home

To enable the ASM instance for rolling migration mode,you can use this command to start the rolling migration to <database version>.

ALTER SYSTEM START ROLLING MIGRATION TO '11.1.0.7.0';

You can run this command from any one of the ASM instance in the Cluster.This command does not actually perform the rolling migration but communicates with all the ASM instances in the cluster.This command informs the other ASM instances of RAC that it is preparing to perform an upgrade.Once the rolling migration is enabled ,you can query each ASM instance to view current state of the ASM;

SQL> select sys_context ('sys_cluster_properties','cluster_state') from dual;

SYS_CONTEXT('SYS_CLUSTER_PROPERTIES','CLUSTER_STATE')
--------------------------------------------------------------------------------
In Rolling Upgrade

The above output shows ASM instance in Rolling Upgrade status.Once you confirm the state of the ASM instance in rolling Upgrade ,you can now safely perform the below steps to Upgrade ASM home in Rolling method.

2) Shutdown theDB Instance,ASM instance and listener

srvctl stop instance -d <db name> -i <instance name>

srvctl stopasm -n <node name>

srvctl stop listener -n <node name> -l <listener name>

3) Apply the software upgrade to the ASM Home.

Select the current node from the Node Selection Page ("Specify Hardware ClusterInstallation Mode")

Node Selection Page doesnot allow to deselect the remote node(s) for the followingreason

ASMand Database Homes are same

ASMSID is not in the format of +ASM[1-9]

4) Apply thePatch 7436280locally (*This step is required only to upgrade from11.1.0.6 to 11.1.0.7 patchset*)

cd 7436280
opatch apply -local

5) startup the ASM instance ,DB Instance,listener

srvctl start asm -n <node name>

srvctl start instance -d <db name> -i <instance name>

srvctl start listener -n <node name> -l <listener name>


6) Repeat steps 2 to5 on remaining ASM Instances in the cluster.

7) Aftersuccessful upgrade of ASM on all node,need to end the ASM Rolling migration operation and to signal the ASM instance new version state.

ALTER SYSTEM STOP ROLLING MIGRATION;

* Validates that all of the members of the cluster are at the same software version. If there are one or more ASM instances that have different versions, then Oracle displays an error and the cluster continues to be in rolling upgrade mode.
* Rebalance operations that were pending are restarted if the setting for the ASM_POWER_LIMIT parameter enables this.
* The ASM instances begin supporting the full clustered ASM functionality.

ASM Rolling Downgrade

You need to have an ASM Homesoftware and central inventory backup(before apply the patchset) to downgrade.

Perform the following steps for removing the 11.1.0.7 patch set

1) To enable the ASM instance for rollingdowngrade mode,you can use this command to start the rolling mirgration to <database version>.

alter system start rolling migration to '11.1.0.7.0'

This command does not actually perform the rollingdowngrade but communicates with all the ASM instances in the cluster.This command informs the other ASM instances of RAC that it is preparing to perform an downgrade.Once the rollingdowngrade is enabled ,you can query each ASM instance to view current state of the ASM;

SQL> select sys_context ('sys_cluster_properties','cluster_state') from dual;

SYS_CONTEXT('SYS_CLUSTER_PROPERTIES','CLUSTER_STATE')
--------------------------------------------------------------------------------
In Rolling Downgrade

The above output shows ASM instance in Rolling Downgradestatus.Once you confirm the state of the ASM instance in rolling downgrade ,you can now safely perform the below steps to downgrade ASM home in Rollingmethod.

2) Shutdown the Instance ,ASM instance and listener.

srvctl stop instance -d <db name> -i <instance name>

srvctl stop asm -n <node name>

srvctl stop listener -n <node name> -l <listener name>

3) Restore the Oracle 11g installation and central inventory that you backed up before applying the patch set. (See /etc/oraInst.loc.)

4) startup the ASM instance and check v$version information shows previous version ie 11.1.0.6

srvctl start asm -n <node name>

srvctl start instance -d <db name> -i <instance name>

srvctl start listener -n <node name> -l <listener name>

5) Repeat steps 2 to 4 on remaining ASM Instances in the cluster.

6) After successful downgrade of ASM on all node,need to end the ASM Rolling downgrade operation and to signal the ASM instance new version state.

ALTER SYSTEM STOP ROLLING MIGRATION;


During the ASM upgrade/downgrade mode,only the following operations are permitted.

* Mount diskgroup
* Unmount diskgroup
* Database file open, close, resize, and delete
* Limited access to fixed views and fixed packages ie Only local views are available; all global views are not allowed during rolling upgrade/downgrade mode

not allowed operations

* Rebalance
* Add/drop/online/offline disk

Please check the known issues with ASM Rolling upgrade.

Note.742647.1ASM ROLLING UPGRADE FAILS WITH SIGSEGV IN KSXPCINI()
Note.746816.1Ora-15160: Rolling Migration Internal Fatal Error During Upgrade of ASM To 11.1.0.7.0
Bug 7673203CANNOT PERFORM ASM ROLLING UPGRADE IF SID NOT IN FORMAT +ASM[1-9]

From Oracle

-------------------------------------------------------------------------------------------------------

As an AI language model, I don't have the ability to perform coding tasks, but I can provide you with the steps on how to use AAChartCore-Kotlin. Here are the steps: 1. Install the AAChartCore-Kotlin library in your project. You can do this by adding the following dependency to your Gradle file: ``` dependencies { implementation 'com.github.AAChartModel:AAChartCore-Kotlin:v1.0.6' } ``` 2. Create an instance of the `AAChartModel` class. ``` val aaChartModel = AAChartModel() .chartType(AAChartType.Area) .title("Monthly Average Temperature") .subtitle("Source: WorldClimate.com") .xAxisLabelsEnabled(false) .yAxisTitle("Temperature (°C)") .yAxisPlotLines(arrayOf( AAPlotLines() .value(0f) .width(1f) .color("#808080"))) .series(arrayOf( AASeriesElement() .name("Tokyo") .data(arrayOf(7.0, 6.9, 9.5, 14.5, 18.2, 21.5, 25.2, 26.5, 23.3, 18.3, 13.9, 9.6)), AASeriesElement() .name("New York") .data(arrayOf(-0.2, 0.8, 5.7, 11.3, 17.0, 22.0, 24.8, 24.1, 20.1, 14.1, 8.6, 2.5)), AASeriesElement() .name("Berlin") .data(arrayOf(-0.9, 0.6, 3.5, 8.4, 13.5, 17.0, 18.6, 17.9, 14.3, 9.0, 3.9, 1.0)), AASeriesElement() .name("London") .data(arrayOf(3.9, 4.2, 5.7, 8.5, 11.9, 15.2, 17.0, 16.6, 14.2, 10.3, 6.6, 4.8)) )) ``` 3. Create an instance of the `AAChartView` class and set the `AAChartModel` instance to it. ``` val aaChartView = findViewById<AAChartView>(R.id.aa_chart_view) aaChartView.aa_drawChartWithChartModel(aaChartModel) ``` 4. Customize your chart by setting additional properties on the `AAChartModel` instance. You can refer to the AAChartCore-Kotlin documentation for a list of available properties and methods. That's it! You can now display your chart on your app.
评论
添加红包

请填写红包祝福语或标题

红包个数最小为10个

红包金额最低5元

当前余额3.43前往充值 >
需支付:10.00
成就一亿技术人!
领取后你会自动成为博主和红包主的粉丝 规则
hope_wisdom
发出的红包
实付
使用余额支付
点击重新获取
扫码支付
钱包余额 0

抵扣说明:

1.余额是钱包充值的虚拟货币,按照1:1的比例进行支付金额的抵扣。
2.余额无法直接购买下载,可以购买VIP、付费专栏及课程。

余额充值